After you prepare the source machine for migration, you must perform certain tasks on the destination machine. If you do not use the vCenter Server data migration tool, you can perform the required tasks manually.

Some of the steps in this procedure would be performed automatically if you use the vCenter Server data migration tool. You might choose not to use the tool if you want to perform the upgrade incrementally so that you can verify at every step that the upgrade is successful. To use the data migration tool instead of performing this procedure, see Use the Data Migration Tool to Migrate to the New Machine.


During this procedure, if you change the host name or IP address of the machine that hosts vCenter Server and View Composer, you might not be able to recompose View Composer desktop pools, even after you upgrade the parent virtual machine to View 5.0 Agent. Change the vCenter Server host name or IP address only if you are willing to recreate View Composer desktop pools after the upgrade.

Complete the required tasks on the source machine. See Prepare the Source Machine for View Composer Migration.

Verify that the Microsoft .NET Framework and the ASP.NET IIS registration tool are installed on the source and destination computers. See the topic in the VMware View Administration document about preparing a Microsoft .NET Framework for migrating RSA keys.

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.

Print or have available the vSphere 4.0 Upgrade Guide and the vSphere 5.0 Upgrade Guide.


On the new, destination machine, set the host name and IP address.

You can set the host name and IP address to the name and IP address originally used on the source machine, or you can use a new host name, IP address, or both.


Migrate the RSA key container used by View Composer.


On the destination 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.


Use the aspnet_regiis command to import the RSA key pair.

aspnet_regiis -pi “SviKeyContainer” “path\keys.xml”

In this command, path\keys.xml is the complete path to the keys.xmlfile.

The tool imports the key pair data into the local key container.


Copy the SSL certificate folder to the destination machine.



Windows 2003 Server

Copy the folder to %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter.

Windows 2008 Server

Copy the folder to %ALLUSERSPROFILE%\VMware\VMware VirtualCenter.


If you use a local database server, use your vendor's database tools to restore or attach the vCenter Server database and the View Composer database.


Create a 32-bit DSN for the vCenter Server 4.0 database.

For more information, see the topic about creating a 32-bit DSN on a 64-bit operating system in the vSphere 4.0 Upgrade Guide.

You need this 32-bit DSN if you install vCenter Server 4.0 rather than 5.0 on the destination machine. The data migration tool installs vCenter Server 5.0 on the destination machine.


Create a 64-bit domain server name (DSN) for vCenter Server and a 64-bit DSN for View Composer.

For instructions, see the vSphere Upgrades document and the VMware View Installation document.


Install vCenter Server 4.0 Update 2 or later.

For instructions, see the vSphere 4.0 Upgrade Guide. In the installer wizard, you will select the 32-bit DNS that you created earlier.


Download and run the installer for the version of View Composer that is included with this release of VMware View.

You can download the installer from the VMware Web site.


Create a test desktop pool and verify that virtual desktops from the test pool work as expected.


Upgrade vCenter Server 4.0 to 5.0, as described in the chapter about upgrading to vCenter Server 5.0, in the vSphere 5.0 Upgrade Guide.


Restart the View Composer service.


If you changed the host name or IP address of the destination machine, log in to View Administrator and update the configuration settings for vCenter Server.


Edit the vCenter Server settings so that the server address uses the correct host name.

If you changed the host name, enter the new name. You can enter an IP address in this field, but using a host name is recommended.


Supply the vCenter Server password.


Deselect the Enable View Composer check box and click OK.

You apply the new vCenter Server settings before you enable View Composer.


After a few moments, edit the vCenter Server settings again to select Enable View Composer and click OK.

View Composer and vCenter Server instances are upgraded and are backward-compatible with existing View 4.0.x, 4.5.x, and 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.

If you upgraded vCenter Server, perform the post-upgrade tasks described in the vSphere Upgrade Guide.

At your next maintenance window, continue with the VMware View upgrade. See Upgrading ESX/ESXi Hosts and Virtual Machines.