Administration

Table Of Contents
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 is enabled. When provisioning is disabled, View stops the machines 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.
Procedure
1 In View Administrator, select Resources > Farms.
2 Double-click the pool ID of the farm that you want to recompose.
3 Click Recompose.
4 (Optional) Click Change to change the parent virtual machine.
The new parent virtual machine must run the same version of the operating system as the current
parent virtual machine.
5 Select a snapshot.
6 (Optional) Click Snapshot Details to display details about the snapshot.
7 Click Next.
8 (Optional) Schedule a start time.
The current time is filled in by default.
9 (Optional) Specify whether to force users to log off or wait for users to log off.
The option to force users to log off is selected by default.
10 (Optional) Specify whether to stop provisioning at first error.
This option is selected by default.
11 Click Next.
The Ready to Complete page is displayed.
12 (Optional) Click Show Details to display details of the recompose operation.
13 Click Finish.
In vCenter Server, you can monitor the progress of the recompose operation on the linked-clone virtual
machines.
NOTE During the recompose operation, View Composer runs Sysprep again on the linked clones. New SIDs
and third-party GUIDs might be generated for the recomposed virtual machines. For details, see
"Recomposing Linked Clones Customized with Sysprep" in the Setting Up Desktop and Application Pools in
View document.
View Administration
160 VMware, Inc.