How To Install Software Packages,Service Pack for ProLiant (SPP) And Support Packs

On the Deployment Server, create a directory in the express share for the file(s).

Download the file(s) into the new directory.

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.

Write down any command-line parameters needed to execute the installer in a silent, non-interactive manner.

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".

In the Deployment Console, create a new job.

a. Add a Distribute Software task with the following options:

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:

Download and extract the PSP/SPP files or hp\swpackages folder from SPP into a directory on the Deployment Server express share, for example ws6-x64-psp or ws6-x64-spp . If the PSP is a Delta bundle, then both PSP and the Delta bundle files will need to be combined in the same directory.

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,2and 3 as return codes that are a success and the job should continue.

Download and extract the LSP files or hp\swpackages folder from SPP 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.

For custom SNMP configurations, create a text file in the directory, for example hpmgmt.conf. Refer to the HP ProLiant Support Pack User Guide or HPSUM helpfor the LSP scripted install support, file format and parameters.

NOTE: Refer to HP Smart Update Manager (HPSUM) help/User guide for additional command line options, return values and logs.

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 SPP should contain the following code:

pushd "$(dirname "$0")"
chmod +x *
./hpsum --silent --force rc=$?
popd
exit $rc

The script to call SPP should contain the following code for RHEL 6:

pushd "$(dirname "$0")"
chmod +x *
rm -rf /rpmbuild
mkdir /rpmbuild
mkdir /root/rpmbuild
mount --bind /root/rpmbuild /rpmbuild
./hpsum --silent --force 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.

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.