Administration

n Migrate View Composer Without Linked-Clone Virtual Machines
If the current VMware Horizon View Composer service does not manage any linked-clone
virtual machines, you can migrate View Composer to a new physical or virtual machine
without migrating the RSA keys to the new machine. The migrated VMware Horizon View
Composer service can connect to the original View Composer database, or you can prepare a
new database for View Composer.
n Prepare a Microsoft .NET Framework for Migrating RSA Keys
To use an existing View Composer database, you must migrate the RSA key container
between machines. You migrate the RSA key container by using the ASP.NET IIS registration
tool provided with the Microsoft .NET Framework.
n Migrate the RSA Key Container to the New View Composer Service
To use an existing View Composer database, you must migrate the RSA key container from
the source physical or virtual machine on which the existing VMware Horizon View Composer
service resides to the machine on which you want to install the new VMware Horizon View
Composer service.
Guidelines for Migrating View Composer
The steps you take to migrate the VMware Horizon View Composer service depend on whether
you intend to preserve existing linked-clone virtual machines.
To preserve the linked-clone virtual machines in your deployment, the VMware Horizon View
Composer service that you install on the new virtual or physical machine must continue to use the
existing View Composer database. The View Composer database contains data that is required to
create, provision, maintain, and delete the linked clones.
When you migrate the VMware Horizon View Composer service, you can also migrate the View
Composer database to a new machine.
Whether or not you migrate the View Composer database, the database must be configured on
an available machine in the same domain as the new machine on which you install the VMware
Horizon 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 VMware Horizon
View Composer service, you must migrate the RSA key container that was created by the original
VMware Horizon View Composer service. You must import the RSA key container to the machine
on which you install the new service.
If the current VMware Horizon View Composer service does not manage any linked-clone virtual
machines, you can migrate the service without using the existing View Composer database. You
do not have to migrate the RSA keys, whether or not you use the existing database.
Note Each instance of the VMware Horizon View Composer service must have its own View
Composer database. Multiple VMware Horizon View Composer services cannot share a View
Composer database.
Horizon 7 Administration
VMware, Inc. 177