HP Smart Update Manager 4.2 User Guide
Table Of Contents
- HP Smart Update Manager User Guide
- Abstract
- Notice
- Contents
- Introduction
- HP Smart Update Manager overview
- Using this guide
- New features of HP SUM 4.2.0
- Minimum requirements
- Supported deliverables overview
- Deployment from HP SUM
- Executing HP SUM
- Deploying software using the ProLiant Support Pack (PSP) for Microsoft Windows
- Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows
- Deploying software using the ProLiant Support Pack for Linux
- Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD
- Deploying firmware using the HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundles
- HP SUM User Interface
- Deployment scenarios
- Keyboard support
- Local host installations
- Multiple-host installations
- Selecting remote hosts or groups
- Searching for remote hosts
- Managing hosts
- Managing groups
- Entering credentials for hosts
- Selecting bundles to filter on multiple hosts
- Selecting components to install on multiple hosts
- Updating Firmware on HP Integrity BL860c/BL870c/BL890c i2 Servers
- Viewing the installation results for multiple hosts
- Scripted deployment
- Advanced topics
- Troubleshooting
- Recovering from a failed ROM upgrade
- Recovering from an installation failure
- Recovering from a discovery failure
- Recovering from a loss of Linux remote functionality
- Recovering from a blocked program on Microsoft Windows
- Recovering from operating system limitations when using a Japanese character set
- Recovering from Fatal Error - application will exit message
- Recovering from a missing reboot message when running on SUSE LINUX Enterprise Server 9
- Recovering a lost HP Smart Update Manager connection
- Troubleshooting HP Smart Update Manager in IPv6 networks
- HP SUM found new hardware message
- Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source
- Linux component version discrepancy for source RPMs
- HP SUM displays No components found in the selected repository(ies) message
- Additional/Optional Actions columns are grayed when HP SUM is maximized
- Installation of components failed with 'Update returned an error' when installing Linux RPMs
- Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens
- HP SUM fails on Windows Vista® due to McAfee firewalls
- Technical support
- Acronyms and abbreviations
- Index

Scripted deployment 68
Command-line argument Description
fails, and an error message writes to the log file.
Failed dependencies are not reported to the user when using the /s[ilent]
argument. To check for failed dependencies, remove the /s[ilent] argument,
reissue the command line, and then the HP SUM GUI appears.
/allow_update_to_bun
dle
This argument is a filter switch and enables the user to install newer versions of
components defined in a PSP, ISP, or firmware bundle.
This argument enables these components to replace the older versions of the
same component that might have shipped with the bundles.
/allow_non_bundle_co
mponents
This argument is a filter switch and enables the user to install components that are
not included in the bundle but reside in the directory with the components in the
bundle.
/b[undle] <bundlename>
or <bundle1_to_install>
<bundle2_to_install>
This argument specifies the bundles to install. Bundles to install can be specified
with or without the /b[undle] argument.
•
If using the /b[undle] argument, then only one bundle can be specified
with the argument. However, multiple /b arguments and bundles can be
specified on the same line.
•
If the /b[undle] argument is not used, then multiple bundles can be
specified at the sam
e time, but the bundles need to be separated by a blank
and listed after all the arguments on the command line.
Multiple components and bundles can be specified on the same command line.
When mixing components and bundles on the command line, the filter switches
control what components and bundles are installed.
/express_install
This argument starts express install (for local host only). HP SUM performs
discovery, install, or exit without user interaction. The user can cancel or
terminate HP SUM.
/use_location
“file_share”
This argument specifies a directory or file share that contains the PSP, ISP, and
components for use with HP SUM. The file_share format must be a mapped file
share and not in UNC format.
If you do not specify this argument, the directory containing hpsum.exe or HP
SUM is used by default. The logged-in account must have access to this location.
The /user and /passwd arguments do not have any effect when attempting to
access the file share. You can use those arguments only when connecting to a
target system.
/use_web
This argument specifies that the checkbox for Check ftp.hp.com on the Source
Selection screen is selected. This enables components to be retrieved from
hp.com and used in the list of possible updates. This argument is not supported
on HP Integrity servers.
/use_proxy <Proxy
server>
This argument enables the inclusion of a proxy server (and port number) to access
ftp.hp.com. This parameter must be used with /use_web. For example,
/use_web /use_proxy <1.22.33.44:80>. This argument is not supported
on HP Integrity servers.
/proxy_script <Proxy
script>
This argument enables the inclusion of a proxy script to access ftp.hp.com. This
parameter must be used with /use_web. For example, /use_web
/proxy_script <autoproxy.com>. This argument is not supported on HP
Integrity servers.
/use_d[ownloaded]
This argument specifies that the checkbox for Include components previously
downloaded from HP.com on the Source Selection screen is selected. This
enables those previously downloaded components to be included in the list of
possible updates. This argument is not supported on HP Integrity servers.
/tpmbypass or
/ignore_tpm
This argument specifies that if a TPM is enabled, then the warning message can
be ignored and component installation continues.