How To Install Software Packages And Support Packs
Article: 20000042
Applies to: All releases
To create a job that installs software:
| 1. |
On the Deployment Server, create a directory in the express share for the file(s).
|
| 2. |
Download the file(s) into the new directory.
|
| 3. |
Write down the name of the install or setup executable.
If the installation requires more than one step, like installing multiple Windows hotfixes, create a batch or script file for all of the steps.
|
| 4. |
Write down any command-line parameters needed to execute the installer in a silent, non-interactive manner.
|
| 5. |
Write down any non-zero exit codes that mean success.
Most installers return 0 on success and non-zero on error. However, some installers also return other success codes.
For example, some Microsoft installers return 3010 for "success, reboot required".
|
| 6. |
In the Deployment Console, create a new job.
| a. |
Add a Distribute Software task with the following options:
|
| Field |
Value |
|
| Name |
The file from step 3 above |
|
| Additional command-line switches |
The parameters from step 4 above |
|
| Copy all directory files |
Selected |
|
| Return Codes |
For each code from step 5 above, add the value and set Response = Continue and Result = Success |
|
|
|
NOTE: Select Yes if a warning appears about the file specified is not a valid RapidInstall or PC Transplant package.
|
| b. |
Add a Power Control task with the following options:
|
| Field |
Value |
|
| Restart |
Selected |
|
| Force applications to close without a message |
Selected |
|
|
|
| 7. |
Execute the new job on the desired servers.
|
Example information to create a job to install a Windows ProLiant Support Pack (PSP):
| 1. |
Download and extract the PSP files into a directory on the Deployment Server express share, for example ws6-x64-psp.
If the PSP is a Delta bundle, then both PSP and the Delta bundle files will need to be combined in the same directory.
|
| 2. |
Create the Distribute Software task in the job with .\ws6-x64-psp\hpsum.exe in the Name field and
-silent -force in the Additional command-line switches field. Add 1 and 3 as
return codes that are a success and the job should continue.
|
Example information to create a job to install a Linux ProLiant Support Pack (LSP):
When editing Linux files on the Deployment Server, use a text editor that saves the file in
Linux compatible format without adding extra characters.
For additional information,
refer to Knowledge Base article (Article 20000058).
LSP components may require certain Linux packages to be installed
prior to starting the LSP installation. If the required packages are not installed,
a component may fail installation with a dependency error and the job fails with error code 10.
Refer to the ProLiant Support Pack User Guide for additional information.
For LSP 8.40 and greater, hpsum is used to install the components and will attempt all components found in the directory.
This may result in a component installing on a server when the component is not needed. For example,
fibre channel drivers are only supported for older updates of Red Hat Enterprise Linux 4 and 5 and SUSE LINUX Enterprise Server 10. However, hpsum will attempt to install
these on RHEL 4.8, RHEL 5.4, and SLES 10 SP3 which results in an error code 253 causing the job to fail. Other components will get installed on the target server.
Alternatively, delete the following components from LSP which are known not to install on latest RedHat and SUSE updates and return error code 253:
hp_qla2x00src-8.02.23-2.noarch.rpm
hp_qla2x00src-mezz-8.02.23-2.noarch.rpm
hp-lpfc-8.2.0.22-9.rhel5.noarch.rpm
| 1. |
Download and extract the LSP files into a directory on the Deployment Server express share, for example rhel5-x64-psp.
If the LSP is a Delta bundle, then both LSP and the Delta bundle files will need to be combined in the same directory.
|
| 2. |
For custom SNMP configurations, create a text file in the directory, for example hpmgmt.conf.
Refer to the HP ProLiant Support Pack User Guide for the LSP scripted install file format and parameters.
|
| 3. |
Create a script file, for example lspinstall.sh, in the directory that will be used as a wrapper script to call the LSP installer.
This is necessary since the LSP installer does not work when called with an absolute path.
The script to call LSP 8.40 and greater should contain the following code:
pushd "$(dirname "$0")"
chmod +x *
./hpsum --silent --force --inputfile hpmgmt.conf
rc=$?
popd
exit $rc
The script to call LSP 8.30 and earlier should contain the following code:
pushd "$(dirname "$0")"
chmod +x install???.sh
./install???.sh --silent --force --inputfile hpmgmt.conf
rc=$?
popd
exit $rc
where hpmgmt.conf is the file created in step 2.
|
| 4. |
Create the Distribute Software task in the job with .\rhel5-x64-psp\lspinstall.sh in the Name field.
For LSP 8.40 and greater, add 1, 2, and 3 as return codes that are a success and the job should continue.
For LSP 8.30 and earlier, add 16 as a return code that is a success and the job should continue.
|
To install the HP Agents bundle for VMware ESX 3.x, the previous LSP steps may be used with the following modifications:
| • |
Run the ESX 3.x scripted install job without the Install Package task; otherwise, the agents installed by the default job
will conflict with HP Agents bundle and result in an error 1 failure.
|
| • |
There is a default hpmgmt.conf file bundled with HP Agents that can be used as a sample to create this file.
|
| • |
The VMware ESX HP Agents installer is called installvmXXX.sh where XXX is the version number.
The script to call the HP Agents installer should use installvm???.sh and the --force calling argument removed.
|
|
Printable version
