Jump to content
Welcome to our new Citrix community!
  • 0

VMware Tools 11.0.5 installation failing


2 answers to this question

Recommended Posts

  • 1

We have successfully performed VMTools updates on our PVS images using these procedures:


Adapted from https://www.helient.com/2017/10/updating-vmware-tools-pvs-secrets-revealed/


  1. Create Merged Base and place in Maintenance
  2. Start update machine and log onto the console
  3. Edit the machine settings and add a second network card, an E1000 specifically. E1000 is a generic virtual NIC and requires no special driver.
  4. Return to the console and confirm the new NIC was added
  5. Power down the machine
  6. Change the update machine properties in the PVS console to reflect the MAC Address of the new E1000 card
  7. Edit Settings and remove the VMXNet3 NIC (PVS will not start with two NICs)
  8. Boot the VM which will use the E1000 NIC to stream the image
  9. Edit Setting and add a VMXNet3 NIC to ensure that the driver gets updated with the VMTools update
  10. Upgrade VMTools as normal
  11. Shutdown the VM
  12. Edit Settings and remove the E1000 NIC
  13. Change the update machine properties in the PVS console to reflect the MAC Address of the VMXNet3 card
  14. Start the VM
  15. Ensure there were no ghost NICs left behind:
    • From an Administrator CMD Prompt
    • Open Device Manager and set Show Hidden Devices
    • Expand Network Adapters
    • Uninstall any E1000
    • Intel® PRO/1000 MT Network Connection
  16. Continue with normal move of vDisk image to test
  • Like 1
Link to comment
  • 0

hey mate, I'm not sure if you're posting this just to let other people know or if this a question where you need help but I'm going to assume the latter.


This is kind of normal and expected behaviour since you switched your existing network card from VMXNET3 to a complete new one (E1000). You basically switched your boot medium (in case of PVS that is the network card) to a device that is not (yet) known inside your master build, pulling the virtual 'hard drive' under Windows feet during the midst of the boot process. So during the BIOS phase your VM machines find the bootstrap and load but right after -upon entering windows phase- the new boot device is not (yet) known in the windows registry so you literally "cut the lifeline" under Windows feet.


Therefore the solution is: Whenever you make such a significant change to the infrastructure you must perform the one-time operation of converting the .VHDX file from your PVS server to a vmware native format on the VMware server's local storage so you can boot from it as a local attached Hard drive in order to be able to register the new hardware in the registry of your master build at least once. So after the conversion make a VM machine where you boot from your converted master image as a local HD.  After entering Windows at least once this way, shut the VM down again and convert your image back to a new .VHDX file on the PVS server. 


After this one-time operation where you basically just entered the new hardware into the Windows registry you're good to go. Booting will no longer give bluescreens nor will it in all future updates of this master build.


 I hope that explains

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...