To use View Composer, you must configure settings that allow Horizon 7 to connect to the View Composer service. View Composer can be installed on its own separate host or on the same host as vCenter Server.
There must be a one-to-one mapping between each View Composer service and vCenter Server instance. A View Composer service can operate with only one vCenter Server instance. A vCenter Server instance can be associated with only one View Composer service.
After the initial Horizon 7 deployment, you can migrate the View Composer service to a new host to support an expanding or changing Horizon 7 deployment. You can edit the initial View Composer settings in Horizon Console, but you must perform additional steps to ensure that the migration succeeds.
Prerequisites
- Verify that you created a user in Active Directory with permission to add and remove virtual machines from the Active Directory domain that contains your linked clones. See Create a User Account for View Composer AD Operations.
- Verify that you configured Horizon 7 to connect to vCenter Server. To do so, you must complete the vCenter Server Information page in the Add vCenter Server wizard. See Add vCenter Server Instances to Horizon 7 in Horizon Console.
- Verify that this View Composer service is not already configured to connect to a different vCenter Server instance.
Procedure
What to do next
Configure View Composer domains.
- If the View Composer instance is configured with a signed TLS certificate, and Connection Server trusts the root certificate, the Add vCenter Server wizard displays the View Composer Domains page.
- If the View Composer instance is configured with a default certificate, you must first determine whether to accept the thumbprint of the existing certificate.