First the target devices boots and acquires an IP address.
If there is an associated target device available under the PVS environment, it’s boot setting values are read and the target device is booted according to these settings.
Target device MAC address lookup completed.
Target device communicates to the provided PVS Server and its associated running “Citrix PVS Stream Service”.
The bootstrap file typically houses connectivity information for all of the PVS servers under your associated PVS Farm.
TFTP services reads associated bootstrap, boot file (ARDBP32.BIN) information to provide back to the client as a usable network boot server.
Target device connects to the TFTP server (typically a PVS Server) provided by DHCP services or by PXE Service.
Target Device Connectivity to Provided TFTP Server.
The PXE Service on the PVS Server will provide the location\IP Address of the server that hosts the ARDBP32.bin file, which is typically the PVS Server itself
If the DHCP Option 66 and 67 is not configured, then we need to Setup\Configure the PXE service on the PVS Server.
Very common to use default file name, rarely changed from default name.
Under a PVS environment, the default file name is ARDBP32.BIN.
If needed, and on rare occasion, TFTP services can also be hosted on an isolated/dedicated infrastructure server.
TFTP boot server services are typically setup and configured on your actual PVS Servers.
Used to provide the target device with a TFTP Boot Server.
DHCP Server (in this special use case of PXE Boot) needs to be configured with below advanced option and values.
IP Address, Subnet Mask, Default Gateway, DNS Server(s).
DHCP Server allocates standard/basic network configuration settings to the Target using DORA Process initiated by the Target device.
DHCP network scope settings are configured for the specific network that the target device is physically located.
Target device reaches and communicates with DHCP Server.
By default, DHCP services are only able to allow target devices to send out a network broadcast limited to only the network/VLAN that it currently resides on.
Using an IP Helper allows the switching environment to identify that the DHCP Server(s) are physically located on a different network/VLAN.
Values of the IP Helper are simply the IP address of the associated DHCP Server(s).
Device BIOS configured to perform a network boot using the NIC (Not using BDM ISO or Partition).
0 kommentar(er)
