according to VMware Support you need to apply 2 patches if you are using ESX 3.5 Update 2 before you can continue using your Update Manager Host Upgrade Baseline using the ESX-4.1.0-update02-502767.iso.
This came to my surprise and delayed my upgrade project as I had to apply too patches using "esxupdate" before I could use the previosuly created Upgrade Baseline.
Thie VMware KB article and the video and the Update Manager does not inlcude any of this important facts! This needs to be updated
this does look very easy and I actually created the exact same baseline for upgrading 2 ESX 3.5 Update 2 Hosts (238493) and everything looked OK at the end until I attached the baseline to my two ESX 3.5 Hosts and ran a compliance scan on them. It then showed me that the upgrade were non compliant! A call to VMware Support revealed that this means that the hosts are not in compliance with the created Upgrade Baseline. I also was told that I need to apply 2 ESX patches before I can run my upgrade
I'd like to know if the virtual machines running are affected by the host bouncing in and out of maintenance mode during the upgrade... in other words, is there any downtime on the VMs during upgrade?
@cjohnson596 When the host is in maintenance mode you will not be able to run any VM's on it. If you have the ability to vmotion onto another host, you should do that and upgrade just one host in your cluster at a time. If you just have the one host, you are looking at VM downtime for this upgrade.
according to VMware Support you need to apply 2 patches if you are using ESX 3.5 Update 2 before you can continue using your Update Manager Host Upgrade Baseline using the ESX-4.1.0-update02-502767.iso.
This came to my surprise and delayed my upgrade project as I had to apply too patches using "esxupdate" before I could use the previosuly created Upgrade Baseline.
Thie VMware KB article and the video and the Update Manager does not inlcude any of this important facts! This needs to be updated
DaRealHess 2 weeks ago
this does look very easy and I actually created the exact same baseline for upgrading 2 ESX 3.5 Update 2 Hosts (238493) and everything looked OK at the end until I attached the baseline to my two ESX 3.5 Hosts and ran a compliance scan on them. It then showed me that the upgrade were non compliant! A call to VMware Support revealed that this means that the hosts are not in compliance with the created Upgrade Baseline. I also was told that I need to apply 2 ESX patches before I can run my upgrade
DaRealHess 2 weeks ago
Great video, saved me a good deal of time and headache!
natemcintyre 8 months ago
I'd like to know if the virtual machines running are affected by the host bouncing in and out of maintenance mode during the upgrade... in other words, is there any downtime on the VMs during upgrade?
cjohnson596 1 year ago
@cjohnson596 When the host is in maintenance mode you will not be able to run any VM's on it. If you have the ability to vmotion onto another host, you should do that and upgrade just one host in your cluster at a time. If you just have the one host, you are looking at VM downtime for this upgrade.
Strykenine 1 year ago
Why did you discontinue the VMware Host Update Utility? No one wants to use the convoluted piece of garbage that is VMware update Manager :(
Bring back the easy and SIMPLE to use VMware Host Update Utility!
EricZBA 1 year ago 3
Nicely done!
ernestgwilsonii 1 year ago
You can use vihostupdate. Check out the link in the details section of this video. There's a video for how to do it.
VMwareKB 1 year ago
nice vid,
how to i upgrade esxi (installable) from 4.0.0 to 4.1?
i idont have vsphere software as shown and i cant seem to get a trial?
cs512tr 1 year ago