Machine recomposition simultaneously updates all the linked-clone virtual machines anchored to a parent virtual machine.
About this task
If possible, schedule recompositions during off-peak hours.
Verify that you have a snapshot of the parent virtual machine. See Prepare a Parent Virtual Machine to Recompose Linked Clones.
Familiarize yourself with the recomposition guidelines. See Updating Linked Clones with Recomposition.
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.
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 linked-clone desktop.
If you force users to log off, View 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 remote 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 remote desktops that require logoffs is 12.
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 desktop 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.
Verify that provisioning for the desktop pool is enabled. When desktop pool provisioning is disabled, View stops the desktops from being customized after they are recomposed.
If your deployment includes replicated View Connection Server instances, verify that all instances are the same version.
- Choose whether to recompose the whole desktop pool or a single machine.
To recompose all virtual machines in the desktop pool
In View Administrator, select.
Select the desktop pool to recompose by double-clicking the pool ID in the left column.
On the Inventory tab, click Machines.
Use the Ctrl or Shift keys to select all the machine IDs in the left column.
Select Recompose from the View Composer drop-down menu.
To recompose selected virtual machines
In View Administrator, select.
Select the machine to recompose by double-clicking the machine ID in the left column.
On the Summary tab, select Recompose from the View Composer drop-down menu.
- Follow the wizard instructions.
You can select a new virtual machine to be used as the parent virtual machine for the desktop pool.
On the Ready to Complete page, you can click Show Details to display the linked-clone desktops that will be recomposed.
The linked-clone virtual machines are refreshed and updated. The OS disks are reduced to their original size.
In a dedicated-assignment pool, unassigned linked clones are deleted and recreated. The specified number of spare virtual machines is maintained.
In a floating-assignment pool, all selected linked clones are recomposed.
In vCenter Server, you can monitor the progress of the recomposition on the linked-clone virtual machines.
In View Administrator, you can monitor the operation by clicking Tasks tab. You can click Cancel task, Pause task, or Resume task to terminate a task, suspend a task, or resume a suspended task., double-clicking the pool ID, and clicking the
If you used a Sysprep customization specification to customize the linked clones when you created the desktop pool, new SIDs 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.