When a Network Driver Interface Specification (NDIS) filter driver from third party product is installed on the master target device (before the image process), a vDisk is not attached and the Provisioning Services agent icon on the system tray shows a red X. This causes an inability to create a new image.
The load order of the NDIS filter driver from third party product might interfere with the connection to Provisioning Services. The Start type of the driver must be 0x0(Boot) to utilize Provisioning Services properly. Otherwise, Provisioning Services driver cannot send and receive packets at the time of OS start.
Important! Citrix recommends you to consult the third party before trying the following solution.Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
--- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\(driver name)] "Type"=dword:00000001 "Start"=dword:00000000 "ErrorControl"=dword:00000001 "Tag"=dword:00000018 … "Group"="NDIS" "NdisMajorVersion"=dword:00000006 "NdisMinorVersion"=dword:00000000 ---Note: It is a necessary condition that Start type is set to 0x0(Boot). However, other factors in network driver of third party product could also cause an interference with Provisioning Services. See also CTX117395 - How to Make the Provisioning Services Server Client Coexist with Third-party Network Drivers;
For I/O to vDisk, Provisioning Services network driver is loaded at the time of Operating System (OS) boot, and sends and receives packets. Most of NDIS filter drivers are loaded at Kernel initialization after OS start process. This interferes with the connection to Provisioning Services server and causes the failure of vDisk attachments.