I installed all of the patches on my ESX 3.0.1 servers. When I do a vmware -v at the service console it shows the correct version: build number 44686.
However, if I connect in via the VI Client to either Virtual Center or directly to the ESX servers it says build number is: 329823.
Why is this?
44686 is correct - you should see 42829 in VC. Patching ESX 3.x has been/become a challenge. ![]()
DB
You might have to restart the mgmt-vmware service to get it to display the updated build number.
I have restarted all ESX servers and the Virtual Center server several times since I have seen this.
So VC should read 42829? Is that a typo?
No thats not a typo.
Try downloading and reinstalling the VI client (sometimes this helps)
Okay, thanks. Actually I have already tried that with no luck. When I first posted, I posted incorrectly. If I am within Virtual Center and highlight the ESX server, it is listed as build 39823. Is this the latest version? Why is it different from when I do a vmware -v at the service console of the ESX server (shows 44686)?
I don't know the reason for this but I guess that it is related to the following.
Sometimes vmware -v reports a different version than cat /proc/vmware/version
I bet cat /proc/vmware/version displays 39823 too.
Yep, it's not a bug, it's a feature. Please see this thread, where I got into the painstaking detail of why this happens: http://www.vmware.com/community/thread.jspa?messageID=613377򕰁
When I was at VMware in late May, I actually had a chance to sit down and chat with some of the VC developers and lay out a (long) list of concerns, frustrations, and ideas.. This was one of the things I brought up where they kind of scratched their heads about until I gave them the condensed version of the issue.. So, hopefully that is something that is being worked on resolving...
Very timely kb article! http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1001179
