To support View Composer, you should follow certain best practices when you install and configure vCenter Server, ESX/ESXi, and other vSphere components.

These best practices let View Composer work efficiently in the vSphere environment.

After you create the path and folder information for linked-clone virtual machines, do not change the information in vCenter Server. Instead, use View Administrator to change the folder information.

If you change this information in vCenter Server, View Manager cannot successfully look up the virtual machines in vCenter Server.

Make sure that the vSwitch settings on the ESX/ESXi host are configured with enough ports to support the total number of virtual NICs that are configured on the linked-clone virtual machines that run on the ESX/ESXi host.

When you deploy linked-clone desktops in a resource pool, make sure that your vSphere environment has enough CPU and memory to host the number of desktops that you require. Use vSphere Client to monitor CPU and memory usage in resource pools.

In vSphere 5.1 and later, a cluster that is used for View Composer linked clones can contain more than eight ESX/ESXi hosts if the replica disks are stored on VMFS5 or later datastores or NFS datastores. If you store replicas on a VMFS version earlier than VMFS5, a cluster can have at most eight hosts.

In vSphere 5.0, you can select a cluster with more than eight ESXi hosts if the replicas are stored on NFS datastores. If you store replicas on VMFS datastores, a cluster can have at most eight hosts.

Use vSphere DRS. DRS efficiently distributes linked-clone virtual machines among your hosts.


Storage vMotion is not supported for linked-clone desktops.