Provisioning Server Problem with NC-Series Multifunction and Broadcom NetXteme II Virtual Block Device Network Interface Card Drivers

Document ID: CTX118814 / Created On: Dec 8, 2008 / Updated On: Dec 8, 2008
Average Rating:
View products this document applies to

Symptoms

After installing Citrix Provisioning Server on a client computer that has a Broadcom NetXteme II VBD Network Interface Card and the client Pre-boot Execution Environment (PXE) boots from the Provisioning Server network to build the virtual disk image, a red X appears in the Provisioning Server statistics tray, meaning there is no connectivity to the Provisioning Server.

Background

When a Provisioning Server Client starts, the Network Interface Card driver (NIC) needs to be in the first set of drivers loaded so that it can provide access to the virtual disk over the network. Unlike most of the other Network Interface Card drivers, the Broadcom NetXteme II Virtual Block Device (VBD) NIC has two drivers, the Provisioning Server client will have no knowledge about the second driver, and thus changes must be made to allow both drivers to be in the first set of drivers that get loaded at startup.

This issue also applies to HP ProLiant Blade servers with the following NIC drivers
HP NC-Series Multifunction Driver
HP NC-Series Broadcom Driver

Depending on the type of NIC being used, Citrix recommends that you use the minimum driver version as mentioned below. Make sure to verify the specific driver and supported NIC model.
- HP NC-Series Multifunction Driver for Windows Server 2003, version 3.0.7.0 (21 Mar 07)
- HP NC-Series Broadcom Driver for Windows Server 2003, version 10.24.0.0 (21 Mar 07)

Note: You can also see this behavior with HP NC7781 Gigabit Server Adapter (This is also Broadcom chipset).

Resolution

The following HP tools must be uninstalled first before installing Provisioning Server:

From control panel add/remove program and uninstall

HP insight management Agent
HP System management homepage
HP Version control agent 2.1

From Local Area Network properties

Uninstall or Uncheck, HP network Configuration Utility

To update the NIC drivers, use the following procedure.

1. Make sure the Provisioning Server Client is uninstalled from the client computer and the computer is restarted as instructed.

2. Apply the NIC driver update.

3. Reinstall the Provisioning Server Client.

4. Boot to the client local hard drive.

5. Run regedit32.exe and make the following registry changes.

Caution! Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of the Registry Editor can be solved. Use the Registry Editor at your own risk. Back up the registry before editing it.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\b06bdrv
Add or modify String “Group” Value: NDIS
Add or modify DWORD “Start” Value: 0
Add or modify DWORD “Tag” Value: 2

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ndisuio
Add or modify DWORD “Start” Value: 0
Add or modify DWORD “Tag” Value: 2

Note: For system using a newer NIC driver, version 3.4.10.0 and later.

With the driver version 3.4.10.0, Broadcom uses the traditional Windows Driver Foundation (WDF) driver model; hence a new dependency was added. For Provisioning Server to work with this driver version, additional registry modification is required as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wdf01000
Add or modify String “Group” Value: NDIS
Add or modify DWORD “Start” Value: 0
Add or modify DWORD “Tag” Value: 1

Make the following changes in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\q57w2k:

Add or modify String “Group” Value: NDIS
Add or modify DWORD “Start” Value: 0
Add or modify DWORD “Tag” Value: 2

6. After making these changes, restart the computer. The Provisioning Server status tray will now be active.

This document applies to:

Ardence 3.x
Ardence 4.1
Provisioning Server 4.5
Provisioning Server 5.0