I am attempting to upgrade our ESXi 5.0 to Update 2. I have tried essentially all upgrade options.
1) tried with VUM it would show it is compliant but the build number still displays 1117897.
2) tried booting with the .iso (VMvisor-Installer-5.0.0.update02-914586.x86_64.iso) I would select the Upgrade option it would go through its upgrade process prompting me to reboot and comes up with "VMware ESXi 5.0.0 (VMKernel Release Build 1117897) versus 914586.
Any thoughts.. ? Hints or tips?
You are already running on ESXi 5.0 U2 after that few patches have been released and the latest one is 1117897 along with the ESXi 5.0 U2 and other patch which was recently released.
So no worries...continue with that...
simple analysis from my end just compare the build number 1117897 > 914586
VMware ESX hosts are patched according to a model where each patch bundle only updates a few components of the ESX installation at a time. Not all components of the installation are upgraded
As a result, the ESX installation can have different components at different build numbers, depending upon which patch bundles have been applied.
If you wanna dig deep into the details of the build on your host.
check this KB.
Well ok that is odd however I thought one of the features (that I was highly interested in) is that when you move a svmotion a VM the name (folder and under lying files would change to the new vm name) I do not see that happening.. Tried it hot and cold.
storage vmotion generally does not change the VM name, it is just moving your VM files from one datastore to another... probably you are talking about cloning where we can specify new VM name I guess
Oh if your looking that feature, it actually not enable by default as soon as you upgrade.
To fully resolve this issue after updating the vCenter Server, add the
provisioning.relocate.enableRename advanced parameter to vCenter Server and set its value to
Note: The default value for
Check this KB for details VMware KB: vSphere 5.x Storage vMotion does not rename virtual machine files on completing migration...
Yes I agree, as per Duncan link it says so, But as per the VMware KB: vSphere 5.x Storage vMotion does not rename virtual machine files on completing migration...its not enabled as default,
and check this post by Duncan Storage vMotion does not rename files?. which was later than the original post
Not according to this and the links within it..
If you check the link Storage vMotion does not rename files? he has clearly mentioned in the first line of the blog that "A while back I posted that 5.0 U2 re-introduced the renaming behavior for VM file names"