vmware-vmupgrade tools upgrade

[mkramer1]

We have a host with VMs that show to be ToolsOld within Virtual Center. We shutdown all host and ran the following:

C:\Program Files\VMware\VMware VirtualCenter 2.0>vmware-vmupgrade.exe -u z08abat -h "/Server Farm Distribution (SFD 1&2)/3.0 Hosts/Sandbox/tcesx25p.fnb.fnni.com"

This ran and gave the following:

/Server Farm Distribution (SFD 1&2)/3.0 Hosts/Sandbox/tcesx25p.fnb.fnni.com:TCMLK2: tools are up-to-date. Skipping tools upgrade

The tools show as old within Virtual Center but does not upgrade via the vmware-vmupgrade tool.

Can you tell us what it compares to determine when vm tools are old and if there is a something needed to have this work for a mass push to update tools?

Thanks

[Texiwill]

Hello,

How old are the vmware-tools in the VM? If they are from ESX v2.5.x or lower you first have to upgrade the tools by hand so that the autoupgrader will work.

Best regards,

Edward

[mkramer1]

We upgraded from 3.01 to 3.02. All tools are 3.0 or higher.

[Texiwill]

Hello,

Then the vmware-upgrader should work... Can you upgrade the tools by hand? Did you check the box that says allow auto-updates?

Best regards,

Edward

[mkramer1]

I can update manually with the check box to run automatically checked. It updates fine.

To me the issue doesn't rely on whether it can update or not but how it determines whether it needs updating. The vmware-upgrader seems to determine that tools is up-to-date when in fact it is not.

[Texiwill]

Hello,

I would agree there is an issue with vmware-upgrader.... I would also open a case with your vmware support agent. It sounds to me like a bug....

Best regards,

Edward

[daniel-san]

Hi

I have the same issue... If any one opens a case, please post the answer.

Best regards

Daniel

[OM4EVER]

Same issue as well not sure why it does not do the upgrade. It comes back with message "tools are up-to-date. Skipping tools upgrade"

I'll be calling support on this and let you know thanks

[Craig_S]

Did you ever find a resolution to this problem? I just upgraded from 3.0.2. to 3.5 and have the same problem when trying to run the vmware-vmupgrade.exe tool. Any info would be greatly appriciated.