VMware Cloud Community
syn3rgy
Contributor
Contributor

isolation.tools.guestinitiatedupgrade.disable = "FALSE"

Hi All,

I have recently upgrade my vsphere 5 environment to the latest release vsphere 5 update 1 and updated all the ESXi Host with the latest updates from VMware.

One of the updates were Vmware Tools. All my VM's are showing mixed information now. ie.

1) VM1 - shows VMware tools up to date yet it is running 8.6.0 and not 8.6.5

2) VM2 - Vmware tools not up to date, running version 8.6.0

Now, when i try to upgrade the vmware tool on each vm, i am getting Update failed as shown below.

vmwaretoolserror.PNG

Here is one showing the "up to date status" yet running the old version: (unable to click the update button, greyed out)

falseinfo.PNG

I understand that there is a fix to download each .vmx file and edit it, however, if you have 10000 vms, i dont think this is viable.

Are there any other suggestions or fixes or is anyone else having the same problem?

Thank you

Rob

Reply
0 Kudos
3 Replies
VMjkasalVM
Contributor
Contributor

I ran in to the exact same issue yesturday while updating VMware tools. The only fix I found was probably the same you found which has a VMware KB article dedicated to it found here.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200729...

The cause only states "This error occurs because the virtual machine is missing a necessary setting." What is the missing setting???

This must be a bug or over looked compatability issue. It seems that this issue has only popped up recently in my enviornmennt. It is also only occuring on VMs that were created in vSphere 4 (4.1) and migrated to esxi 5.0 GA hosts. And another curve ball, not all VMs are experiancing this in my enviornment. Only a few thus far.

I know vsphere 5.0 up1 was released last thurdsday (March 15, 2012) maybe there is a fix there. I have not read the release notes in great detail yet, but I don't see any mention of this as a known issue or resolved issue.

Release notes for 5.0 up1: http://www.vmware.com/support/vsphere5/doc/vsp_esxi50_u1_rel_notes.html#resolvedvmwaretools

Not a solution, but your not alone atleast

Reply
0 Kudos
syn3rgy
Contributor
Contributor

This is really strange, mine is happening on all my Virtual machines, I upgraded this week from v5 to v5 up1.

So far, instead of editing each .vmx file, i have enabled to VM's to check and upgrade tools during power cycle. Though, this is a pain as i do not want to have to reboot each VM, let VM tools install and reboot the system again (I know the reboots happen automatically after the install though, this is additional down time.)

I hope the little bit above re enabling check and upgrade tools helps other people instead of editing the .vmx file. I am really hoping that someone (VMware) can come up with a proper solution.

Reply
0 Kudos
adelisa
Enthusiast
Enthusiast

Hi syn3rgy ,

Please To perform a silent, non GUI with suppressed reboot VMware Tools installation

in a Windows guest operating system . Run the command:

setup.exe /S /v"/qn REBOOT=R"

" Affirmation without discipline is the beginning of delusion."
Reply
0 Kudos