During a recent project, I was at the deployment stage of the PoC. This particular piece of work was using VMware vSphere as the underlying hypervisor, with Citrix XenDesktop as the broker solution and Citrix Provisioning server for the image deployment.
It was a relatively small PoC, just to test out the designs to ensure they would stand up in the pilot phase, and to ensure we had relevant communication ports open.
The install went very smoothly, until I started to create the VHD’s with Provisioning server and boot test machines from that VHD image. Whilst the image conversion completed without any ‘major’ errors in the log (there were a number, but not to worry about) and the image we copied was in perfect health, the VHD would constantly produce a BSOD.
Now, I had already followed Citrix recommendation to ensure the servers and the desktops were making use of the VMXNET3 network adapter. I had also installed the Microsoft hotfix described here to resolve the known issues with the VMXNET drivers to no avail.
After going through a few different troubleshooting steps mentioned in forums (such as removing the MS hotfix above, then removing the PVS software from the target, reinstalling the hotfix the the PVS software) I was starting to become a little frustrated. A colleague then cast his eye over everything when we discovered the the VMware tools were out of date on both the desktop image and the PVS server. Although these had been initially updated after the VM templates were deployed the hosting infrastructure was upgraded from 5.0U2 to 5.1 U1 during that day, carried out by a separate team within the customers IT department. As soon as the tools were updated to the latest revision on both the PVS server and the desktop image, the image was re-imported into the PVS server, and as if by magic the issue was resolved.
Lesson learnt – Keep an eye on VMware tools versions and ensure (where possible) they are up to date and consistent when using Citrix PVS.