In some situations, you might need to migrate a View Composer service to a new computer. You can continue to use the existing View Composer database.

For example, you might migrate a vCenter Server instance to a new ESX host or cluster to expand your deployment or recover from a hardware failure. To preserve your linked-clone desktops, you must also migrate the View Composer service installed with vCenter Server.

To migrate the View Composer service, you uninstall the service on the old computer and install the service on the new computer. For installation instructions, see the VMware View Installation document.

The existing View Composer database must be configured on an available computer in the same domain as the computer on which you install the new View Composer service, or on a trusted domain.

View Composer creates RSA key pairs to encrypt and decrypt authentication information stored in the View Composer database. To make this data source compatible with the new View Composer service, you must migrate the RSA key container that was created by the original View Composer service. You must import the RSA key container to the computer on which you install the new service.


Each instance of the View Composer service must have its own View Composer database. Multiple View Composer services cannot share a View Composer database.