Scripted Install For Linux; Scripted Install Summary; Distributing Software - Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0 Manual

Scripted install for Linux

Distributing software

Altiris Deployment Solution™ from Symantec User's Guide
Note
If you want to use the sample answer files (Vista_unattend.xml and
Longhorn_unattend.xml) provided by default in the Deploy folder of the Deployment
Share, you must enter the product key (for the version you want to install) before
you schedule the job. (See
the product key, the job fails.
The Scripted OS install for Linux provides a wizard to help set up Linux installation files
and run Sample jobs. Follow steps in the wizard to identify the type of scripted install
and locate the answer files. You can also modify and run Sample deployment jobs to
remotely run a scripted install on Linux servers and workstations.
Directory. Browse to or enter the path and name of the Linux answer file (Kickstart
file).
Command-line. Enter the command-line options.
Automation pre-boot environment (DOS/WinPE/Linux). Select the required pre-
boot environment from the drop-down list to perform the Backup and Restore task in
the selected pre-boot environment. By default, the Default Automation (Auto-select)
type is selected.
See also Scripted OS install

Scripted install summary

View a summary of the selected options for the scripted install. Click Back to change
any of these settings or click Finish to complete the Scripted Install task.
Send .MSI Packages, .CAB, .EXE, and other package files to selected computers or
computer groups, including EBS, and .RPM files for Linux computers. This task identifies
valid Altiris packages and assigns passwords and command-line options.
Distribute software packages to managed computers using the New Job
Wizard or adding the Distribute Software task when building new jobs.
See New Job Wizard on page 130 and Building New Jobs on page 134.
1. Enter the name and location of the package to distribute in the Name field.
Note
Information about the package appears in the Description field for valid packages.
If no description appears, the file is not an .RIP or a Personality Package.
2. For .RIPs, if you set the password option when you created the .RIP, you must
enter the password for the package to run.
3. Select Run in quiet mode to install the package without requiring user interaction.
4. Specify the users to associate with the .RIP or the Personality Package.
OS product key dialog
on page 168 and Scripted install for Windows
on page 84.) If you do not select
on page 169.
175