5.2

Procedure
1
In vCenter Server, update the parent virtual machine for the recomposition.
n
Install OS patches or service packs, new applications, application updates, or make other changes in
the parent virtual machine.
n
Alternatively, prepare another virtual machine to be selected as the new parent during the
recomposition.
2 In vCenter Server, power off the updated or new parent virtual machine.
3 In vCenter Server, take a snapshot of the parent virtual machine.
What to do next
Recompose the linked-clone desktop pool.
Recompose Linked-Clone Desktops
Desktop recomposition simultaneously updates all the linked-clone desktops anchored to a parent virtual
machine.
If possible, schedule recompositions during off-peak hours.
Prerequisites
n
Verify that you have a snapshot of the parent virtual machine. See “Prepare a Parent Virtual Machine to
Recompose Linked-Clone Desktops,” on page 253.
n
Familiarize yourself with the recomposition guidelines. See “Updating Linked Clones with Desktop
Recomposition,” on page 256.
n
Decide when to schedule the recomposition. By default, View Composer starts the recomposition
immediately.
You can schedule only one recomposition at a time for a given set of linked clones. You can schedule
multiple recompositions if they affect different linked clones.
n
Decide whether to force all users to log off as soon as the recomposition begins or wait for each user to
log off before recomposing that user's desktop.
If you force users to log off, View Manager notifies users before they are disconnected and allows them
to close their applications and log off.
If you force users to log off, the maximum number of concurrent recompose operations on desktops that
require logoffs is half the value of the Max concurrent View Composer maintenance operations setting.
For example, if this setting is configured as 24 and you force users to log off, the maximum number of
concurrent recompose operations on desktops that require logoffs is 12.
n
Decide whether to stop provisioning at first error. If you select this option and an error occurs when View
Composer provisions a linked clone, provisioning stops for all clones in the pool. You can select this option
to ensure that resources such as storage are not consumed unnecessarily.
Selecting the Stop at first error option does not affect customization. If a customization error occurs on a
linked clone, other clones continue to be provisioned and customized.
n
Verify that provisioning for the pool is enabled. When pool provisioning is disabled, View Manager stops
the desktops from being customized after they are recomposed.
n
If your deployment includes replicated View Connection Server instances, verify that all instances are the
same version.
VMware Horizon View Administration
254 VMware, Inc.