Applicable Products

Ct Driver's License Replacement

• Provisioning Services

Symptoms or Error

This article provides information about how to troubleshoot a target device that fails to boot into a vDisk. The status of the target device appears as a red X state within the console

Solution

Complete the following steps to resolve the issue:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
IP Aquisition

1. Verify DHCP/PXE/TFTP services are running successfully in your environment:
   This can be verified using the CTX217122 - PXEChecker for Citrix Provisioning Services

2. Validate that Network boot is enabled in BIOS.

3. Disable Spanning Tree Protocol or enable Port Fast Engelmann drivers ed. on any port the switch uses for PVS traffic.

   ​Note: Refer to CTX117374 - Best Practices for Configuring Provisioning Services Server on a Network for more information on firewall settings.

Tx Driver License Replacement

1. Enable Verbose mode under the bootstrap.

When the target device boots, verify that it is getting an IP address while connecting to the TFTP server.

2. ​Run the following tftp command to test TFTP from the target device to the PVS server:

   tftp <IP of the TFTP server/PVS> get ardbp32.bin

   Note: Test TFTP by installing the TFTP protocol in Windows 7 with Add Remove Windows Features, and with Windows 2008 in the Add Features server role.

   In a broadcast domain, only one PXE server can be configured. Some environments might have another third party software running the PXE protocol, such as Norton Ghost.
   Note: When using DHCP scope options, the PXE server does not need to be configured in an environment.

3. If PXE or DHCP options fail to boot a device, configure a BDM file to test boot a target device. Configure BDM with a static IP address and it will bypass the DHCP Server.

1. On the server and target device, the following ports are used:
   If you are using a virtual machine, validate the Network Interface Card (NIC) used to connect to the PVS server at the top of the list containing the polling order of network cards.

   
   For the Stream service: UDP 6910, 6911, 6912, 6913, 6914, 6915, 6916, 6917, 6918, 6919, 6920, 6921, 6922, 6923, 6924, 6925, 6926, 6927, 6928, 6929, and 6930.
   For the console: TCP 54321 and 54322. TFTP: Port 69.

2. Disable the Windows Firewall on the target device and server. After verifying the firewall, open the ports: UDP 6890 – 6909 for communication between servers.
   Note: Refer to CTX117374 - Best Practices for Configuring Provisioning Services Server on a Network for more information on firewall settings.

3. Uninstall the Antivirus software. After the target device boots, install the Provisioning Services (PVS) target software in private image mode.
   Note: Refer to CTX124185 - Provisioning Services Antivirus Best Practices for more information on configuring Antivirus software.

4. Verify you are able to ping the target device to the PVS server.
   Note: Use the IP address of the server rather than the Fully Qualified Domain Name (FQDN).

5. Disable IPv6 on the server and target device by editing the registry and modifying the following key:

HKLMSYSTEMCurrentControlSetServicesTcpip6Parameters
DWORD DisabledComponents = 0xff

Image Creation

1. Remove hidden network cards from Device Manager. (Note: Do not remove hidden (ghost) Network Cards from a XenServer target. Only remove them from Hyper-V, VMWare or Physical targets)
   Note: Refer to CTX133188 - Event ID 7026 - The following boot-start or system-start driver(s) failed to load: Bnistack for details on how to remove hidden network cards.

2. Uninstall any software on the target device that configures a third party NIC driver, such as IBM Tivoli.

3. If the target device or PVS Server is configured with bonded network cards, break the bond and test with only one NIC active.
   This will simplify the environment and validate if the bonding network cards could be causing an issue.
   Note: Refer to Requirements and considerations for manufacturer's NIC teaming.

4. If the environment is configured with vSphere 5.0 (without any updates) and using VMXNET3 drivers, either enable Interrupt safe mode in the bootstrap or upgrade to vSphere 5.1 or later.
   Note: For additional information, refer to CTX131993 - vSphere 5 Support for Provisioning Server 5.6.x, 6.x and 7.x.

Additional Resources

Gtx 1060 Driver

• CTX117374 - Best Practices for Configuring Provisioning Server on a Network
• CTX123638 - Error: “Connection to Provisioning Services. Please wait…” Appears when Attempting to Boot using BD
• CTX119000 - vDisk Inactive State with Broadcom Network Cards
• CTX132133 - Provisioning Services 6.0 Targets Stop Responding at a Black Screen
  

Disclaimer

Ctx Driver Jobs