4.6

Table Of Contents
Remove View Composer from View Manager
You can remove the connection between View Manager and the View Composer service installed in a vCenter
Server instance. When you do so, View Manager no longer manages the linked-clone desktops created by View
Composer in the vCenter Server instance.
Before you disable the connection to View Composer, you must remove from View Manager all the linked-
clone desktops that were created by View Composer. After the connection to View Composer is disabled, View
Manager cannot provision, manage, or delete the linked clones. View Manager does not force you to delete
the linked clones. You must take this action on your own.
Procedure
1 Remove the linked-clone pools that were created by View Composer.
a In View Administrator, click Inventory > Pools.
b Select a linked-clone pool and click Delete.
A dialog box warns that you will permanently delete the linked-clone pool from View Manager. 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.
c Click OK.
d Repeat these steps for each linked-clone pool that was created by View Composer.
2 Click View Configuration > Servers.
3 In the vCenter Servers panel, select the vCenter Server instance in which View Composer is installed.
4 Click Edit.
5 In the View Composer Settings panel, deselect Enable View Composer and click OK.
You can no longer create linked-clone desktops in this vCenter Server instance, but you can continue to create
and manage full virtual-machine desktop pools in the vCenter Server instance.
If linked-clone desktops were not deleted before you disabled the connection to View Composer, you can try
enabling the connection to View Composer, deleting the linked clones, and disabling the connection to View
Composer again. For details about enabling View Composer, see “Configure View Composer Settings for
vCenter Server,” on page 15.
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 View Manager, 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.
VMware View Administration
16 VMware, Inc.