Altiris Deployment Solution™ from Symantec User’s Guide 186
purposes. The script runs in a logged-in user’s UI session. If no users are logged
in, the job fails.
Scripts run in an elevated mode, which skips the usual consent step through a
user access control (UAC). Otherwise, someone must physically go to the
remote computer and approve the action to allow the script to run.
Script Window. From the drop-down list, select how you want the script window to
appear: minimized, normal, maximized, or hidden.
Note
This option is available only for Windows environment.
Script Options - (Windows/Linux/Mac OS X)
Additional command-line switches. Enter commands to execute when the
script runs in Windows, Linux, or Mac OS X.
z Automation pre-boot environment (DOS/WinPE/Linux/Mac OS X). Select
this option to run the script in an automation environment. Select a pre-boot
automation environment from the drop-down list.
If you select Linux as the operating system type, the Locally on the Deployment
Server option is disabled and only the Additional command-line switches under the
Production Client installed OS (Windows/Linux/Mac OS X) is enabled.
If you select DOS as the operating system type, the Locally on the Deployment
Server and the Production - Client-installed OS (Windows/Linux/Mac OS X)
options are disabled.
Example script
The process to convert NT4 from FAT16 to NTFS normally returns a 1 after a successful
completion. The following is an example of the file that is modified to return a code of 0
(which is the success code recognized by the Symantec Management Console and
utilities). You can make similar changes to your script files as needed.
CONVERT /FS:NTFS
if ERRORLEVEL 1 goto success
goto failure
:success
set ERRORLEVEL = 0
goto end
:failure
echo Failed
set ERRORLEVEL = 1
goto end
:end
Using LogEvent and WLogEvent in scripts
The logging features, LogEvent and WLogEvent, accommodate detailed logging to help
debug complex scripts. These utilities include the following features:
To Next Page
Loading...
