Upgrading an enterprise VMware View deployment involves several high-level tasks. Upgrading is a multistage process in which procedures must be performed in a particular order.

During an upgrade to View 5.1, View does not support View Composer provisioning and maintenance operations, local mode operations, or View Transfer Server publish operations. Operations such as provisioning and recomposing linked-clone desktops, checking out or checking in desktops, and publishing View Composer base images are not supported during the transitional period when any View servers are still running the earlier version. You can successfully perform these operations only when all instances of View Connection Server, View Composer, and View Transfer Server have been upgraded to View 5.1.

You must complete the upgrade process in a specific order. Order is also important within each upgrade stage.


This overview relates to upgrades for major, minor, and maintenance releases. For information about patches, see Applying VMware View Patches.

How many of the following tasks you need to complete depends on which components of VMware View you use in your deployment.


On the physical or virtual machines that host View Connection Server instances, make backups and record various configuration and system settings. See Preparing View Connection Server for an Upgrade.


On the physical or virtual machines that host View Composer and vCenter Server, make backups and temporarily halt certain scheduled tasks. See Preparing vCenter Server and View Composer for an Upgrade.

For details about which versions of VMware View are compatible with which versions of vCenter Server and ESX/ESXi, see the VMware Product Interoperability Matrix at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.


If you use View 5.1 security servers, perform the tasks in Prepare to Upgrade or Reinstall a Security Server.


Upgrade View Connection Server on the existing host or migrate to a new machine. See Upgrade View Connection Servers in a Replicated Group.


After you upgrade a View Connection Server instance to View 5.1, you cannot downgrade that instance to an earlier version. After you upgrade all View Connection Server instances in a replicated group, you cannot add another instance that runs an earlier version of View.


If you use View security servers, upgrade to 5.1, see Upgrade View Security Server.


Upgrade View Composer on an existing Windows Server 2008 host or, if you are running View Composer 2.6 on Windows Server 2003, migrate to a new machine. See Upgrade View Composer.


If you are also upgrading vSphere components, upgrade vCenter Server. See Upgrade vCenter Server.


For the View Client with Local Mode component, upgrade or install and configure one or more View Transfer Server instances. See the VMware View 5.1 Installation document or, for upgrades, see Upgrade View Transfer Server.

This server transfers data that end users need to check out and run View desktops locally on their client systems.


If you are also upgrading vSphere, upgrade the ESXi hosts and virtual machines. See Upgrade ESX/ESXi 4.0.x, 4.1.x, or 5.0.x Hosts and Their Virtual Machines.


Upgrade the VMware View software that runs on the physical or virtual machines that are used as desktop sources, as full-clone desktops in a pool, and as individual desktops in a manual pool. See Upgrade View Agent.


Use the newly upgraded virtual desktop sources to create upgraded pools of View desktops. See Upgrade View Composer Desktop Pools.


Upgrade the VMware View software that runs on end users' client devices. See Upgrade View Clients and Upgrade View Local Mode Clients.

Because certain commands can simultaneously upgrade more than one stage, VMware recommends that you thoroughly understand the irreversible changes at each stage before you upgrade your production environments.