This example scenario shows how you can use vCenter Update Manager to simplify the host and virtual machine upgrade process and minimize downtime in environments that include host clusters.

These are the prerequisites for this scenario:

You must have VirtualCenter 2.5 or higher or vCenter Server 4.0.

You must have vCenter Update Manager.

All your hosts must be ESX 3.5/ESXi 3.5 or higher.

The following list of tasks provides a high-level overview of the upgrade process.


Upgrade vCenter Server 2.5 or higher to vCenter Server 4.1.


Starting with vCenter Server 4.1 Update 1, you cannot upgrade vCenter Server from releases prior to VirtualCenter Server 2.5 Update 6.


Make sure your database is compatible with vCenter Server 4.1. See the vSphere Compatibility Matrixes on the VMware vSphere documentation Web site.


Make sure that you have the required permissions to perform this procedure. See Database Prerequisites.


Take a full backup of the vCenter Server database. See your database documentation.


Back up the vCenter Server SSL certificates.

The downtime required for this upgrade is based on the amount of data in the database. During this time, you cannot perform provisioning operations, such as cloning or creating virtual machines.

After the upgrade, the hosts are automatically connected to vCenter Server 4.1 if you select that option during the upgrade process. VMware High Availability (HA) and VMware Distributed Resource Scheduler (DRS) clusters are automatically reconfigured. (Check to ensure that the automatic reconfiguration is successful. In some cases, you might need to reconfigure the clusters manually.)

vCenter Server 4.1 is supported only on 64-bit systems. The upgrade method you use depends on what version of VirtualCenter or vCenter Server you are upgrading and on what system it is currently installed. For a detailed description of the upgrade procedure, see Preparing for the Upgrade to vCenter Server and Upgrading to vCenter Server 4.1.


Run the vCenter Agent Preupgrade Check tool.


Install the vSphere Client.

You can install the vSphere Client on the same machine with your previous version of the vSphere Client. You must have the previous version of the vSphere Client to connect to previous versions of vCenter Server and ESX/ESXi.

For a detailed description of the procedure, see Upgrade the vSphere Client.


If your environment has vCenter Converter, upgrade it to the latest version.


If your environment has vCenter Guided Consolidation, complete the consolidation plan and then upgrade it to the latest version.


Upgrade vCenter Update Manager to vCenter Update Manager 4.1.


Use vCenter Update Manager to upgrade ESX 3.5/ESXi 3.5 or higher hosts to ESX 4.1/ESXi 4.1.

vCenter Update Manager puts the host into maintenance mode before upgrading the host. The downtime for the procedure depends on the network speed and the server boot time.

In case of upgrade failure, vCenter Update Manager supports rollback to the previous release.

For a detailed description of the procedure, see the vSphere Update Manager Administration Guide.


Use vCenter Update Manager to upgrade your virtual machines. vCenter Update Manager ensures that the VMware Tools upgrade and the virtual hardware upgrade happen in the correct order to prevent loss of your network connectivity. vCenter Update Manager also performs automatic backups of your virtual machines in case you need to roll back after the upgrade. You can upgrade hosts in clusters without powering off the virtual machines if Distributed Resource Scheduler is available for the cluster.


Upgrade your product licenses:


Either your new license keys are sent to you in email, or you get them using the license portal.


Apply the new license keys to your assets using vCenter Server.