6.2

SeIncreaseBasePriorityPrivilege
SeCreatePermanentPrivilege
SeDebugPrivilege
SeAuditPrivilege
QuickPrep Script Logs
View Composer logs contain information about QuickPrep script execution. The log records the start and
end of execution and logs output or error messages. The log is located in the Windows temp directory:
C:\Windows\Temp\vmware-viewcomposer-ga-new.log
Recomposing Linked Clones Customized with Sysprep
If you recompose a linked-clone machine that was customized with Sysprep, View runs the Sysprep
customization specification again after the OS disk is recomposed. This operation generates a new SID for
the linked-clone virtual machine.
If a new SID is generated, the recomposed linked clone functions as a new computer on the network. Some
software programs such as system-management tools depend on the SID to identify the computers under
their management. These programs might not be able to identify or locate the linked-clone virtual machine.
Also, if third-party software is installed on the system disk, the customization specification might regenerate
the GUIDs for that software after the recomposition.
A recomposition restores the linked clone to its original state, before the customization specification was run
the first time. In this state, the linked clone does not have a local computer SID or the GUID of any third-
party software installed in the system drive. View must run the Sysprep customization specification after
the linked clone is recomposed.
Keeping Linked-Clone Machines Provisioned for Use in Remote
Desktop Sessions During View Composer Operations
If your users must be able to access remote desktops at all times, you must maintain a certain number of
machines that are provisioned for use in remote desktop sessions even when View Composer maintenance
operations take place. You can set a minimum number of machines that are not placed in maintenance mode
while View Composer refreshes, recomposes, or rebalances the linked-clone virtual machines in a pool.
When you set a Minimum number of ready (provisioned) machines during View Composer maintenance
operations, View ensures that the specified number of machines stay provisioned, and are not placed in
maintenance mode, while View Composer proceeds through the maintenance operation.
This setting lets users maintain existing connections or make new connection requests during the View
Composer maintenance operation. The setting does not distinguish between spare machines that are ready
to accept new connections and machines that are already connected in existing desktop sessions.
You can specify this setting when you create or edit a linked-clone pool.
The following guidelines apply to this setting:
n
To allow a number of users to maintain their existing desktop connections and keep a minimum
number of spare (powered on) machines that can accept new connection requests, set the Minimum
number of ready (provisioned) machines during View Composer maintenance operations to a large
enough value to include both sets of machines.
n
If you use a naming pattern to provision machines and provision machines on demand, set the number
of provisioned machines during View Composer operations to a smaller value than the specified Max
number of machines. If the maximum number were smaller, your pool could end up with fewer total
machines than the minimum number you want to keep provisioned during View Composer operations.
In this case, View Composer maintenance operations could not take place.
Chapter 5 Creating Linked-Clone Desktop Pools
VMware, Inc. 77