Administration

Table Of Contents
c Click OK.
The virtual machines are deleted from vCenter Server. In addition, the associated View
Composer database entries and the replicas that were created by View Composer are
removed.
d Repeat these steps for each linked-clone desktop pool that was created by View
Composer.
2 Select View Configuration > Servers.
3 On the vCenter Servers tab, select the vCenter Server instance with which View Composer is
associated.
4 Click Edit.
5 Under View Composer Server Settings, click Edit, select Do not use View Composer, and click
OK.
Results
You can no longer create linked-clone desktop pools in this vCenter Server instance, but you can
continue to create and manage full virtual-machine desktop pools in the vCenter Server instance.
What to do next
If you intend to install View Composer on another host and reconfigure Horizon 7 to connect to
the new VMware Horizon View Composer service, you must perform certain additional steps. See
Migrate View Composer Without Linked-Clone Virtual Machines.
Conflicting vCenter Server Unique IDs
If you have multiple vCenter Server instances configured in your environment, an attempt to add a
new instance might fail because of conflicting unique IDs.
Problem
You try to add a vCenter Server instance to Horizon 7, but the unique ID of the new vCenter Server
instance conflicts with an existing instance.
Cause
Two vCenter Server instances cannot use the same unique ID. By default, a vCenter Server unique
ID is randomly generated, but you can edit it.
Solution
1 In vSphere Client, click Administration > vCenter Server Settings > Runtime Settings.
2 Type a new unique ID and click OK.
For details about editing vCenter Server unique ID values, see the vSphere documentation.
Horizon 7 Administration
VMware, Inc. 30