5.2

Guidelines for Migrating View Composer
The
steps you take to migrate the View Composer service depend on whether you intend to preserve existing
linked-clone desktops.
To preserve the linked-clone desktops in your deployment, the View Composer service that you install on the
new computer 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 View Composer service, you can also migrate the View Composer database to a new
computer.
Whether or not you migrate the View Composer database, the database must be configured on an available
computer in the same domain as the new computer on which you install the 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.
If the current View Composer service does not manage any linked-clone desktops, 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 View Composer service must have its own View Composer database. Multiple
View Composer services cannot share a View Composer database.
Migrate View Composer with an Existing Database
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.
Follow the steps in this procedure when you migrate View Composer in any of the following directions:
n
From a vCenter Server computer to a standalone computer
n
From a standalone computer to a vCenter Server computer
n
From a standalone computer to another standalone computer
n
From a vCenter Server computer to another vCenter Server computer
When you migrate the View Composer service, you can also migrate the View Composer database to a new
location.
For example, you might need to migrate the View Composer database if the current database is located
on a vCenter Server computer that you are migrating as well.
When you install the View Composer service on the new computer, you must configure the service to connect
to the View Composer database.
Prerequisites
n
Familiarize yourself with the View Composer migration requirements. See “Guidelines for Migrating
View Composer,” on page 363.
n
Familiarize yourself with the steps for migrating the RSA key container to the new View Composer Service.
See “Prepare a Microsoft .NET Framework for Migrating RSA Keys,” on page 366 and “Migrate the RSA
Key Container to the New View Composer Service,” on page 366.
n
Familiarize yourself with installing the View Composer service. See "Installing View Composer" in the
VMware Horizon View Installation document.
Chapter 15 Maintaining View Components
VMware, Inc. 363