Administration

Table Of Contents
c In the View Composer Server Settings pane, click Edit.
d Select Do not use View Composer and click OK.
2 Uninstall the VMware Horizon View Composer service from the current machine.
3 Install the VMware Horizon View Composer service on the new machine.
During the installation, configure View Composer to connect to the DSN of the original or new View
Composer database.
4 Configure an SSL server certificate for View Composer on the new machine.
You might be able to copy the certificate that was installed for View Composer on the original
machine, or you can install a new certificate.
5 In View Administrator, configure the new View Composer settings.
a In View Administrator, select View Configuration > Servers.
b On the vCenter Servers tab, select the vCenter Server instance that is associated with this View
Composer service and click Edit.
c In the View Composer Server Settings pane, click Edit.
d Provide the new View Composer settings.
If you are installing View Composer with vCenter Server on the new machine, select View
Composer co-installed with the vCenter Server.
If you are installing View Composer on a standalone machine, select Standalone View
Composer Server and provide the FQDN of the View Composer machine and the user name
and password of the View Composer user.
e In the Domains pane, click Verify Server Information and add or edit the View Composer
domains as needed.
f Click OK.
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.
Prerequisites
Download the .NET Framework and read about the ASP.NET IIS registration tool. Go to
http://www.microsoft.com/net.
Procedure
1 Install the .NET Framework on the physical or virtual machine on which the VMware Horizon View
Composer service associated with the existing database is installed.
View Administration
VMware, Inc. 164