ESX buildnumber is not reflected in the vi client

[Timothy1]

Hi all,

I just updated 3 ESX 4.0 hosts with the latest patches found on https://www.vmware.com/mysupport/download/ . I installed them manually on all hosts via the esxupdate scan|stage|update command. The updates were all succesfully applied. After the 3 updates the buildnumber is reflected in /proc/vmware/version. However if I log on the vCenter server or directly , I see a buildnumber 175625 which should be 193498 (or at least this is the vmkernel release in /proc/vmware/version). Executing vmware -v shows yet another buildnumber namely 171294.

There doesn't seem to be a problem with the patches. However in the future we plan to use vmware update manager in vSphere. What if the version number are not properly interpreted by this tool and it will try to update the host without this being needed?!

Thanks for helping out!

Timothy

[AndreTheGiant]

See:

Andre

[Troy_Clavell]

here too

http://kb.vmware.com/kb/392

[Timothy1]

Hi,

Thanks for helping! I tried esxupdate info command. The version of hostd is the same version that is reflected in the viclient. I guess that is where the viclient is getting the buildnumber. So if this is normal behaviour, I'm happy. If another user could confirm those build numbers, I would be even more happy

Greetings,

Timothy

[Poort443]

I have more or less the same issue, but I doubt it's normal behaviour. My buildnumber is 164009, while it should be 193498. This last number is only in /proc/vmware/version. I checked that all the patches in between are actually installed. I found I had this issue while working with VMware support trying to resolve another issue. They asked me to install the missing patches. If VMware support doesn't know about this, I don't think this is by design. I'm still looking into this trying to find a way to get the right buildnumber in vCenter.

[ajesha008]

Even I have the similar issue

Initially my Build No. is ESX 3.5.0, 163429 but even after applying 91 patches using VUM it shows the same build No. in vSphere Client, Im yet to check this in ESX directly.