Update Manager upgrade

The last and final step before we can start upgrading ESX hosts, and enjoy all 150 new features, is to upgrade the VMware Update Manager. VMware Upgrade Manager is an essential part of the vSphere 4.1 upgrade process because this is the part that actually performs the upgrade of the ESX hosts.

Start the installation and the previous Update Manager installation is detected.

Check the vCenter server details and supply the service account password to enable the Update Manager to connect to the vCenter server.

The installation detects the current Update Manager database and the used ODBC driver. Check whether the correct database is displayed to avoid upgrading the incorrect database.

Confirm that you want to upgrade your existing database and that you have made a back-up before starting the upgrade process.

Check the ports used by Update Manager. In my home test environment the changes made for the previous installation had been preserved.

This is all the installer want to know before upgrading VMware Update Manager and after a reboot the upgrade process is complete.

The last thing to do is to install and enable the VMware Update Manager plug-in in vCenter server. This was actually the ‘hardest’ part.

After the installation I tried to enable the plug-in but an error appeared stating that no connection with the Update Manager Database could be established. I encountered the exact same message installing vCenter server with Update Manager 4.0 which I solved by running the VMware Update Manager service with the VMware service account instead of Local System. A quick look in the services section of my server learned that this had been undone by the upgrade process but assigning the VMware service account to the Update Manager service did the trick.

Next, ESX host upgrade


Page 1 – vCenter server upgrade
Page 2 – vSphere client upgrade
Page 3 – Update Manager upgrade
Page 4 –  ESX host upgrade