4.6

In particular, QuickPrep passes the path that is specified for the script as the second parameter to the
CreateProcess API and sets the first parameter to NULL.
For example, if the script path is c:\myscript.cmd, the path appears as the second parameter in the function in
the View Composer log file: CreateProcess(NULL,c:\myscript.cmd,...).
Providing Paths to QuickPrep Scripts
You provide paths to the QuickPrep customization scripts when you create a linked-clone desktop pool or
when you edit a pool's guest customization settings. The scripts must reside on the parent virtual machine.
You cannot use a UNC path to a network share.
If you use a scripting language that needs an interpreter to execute the script, the script path must start with
the interpreter binary.
For example, if you specify the path C:\script\myvb.vbs as a QuickPrep customization script, View Composer
Agent cannot execute the script. You must specify a path that starts with the interpreter binary path:
C:\windows\system32\cscript.exe c:\script\myvb.vbs
QuickPrep Script Timeout Limit
View Composer terminates a post-synchronization or power-off script that takes longer than 20 seconds. If
your script takes longer than 20 seconds, you can increase the timeout limit. For details, see “Increase the
Timeout Limit of QuickPrep Customization Scripts,” on page 69.
Alternatively, you can use your script to launch another script or process that performs the long-running task.
QuickPrep Script Account
QuickPrep runs the scripts under the account under which the View Composer Agent service is configured to
run. By default, this account is SYSTEM.
You can change the default account by using the Windows Services (services.msc) dialog and changing the
log-on properties of the VMware View Composer Guest Agent Server service. The internal service name is
vmware-viewcomposer-ga.
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 desktop that was customized with Sysprep, View Manager 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 Manager must run the Sysprep customization specification after
the linked clone is recomposed.
Chapter 5 Creating Desktop Pools
VMware, Inc. 87