Table of Contents
Advertisement
Altiris Deployment Solution™ from Symantec User's Guide
execution. If a program returns a one (1), you see an error message at the
Deployment Console even though the script ran correctly. To modify the return
codes, you can edit the script file to return a code that the console interprets
correctly.
See also
Modifying tasks in a deployment job
Script information
Script Run Location
Select one of the following options to run the script:
On the client computer. This option runs the script on the managed computer
to which you assign the job.
Locally on the Deployment Server. This option runs a server-side script on
the Deployment Server of the managed computer. In most cases you can create
a server-side script task that runs in context with other tasks. Example: You can
add a task to image a computer and add a task to execute a server-side script
to post the imaging return codes to a log file stored on the Deployment Server
computer.
Use the -id option for running scripts on Deployment Server when using the
WLogEvent and LogEvent utilities. See
on page 186.
Note
You cannot use this feature to run scripts that require user intervention. The
script runs on the Deployment Server of the managed computer, but is not
visible. Example: If you run a DOS command locally on the Deployment Server,
the Command Prompt window does not open on the Deployment Server
computer when the script runs.
When running the script on the Deployment Server, it runs specifically for the
assigned managed computer. Example: If you create a job with a script to run
locally on the Deployment Server and assign the job to 500 computers, the
script runs on the Deployment Server 500 times.
Client run environment
Select the environment for your client computer. You can run the script either in
production mode or in automation mode.
Production - Client-installed OS (Windows/Linux/Mac OS X)
Security Context. You can specify one of the following security options for running
the scripts:
Default (local system account). Use the network security account established
to administrate all managed computers.
Specific user. If you have selected to run the task on the local Deployment
Server, enter an administrator user name and password for that Deployment
Server account. In most cases Deployment Server does not have the
Deployment Agent installed, which prohibits it from using a network security
account.
Run script in console user session. For Windows 2008 and Vista, you can
see the output of jobs on a local desktop and use that output for debugging
on page 190.
Using LogEvent and WLogEvent in scripts
185
Advertisement
Table of Contents
