Installation

Table Of Contents
Configuring Your Infrastructure for View Composer
You can take advantage of features in vSphere, vCenter Server, Active Directory, and other components of
your infrastructure to optimize the performance, availability, and reliability of View Composer.
Configuring the vSphere Environment for View Composer
To support View Composer, you should follow certain best practices when you install and configure
vCenter Server, ESXi, and other vSphere components.
These best practices let View Composer work efficiently in the vSphere environment.
n
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 cannot successfully look up the virtual machines
in vCenter Server.
n
Make sure that the vSwitch settings on the 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
ESXi host.
n
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.
n
In vSphere 5.1 and later, a cluster that is used for View Composer linked clones can contain more than
eight 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.
n
Use vSphere DRS. DRS efficiently distributes linked-clone virtual machines among your hosts.
NOTE Storage vMotion is not supported for linked-clone desktops.
Additional Best Practices for View Composer
To make sure that View Composer works efficiently, check that your dynamic name service (DNS) operates
correctly, and run antivirus software scans at staggered times.
By making sure that DNS resolution operates correctly, you can overcome intermittent issues caused by
DNS errors. The View Composer service relies on dynamic name resolution to communicate with other
computers. To test DNS operation, ping the Active Directory and View Connection Server computers by
name.
If you stagger the run times for your antivirus software, performance of the linked-clone desktops is not
affected. If the antivirus software runs in all linked clones at the same time, excessive I/O operations per
second (IOPS) occur in your storage subsystem. This excessive activity can affect performance of the linked-
clone desktops.
Chapter 5 Installing View Composer
VMware, Inc. 43