7.0

Table 9‑2. Worksheet: Configuration Settings for Creating an Automated Farm (Continued)
Setting Description
Fill in Your Value
Here
Snapshot Select the snapshot of the parent virtual machine to use as the base
image for the farm.
Do not delete the snapshot and parent virtual machine from vCenter
Server, unless no linked clones in the farm use the default image, and
no more linked clones will be created from this default image. The
system requires the parent virtual machine and snapshot to provision
new linked clones in the farm, according to farm policies. The parent
virtual machine and snapshot are also required for View Composer
maintenance operations.
VM folder location Select the folder in vCenter Server in which the farm resides.
Host or cluster Select the ESXi host or cluster on which the desktop virtual machines
run.
With Virtual SAN datastores (a vSphere 5.5 Update 1 feature), you
can select a cluster with up to 20 ESXi hosts. With Virtual Volumes
datastores (a vSphere 6.0 feature), you can select a cluster with up to
32 ESXi hosts.
In vSphere 5.1 or later, you can select a cluster with up to 32 ESXi
hosts if the replicas 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.
Resource pool Select the vCenter Server resource pool in which the farm resides.
Datastores Select one or more datastores on which to store the farm.
A table on the Select Linked Clone Datastores page of the Add Farm
wizard provides high-level guidelines for estimating the farm's
storage requirements. These guidelines can help you determine which
datastores are large enough to store the linked-clone disks. For details,
see “Storage Sizing for Instant-Clone and View Composer Linked-
Clone Desktop Pools,” on page 241.
You can use shared or local datastores for an individual ESXi host or
for ESXi clusters. If you use local datastores in an ESXi cluster, you
must consider the vSphere infrastructure constraints that are imposed
on your desktop deployment. See “Storing View Composer Linked
Clones on Local Datastores,” on page 248.
NOTE If you use Virtual SAN, select only one datastore.
Storage Overcommit Determine the storage-overcommit level at which linked-clones are
created on each datastore.
As the level increases, more linked clones fit on the datastore and less
space is reserved to let individual clones grow. A high storage-
overcommit level lets you create linked clones that have a total logical
size larger than the physical storage limit of the datastore. For details,
see “Storage Overcommit for View Composer Linked-Clone Virtual
Machines,” on page 245.
NOTE This setting has no effect if you use Virtual SAN.
Setting Up Desktop and Application Pools in View
114 VMware, Inc.