4.5

Solution
n
Examine the customization script log.
QuickPrep customization information is written to a log file in Windows temp directory:
C:\Windows\Temp\vmware-viewcomposer-ga-new.log
n
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 [1500] INFO Ready -
[Ready.cpp, 102] Running the PostSync script: cmd /c
C:\temp\build\composer.bat
2010-02-21 21:06:07,348 [1500] 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.
n
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:
C:\windows\system32\cscript.exe c:\script\myvb.vbs
n
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 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.
View Composer Provisioning Errors
If an error occurs when View Composer provisions or recomposes linked-clone desktops, an error code
indicates the cause of the failure. The error code appears in the desktop-status column in View Administrator.
Table 15-2 describes the View Composer provisioning error codes.
This table lists errors that are associated with View Composer and QuickPrep customization. Additional errors
can occur in View Connection Server and other View components that can interfere with desktop provisioning.
Table 15-2. View Composer Provisioning Errors
Error
Description
0 The policy was applied successfully.
NOTE
Result code 0 does not appear in View Administrator. The linked-clone desktop proceeds to a Ready
state, unless a View Manager error outside the domain of View Composer occurs. This result code is included
for completeness.
1 Failed to set the computer name.
2 Failed to redirect the user profiles to the View Composer persistent disk.
3 Failed to set the computer's domain account password.
VMware View Administrator's Guide
284 VMware, Inc.