Troubleshooting QuickPrep customization problems (1026999)
- The QuickPrep post-synchronization or power-off script does not execute
- The script completes successfully on some linked clones, but fail on others
This article provides information to troubleshoot Quickprep customization problems in a VMware View environment.
A View Composer QuickPrep customization script can fail for a variety of reasons. Some of the common causes for QuickPrep script failures are:
- 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
To resolve this issue:
- Examine the customization script log on the cloned desktop.
QuickPrep customization information is written to the vmware-viewcomposer-ga-new.log file located at:
- C:\Windows\Temp\ if there is no disposible disk configured
- DisposableDisk/Temp folder in the disposable disk if there is a disposable disk configured
- Determine if the script timed out.
View Composer terminates a customization script that takes longer than 20 seconds. The log file displays a message similar to:
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 resolve a timeout issue, increase the timeout limit for the script and run it again.
In View 4.5.x and 5.x you can increase the timeout limit by changing a registry value in the parent virtual machine. For more information, see the Increase the Timeout Limit of QuickPrep Customization Scripts section in the VMware View Administrator's Guide.
In View 4.0.x, you can use your customization script to launch another script or process that performs the long-running task. For example:
a. Create a batch file such as batch1.bat that contains the following line:
b. Create a batch script file under c:\yourpath\batch2.bat . This is the main script file that performs
the customization task.
When you specify a customization script, use batch1.bat as your script file.
- 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, C:\windows\system32\cscript.exe c:\script\myvb.vbs.
- Determine if the account under which the script runs has appropriate permissions to perform script tasks.
QuickPrep runs the scripts using an account with which the View Composer Agent service is configured to run. By default, this account is SYSTEM.To change the default account:
- Log in to the Virtual Desktop via Microsoft RDP or vSphere Client.
- Click Start > Run, type services.msc, and click OK. The Windows Services Microsoft Management Console Snap-In opens.
- Locate the VMware View Composer Guest Agent Server service.
Note: The internal service name is vmware-viewcomposer-ga.
- Right-click the service and click Properties.
- Click the Log On tab.
- Under Log On As, type the username and password of the user account under which you want to run the service.
- Click OK.
- Restart the service and use the new user credentials.