To deploy linked-clone desktops, you must prepare a parent virtual machine that meets the requirements of the View Composer service.

The View Composer service requires a parent virtual machine from which you generate a base image for creating and managing linked-clone desktops.

To make sure that View Composer properly activates Windows 8, Windows 7, and Windows Vista operating systems on linked-clone desktops, you must use Microsoft volume activation on the parent virtual machine. The volume-activation technology requires a volume license key.

The Windows hibernation option creates a large system file that can increase the size of the linked-clone OS disks that are created from the parent virtual machine. Disabling the hibernation option reduces the size of linked-clones.

When you prepare a parent virtual machine for View Composer, you can configure the parent virtual machine and linked-clone desktops to store virtual-machine swap files on the local datastore. This optional strategy lets you take advantage of local storage.

When you create a linked-clone pool, you can redirect the linked clones' guest OS paging and temp files to a separate disk. You must configure this disk to be larger than the paging file in the guest OS.

View Composer terminates a QuickPrep post-synchronization or power-off script that takes longer than 20 seconds. You can increase the timeout limit for these scripts by changing the ExecScriptTimeout Windows registry value on the parent virtual machine.