In PVS environment, a very common error is the 'BNIStack failed' loop restart error
During target device boot up, a 'BNIStack failed,network stack could not be initialized' occur, then target device had to reboot again, and the next new bootup encounter same error and reboot again and again. This deliver a bad user experience to end user

---

Instructions

There are several potential cause of the issue, administrator should check it one by one Once you have chance to access vDisk OS successfully (no matter use private mode vDisk or directly check the master image which convert the vDisk), open the device manager -> network adapter, make sure view -> show hidden devices is checked, then pay attention to the hidden redundant network adapter

Uninstall the abnormal redundant network adapter and boot again

2.Does not meet system requirement

The top 2 most common mistakes we have ever meet:
I. Use E1000 network type on VMs in VMware environment
II. No necessary Microsoft patch applied within vDisk in VMware environment
Refer to our eDoc: http://docs.citrix.com/en-us/provisioning/7-6/pvs-requirements.html ----> Hypervisor requirements ----> VMware vSphere ESX 4.1 and newer

• ESX 4.x – E1000
• ESX 5.0 and newer – VMXNET3

• Windows 7 and Windows 2008 R2 without service packs — Install Microsoft iSCSI hotfix http://support.microsoft.com/kb/2344941 and restart the VM before installing Provisioning Services target device software.
• Windows 7 and Windows 2008 R2 with service pack 1 – Install Microsoft iSCSI hotfix http://support.microsoft.com/kb/2550978 and restart the VM before installing Provisioning Services target device software.

3.Activate master image OS by 3rd party windows crack software before image

This article describe how to troubleshooting a PVS common error : when target device boot up, an error 'BNIStack failed,network stack could not be initialized' occur