If you spread the upgrade tasks across multiple maintenance windows, you can verify success or discover issues at each phase of the process. During the first maintenance window, you upgrade all the View Connection Server instances in a group that replicates a View LDAP database.

To use the new features of VMware View 5.0, you must upgrade to VMware View 5.0. For a list of the new features included in View 5.0, see the release notes.

Note

This procedure describes an in-place upgrade. To migrate to a different machine, see Upgrade to View Connection Server 5.0 on a Different Machine.

Determine when to perform this procedure. Choose an available desktop maintenance window. The amount of time the upgrade takes depends on the number of View Connection Server instances in the group. Budget 15 minutes to half an hour for each instance.

Complete the tasks listed in Preparing View Connection Server for an Upgrade.

Verify that you have a VMware View license for the new version. VMware View 4.0 and later releases use a new licensing model. The license key has 25 characters. Even if you were not required to purchase an upgrade, you must use a View 4.0 or higher license key.

Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade.

If you are upgrading from View 4.0.x, 4.5.x, or 4.6.x and are unfamiliar with the vdmexport.exe utility, print the instructions for using it from the View Manager 4 Administration Guide, the VMware View 4.5 Administrator's Guide, or the VMware View 4.6 Administration document. You will use this utility to back up the View LDAP database as part of the upgrade procedure.

If you use security servers, familiarize yourself with the instructions on running the installer to create a security server that uses the new security server pairing mechanism. See the VMware View 5.0 Installation document.

If you do not remember the location of the GPO templates on View Connection Server, see the section about Group Policy Objects in the View Manager Administration Guide, for View 4.0.x, the VMware View 4.5 Administrator's Guide, or the VMware View 4.6 Administration document. You must copy these templates as part of the upgrade procedure.

You do not need to make any changes to the configuration of existing load balancers.

1

Stop the service called VMware View Connection Server service on all View Connection Server instances in the group.

View LDAP database corruption can occur if you upgrade a View Connection Server instance while other instances in the same group are running.

Do not stop the VMwareVDMDS service. The VMwareVDMDS service must be running so that the View LDAP database can be upgraded.

2

On the host of one of the View Connection Server instances in the group, run the installer for the VMware View 5.0 Connection Server.

The installer determines that an older version is already installed and performs an upgrade. The installer displays fewer installation options than during a fresh installation.

The View LDAP is also upgraded.

3

Verify that the VMware View Connection Server service restarts after the installer wizard closes.

4

Verify that you can log in to View Connection Server, and click About in View Administrator to verify that the new version is being used.

5

Go to View Configuration > Product Licensing and Usage, click Edit License, enter the View Manager license key, and click OK.

6

Verify that you can log in to a View desktop.

7

Stop the View Connection Server service again.

8

Repeat Step 1 through Step 7 to upgrade each View Connection Server instance in the group.

9

After all servers in the group are upgraded, start the View Connection Server service on all of them.

10

Use the vdmexport.exe utility to back up the newly upgraded View LDAP database.

If you have multiple instances of View Connection Server in a replicated group, you need only export the data from one instance.

11

On one of the upgraded View Connection Server instances, copy the GPO templates and load them into Active Directory.

12

Repeat Step 1 through Step 7 to upgrade each security server.

This release of VMware View includes a security server pairing mechanism.

13

If you use security servers, in View Administrator, go to View Configuration > Servers and remove any duplicate security servers from the list.

The new automated security server pairing mechanism can produce duplicate entries in the Security Servers list if the full system name does not match the name that was assigned when the security server was originally created.

View Connection Server instances are upgraded and are backward-compatible with existing View 4.0.x, View 4.5.x, and View 4.6 View Clients and with desktop sources that have View 4.0.x, 4.5.x, or 4.6.x View Agent installed.

View desktops that were called individual desktops in View 4.0.x deployments are added to manual pools in View 5.0. In the case of individual desktops, the manual pool contains only one desktop.

If the upgrade fails on one or more of the View Connection Server instances, see Create a Replicated Group After Reverting View Connection Server to a Snapshot.

If you are upgrading from View 4.0.x or earlier and the upgrade is successful, install and configure the event database. For instructions, see the VMware View Installation document. If you are upgrading from View 4.5.x or 4.6.x, you probably installed the event database when you installed View 4.5.x or 4.6.x. The event database does not require an upgrade for View 5.0.

Upgrade the other View server components. If you use View Composer, see Upgrade View Composer Only or Upgrade to View Composer 2.7 and vCenter Server 5.0 on a Different Machine. If you use VMware View with Local Mode, see Upgrade View Transfer Server.

If you ever reinstall View Connection Server on a Windows Server 2008 operating system and you have a data collector set configured to monitor performance data, stop the data collector set and start it again.