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.

You must complete the upgrade process in a specific order. If you do not complete each upgrade stage before moving on, you can lose data and server access. Order is also important within each upgrade stage.

Note

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. Because VMware View 5.0 includes components that were not available in releases earlier than View 4.5, some of the tasks might be installation rather than upgrade tasks.

1

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.

2

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.

3

If some of your end users are using View 4.0.x Client with Offline Desktop or View 4.5 Client with Local Mode, ask them to check in their View desktops.

4

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

5

If you are upgrading from View 4.0.x, install and configure an event database that View Administrator 5.0 uses for displaying some of the View Connection Server events that were previously recorded only in logs. See the VMware View 5.0 Installation document.

If you are upgrading from View 4.5, you have probably already installed this database. You do not need to upgrade the View 4.5 database schema. View 5.0 does not require any database schema changes.

6

For the View Client with Local Mode component, upgrade or install and configure one or more View Transfer Server instances.

Current Version

Action

View 4.0.x

Install Transfer Server instances. See the VMware View 5.0 Installation document.

View 4.5 and 4.6

Upgrade Transfer Server instances. 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.

View Client with Local Mode is the fully supported feature that in earlier releases was an experimental feature called View Offline Desktop.

7

Upgrade View Composer on the existing host or, if you are also upgrading to vSphere 5.0, migrate to a new machine. See Upgrade to View Composer 2.7 and vCenter Server 5.0 on a Different Machine.

8

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.

9

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

10

Upgrade the VMware View software that runs on end users' client devices. See Upgrade View Clients and Upgrade Offline Desktop Clients to View Client with Local Mode.

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.