If your running both Vsphere 5.1 and Provisioning Services 6.1 you may have come across an issue with your vm’s suffering from a BSoD.
Symptoms of this issue include the master target device booting without issue in private or standard mode, however adding subsequent devices to the image result in a 7b BS0D. Also creating another vm without a hard disk attached but manually assigning the same MAC address to the vm ensures a successful boot.
To start with Provisioning Services supports VMXNET3 vnics and not the old E1000’s so if your still using E1000’s then please change them for VMXNET3’s . Also a few steps will need to be taken to resolve this issue.
Firstly you’ll need to ensure that the issue is the same by looking at the the configuration parameters of the master target device and then the other devices in the collection.
1/ Shut down the master target device and right click the vm and select edit settings.
2/ Click the Options tab and then the General menu item and then the Configuration Parameters button.
3/ Scroll to the item entitled ethernet0.pci and take a note of the value associated with it.
4/ Repeat the steps on the other devices in the collection and if the values are the same then the issue above becomes a little clearer. If they are different try changing the values to match the master target device and try again.
Next you will need to ensure that there are no ghost network cards within the target device disk.
1/ Boot the master target device from its original hard disk from which you created the vdisk.
2/ Start a command prompt in elevated mode and type “set devmgr_show_nonpresent_devices=1”
3/ Then type “Start Devmgr.msc”
4/ Click View within device manager and click on show hidden devices
5/ Expand the network node and if any network cards appear grayed out then they remove them (apart from the RAS device which is required and windows will complain profusely)
6/ Run the Provisioning Services imaging wizard again and recreate the vdisk. Test the vdisk to see if the same issue occurs if so read on if not go and make yourself a cup of tea and congratulate yourself on a job well done.
The issue I’ve encourted requires a microsoft hotfix to be applied to the master target harddisk before installing the target device software and running the imaging wizard This does not mean that you have to rebuild the target harddisk though.
1/ Boot your master target device with the original hard disk and log in.
2/ Run the add/remove wizard and uninstall the Citrix Provisioning Services Target Device software and when it complains open services.msc and stop the Citrix PVS Device Service and hit retry where it will complete the uninstall correctly.
3/ Register and download the microsoft hotfix for the correct version the device is running
Windows 7 and Server 2008 R2 http://support.microsoft.com/kb/2344941
Windows 7 and Server 2008 R2 SP1 http://support.microsoft.com/kb/2550978
Windows Vista (shudder) and Server 2008 http://support.microsoft.com/kb/2487376
4/ Before you run the installation if you have previously run the optimization wizard during a vdisk creation you will need to delve back into services.msc and change the Windows Update service from disabled to manual.
5/ Run the hotfix on the device and then reinstall the Provisioning Services Target Device software and run through the imaging wizard again.
Hopefully you should find that this now cures the BSoD issue for all the subsequent devices you choose to associate with the vdisk.
Author: Dale Scriven
Subscribe to vhorizon
DisclaimerThis blog and any other post made by me on the internet is representative of my views only, they are not the views of my past/current/future employers.