In some situations, you might need to migrate a View Composer service to a new Windows Server computer. For example, you might migrate View Composer and vCenter Server to a new ESXi host or cluster to expand your View deployment. In addition, View Composer and vCenter Server do not have to be installed on the same Windows Server computer.

You can migrate View Composer from the vCenter Server computer to a standalone computer or from a standalone computer to the vCenter Server computer.

The steps you take to migrate the View Composer service depend on whether you intend to preserve existing linked-clone desktops.

When you migrate View Composer to another computer, if you intend to preserve your current linked-clone desktops, the new View Composer service must continue to use the existing View Composer database.

If the current View Composer service does not manage any linked-clone desktops, you can migrate View Composer to a new computer without migrating the RSA keys to the new computer. The migrated View Composer service can connect to the original View Composer database, or you can prepare a new database for View Composer.

To use an existing View Composer database, you must migrate the RSA key container between computers. You migrate the RSA key container by using the ASP.NET IIS registration tool provided with the Microsoft .NET Framework.

To use an existing View Composer database, you must migrate the RSA key container from the source computer on which the existing View Composer service resides to the computer on which you want to install the new View Composer service.