During the first maintenance window, after you upgrade View Connection Server, you can also upgrade View Composer, which is hosted on the same virtual or physical machine as vCenter Server.

This procedure provides an overview of the tasks you must perform during the first maintenance window. To complete some of these tasks, you might need step-by-step instructions found in other documents.

Determine when to perform this procedure. Choose an available desktop maintenance window. For information about how much time is required, see the vSphere Upgrade Guide.

Complete the tasks listed in Preparing for Upgrades of View Composer Only.

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 Composer 1.0, which is included with VMware View 3.0, determine whether to let the installer wizard upgrade the View Composer database. You can choose to run the SviConfig command-line utility after the wizard finishes to upgrade the database manually and to create a log of the upgrade.

Note

Upgrading directly from View Composer 1.0 to View Composer 2.7 is not supported. This information is provided only to point out the product behavior that occurs if a database schema upgrade is required.

1

Upgrade View Composer instances.

a

On the virtual or physical machines where View Composer is installed, download and run the installer for View Composer 2.7, which is the version included with VMware View 5.0.

You can download the installer from the VMware Web site.

b

If you are upgrading from View Composer 1.0, when a prompt asks whether you want the wizard to upgrade the database, specify whether you do want the wizard to upgrade the database.

If you are upgrading from View Composer 1.1 or higher, no database schema upgrade is required and no prompt appears.

If a dialog box appears with the message "Database upgrade completed with warnings" you can click OK and safely ignore the message.

c

When the wizard prompts you for the View Composer port number, verify that the port number is set to 18443.

The upgrade changes the port number, which was previously 8443, to 18443 because vCenter Server 4 and later releases require port 8443.

Step-by-step instructions for running the installer appear in the VMware View Installation document.

2

In to View Administrator verify or, if necessary, change the port number used for View Composer.

a

Edit the configuration for the vCenter Server instance and make sure that the View Composer port is set to 18443.

The port number must match the port number specified during the View Composer upgrade.

b

Supply the vCenter Server password.

c

Select the Enable View Composer check box and click OK.

3

Upgrade the View Agent on a parent virtual machine and create a desktop pool for testing purposes.

a

Download and run the View 5.0 View Agent installer on a parent virtual machine.

You can download the installer from the VMware Web site.

b

Create a small linked-clone desktop pool from this virtual machine.

c

Test a virtual desktop from the desktop pool to verify that all the usage scenarios function properly.

For example, create a desktop pool that contains one virtual desktop, and verify that you can use View Client to log in to that desktop.

Do not upgrade View Agent on any other desktop sources.

Step-by-step instructions for running the View Agent installer and creating desktop pools appear in the VMware View Administration document, available by clicking the Help button in View Administrator.

4

Verify that virtual desktops from the test desktop pool work as expected.

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

At your next maintenance window, continue with the VMware View upgrade. See Upgrade View Agent.