Updating vmware tools without reboot
And to be very clear: what these scripts do is request an automatic postpone of the reboot, not trigger some hidden functionality in VMware Tools not to really reboot after all!
To remove all suspicion, I did a little test on a Windows 2003 virtual machine and upgraded the tools from ESX 3.0.2 to ESX 3.5U2 without rebooting (using the commandline It turned out that these drivers didn't require updating for my specific virtual machine (even after a reboot).
Using the automatic upgrade, if the guest OS is Windows and it require a reboot, this will happen (unattended) after the VMware Tools upgrade procedure.
Anyway I always suggest to plan a VM reboot after VMware Tools upgrade, both for Windows and Linux guests, just because it a simple way to verify that the VM will boot again (remember that there are some changes in drivers and on Linux also in initrd, one of the files used in the bootstrap procedure).
After the couple of reboots that you have to go through with an uninstall and reinstall of VMware Tools you will find that you can now clone VM’s and have them automatically customized. I’ve logged a support call with VMware to address this problem. The Official VMware KB Article [Updated 14/01/2016] After further testing I have narrowed down the problem area to new installs where the complete option is selected, and any upgrades where the complete options was previously selected, or where the VMCI / NSX Guest Introspection Driver is included.
I have been able to successfully clone from a new VM Image that has had a fresh install of Windows 2008 R2 and VMware Tools without the VMCI / NSX Guest Introspection Driver, or where VMware Tools was installed twice / installed and repaired on the same VM, when the complete option was previously selected.
Get-Cluster "Lab Hosts" | Get-VM | Where-Object | Update-Tools -No Reboot In this example I chose my Lab Hosts cluster and updated tools on all VMs that don't have SQL or DB in their names.
This is why the command structure after the /v is enclosed in double quotes.I just upgraded my environments to the latest VMware patches ESXi 6.0 U1b (build 3380124), that has just come out.As you do usually when there is a new hypervisor build you upgrade VMware Tools.If you were manually kicking off the tools upgrade all you need to do is enter the following features into the advanced settings box/s /v"/qn REBOOT=Really Suppress?This is great and causes the tool update to only lose one ping instead of requiring a full restart. Luckily there's a handy one line Power CLI command that can grab a set of VMs and update tools for you.
Search for updating vmware tools without reboot:
Speaking of Power CLI, version 6.5 recently released.