There are many reasons both for and against suppressing the reboot process, and I certainly don’t recommend avoiding the reboot for prolonged amounts of time.
However, if you want to do a non-invasive update and let the reboot occur during your corporate patch cycle, the information in this post may appeal to you.
😉 The second method is a little more difficult, but not by much.
It requires that you have installed Power CLI onto your workstation or server.
I did a lot of web searching but could not find anyone with the updated string to put in this box after the VI3 days.
Also, the official VMware documentation seems to ignore any recommended values for the advanced options box.
A client was asking me if it was possible to install the VMware tools inside VM’s without having to reboot them right after.
Historically, one of my biggest little annoyances with a VMware version upgrade has been upgrading VMware tools.Probably the most known, and easiest method, to update VMware Tools is via the v Sphere Client. You will be prompted to choose how you would like the upgrade to take place, either Interactively or Automatically.Along with the Automatic option comes the ability to enter some arguments, listed as “advanced options” in the GUI, that will be passed to the install.I ended up with just simply using the v Sphere Power CLI and a one line command for them to use.
They can adjust the command line with some different parameters to select the scope of VM’s they want to target.A former colleague of mine asked what to put in the box, so I did some digging with procmon to see exactly what the advanced options box does. The string that I have found to work is as follows: I’ve tested this on ESXi 4.1 and ESXi 5.0 with the same results – the VM is updated without a reboot.