You can remove the connection between View Manager and the View Composer service that is associated with a 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. View Manager prevents you from removing View Composer if any associated linked clones still exist. After the connection to View Composer is disabled, View Manager cannot provision or manage new linked clones.


Remove the linked-clone pools that were created by View Composer.


In View Administrator, click Inventory > Pools.


Select a linked-clone pool and click Delete.

A dialog box warns that you will permanently delete the linked-clone pool from View Manager. If the linked-clone desktops are configured with persistent disks, you can detach or delete the persistent disks.


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.


Repeat these steps for each linked-clone pool that was created by View Composer.


Click View Configuration > Servers.


In the vCenter Servers tab, select the vCenter Server instance with which View Composer is associated.


Click Edit.


Under View Composer Server Settings, click Edit, select Do not use 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 you intend to install View Composer on another host and reconfigure View Manager to connect to the new View Composer service, you must perform certain additional steps. See Migrate View Composer Without Linked-Clone Desktops.