7.0

Instant clones have the following compatibility requirements:
n
vSphere 6.0 Update 1 or later.
n
Virtual machine version 11 or later.
It is recommended that you configure distributed virtual switches in the vSphere environment.
In Horizon 7.0, instant clones have certain restrictions:
n
Single-user desktops only. RDS hosts are not supported.
n
Floating user assignment only. Users are assigned random desktops from the pool.
n
Instant-clone desktops cannot have persistent disks. Users can use VMware App Volumes to store
persistent data. For more information about App Volumes, see
https://www.vmware.com/products/appvolumes.
n
Virtual Volumes and VAAI (vStorage APIs for Array Integration) native NFS snapshots are not
supported.
n
Sysprep is not available for desktop customization.
n
Windows 7 and Windows 10 are supported but not Windows 8 or Windows 8.1.
n
PowerCLI is not supported.
n
Local datastores are not supported.
n
IPv6 is not supported.
n
Instant clones cannot reuse pre-existing computer accounts in Active Directory.
n
Persona Management is not available.
n
3D rendering is not available.
n
You cannot specify a minimum number of ready (provisioned) machines during instant clone
maintenance operations. This feature is not needed because the high speed of creating instant clones
means that some machines are always available even during maintenance operations.
The disk space reclamation feature that is available to View Composer linked clones is not needed because
instant clones are recreated when users log off, so that reclaiming unused disk space in a VM no longer has
a significant impact on storage consumption.
Each instant-clone desktop pool is associated with an image. An image is the snapshot of a parent VM.
Creating an instant-clone desktop pool involves two operations:
1 View publishes the image that you selected. In vCenter Server, four folders
(ClonePrepInternalTemplateFolder, ClonePrepParentVmFolder, ClonePrepReplicaVmFolder, and
ClonePrepResyncVmFolder) are created if they do not exist, and a number of internal VMs that are
required for cloning are created. In View Administrator, you can see the progress of this operation on
the summary page of the desktop pool. During publishing, the Pending Image pane shows the image
and its state.
NOTE Do not tamper with the four folders or the internal VMs that are in them. Otherwise, errors
might occur. The internal VMs are automatically removed when they are no longer needed. Normally
the VMs are removed within 5 minutes of pool deletion or a push image operation. However,
sometimes the removal can take up to 30 minutes.
2 The clones are created. This process is very fast. Typically, a clone can be created in less than two
seconds. During this process, the Current Image pane shows the image and its state.
After the pool is created, you can change the image through the push image operation. See "Change the
Image of an Instant-Clone Desktop Pool" in the View Administration document. Again, the new image is first
published. Then the clones are recreated.
Setting Up Desktop and Application Pools in View
80 VMware, Inc.