For vSphere 4.1.x and 5.0.x, vCenter Server is supported only on 64-bit Windows operating systems. If your current vCenter Server and View Composer server are installed on a 32-bit Windows machine, you need to move to a 64-bit Windows machine as part of the upgrade.

You upgrade View Composer to 2.6 on the source computer first and if necessary also upgrade VirtualCenter Server to vCenter Server 4.0. You then migrate View Composer 2.6 and vCenter Server 4.0 to the destination computer. After making sure that everything is working on the destination computer, you upgrade to View Composer 2.7 and vCenter Server 5.0.

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 That Include vSphere. These tasks include backing up the View Composer database and the vCenter Server database and making a copy of the SSL certificate folder located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter.

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.

Verify that you have the correct license keys for vSphere if you are upgrading Virtual Infrastructure components to vSphere.

If you are currently using VirtualCenter Server 2.5, download and print a copy of the vSphere 4.0 Upgrade Guide. You must upgrade to vCenter Server 4.0 before upgrading to vCenter Server 5.0.

Determine whether to use the vSphere 5.0 data migration tool to perform the vCenter Server migration. This tool is described in the chapter about upgrading to vCenter Server on a different machine and upgrading the existing database, in the vSphere Upgrade Guide.

1

On the existing virtual or physical machine where vCenter Server and View Composer are installed, download and run the installer for View Composer 2.6, which is the version included with VMware View 4.6.

a

Download the installer from the VMware Web site.

b

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

If you are upgrading from View Composer 1.1, the upgrade changes the port number, which was previously 8443, to 18443 because vCenter Server 4 requires port 8443.

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

2

If you are running VirtualCenter Server 2.5, upgrade VirtualCenter Server to vCenter Server 4.0 Update 2 or later, as described in the vSphere 4.0 Upgrade Guide.

You will complete the upgrade to vCenter Server 5.0 on the destination machine.

3

Use your database tools to make new backups of the vCenter Server database and the View Composer database.

4

If you upgraded vCenter Server, restart the View Composer service.

5

In View Administrator verify the port number used for View Composer.

a

Edit the configuration for the vCenter Server and if necessary, change the View Composer port 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.

6

Verify that View Composer is working correctly by creating a test pool.

7

Migrate the RSA key container used by View Composer.

a

On the source machine, open a command prompt and change directories to the directory where the aspnet_regiis program is located.

cd %windir%\Microsoft.NET\Framework\v2.0.xxxxx

You might have several copies of the aspnet_regiis program on the computer. Use the one in the v2.0.xxxxx directory.

b

Type the aspnet_regiis command to save the RSA key pair in a local file.

aspnet_regiis -px “SviKeyContainer” “keys.xml” -pri

This command exports the RSA public-private key pair from the SviKeyContainer container to a keys.xml file.

c

Copy the keys.xml file to the destination machine.

8

On the source machine, stop the VMware VirtualCenter Server service and the VMware View Composer service.

9

If you plan to use the same name and IP address on the new, destination machine, change the host name and IP address of the source machine so that you can use the original name and IP address on the destination machine.

10

If you want to use the vSphere 5.0 data migration tool, run that tool as described in the chapter about upgrading to vCenter Server on a different machine and upgrading the existing database, in the vSphere 5.0 Upgrade Guide.

If you plan to use the vSphere 5.0 data migration tool, complete the tasks for backing up and restoring the vCenter Server database and creating a 64-bit data source name (DSN), as described in the chapter about upgrading to vCenter Server on a different machine and upgrading the existing database, in the vSphere 5.0 Upgrade Guide. Next, perform the procedure described in Use the Data Migration Tool to Migrate to the New Machine.

If you do not plan to use the vSphere 5.0 data migration tool, perform the procedure described in Manually Migrate View Composer to the New Machine.