A View Composer QuickPrep customization script can fail for a variety of reasons.
A QuickPrep post-synchronization or power-off script does not execute. In some cases, a script might complete successfully on some linked clones, but fail on others.
A few common causes exist for QuickPrep script failures:
- The script times out
- The script path refers to a script that requires an interpreter
- The account under which the script runs does not have sufficient permission to execute a script task
- Examine the customization script log.
QuickPrep customization information is written to a log file in Windows temp directory:
- Determine if the script timed out.
View Composer terminates a customization script that takes longer than 20 seconds. The log file displays a message showing that the script has started and a later message indicating the timeout:
2010-02-21 21:05:47,687  INFO Ready - [Ready.cpp, 102] Running the PostSync script: cmd /c C:\temp\build\composer.bat 2010-02-21 21:06:07,348  FATAL Guest - [Guest.cpp, 428] script cmd /c C:\temp\build\composer.bat timed out
To solve a timeout problem, increase the timeout limit for the script and run it again.
- Determine if the script path is valid.
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:
- Determine if the account under which the script runs has appropriate permissions to perform script tasks.
QuickPrep runs the scripts under the account under which the VMware View Composer Guest Agent Server service is configured to run. By default, this account is Local System.
Do not change this log on account. If you do, the linked clones do not start.