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 72
Command-line argument Description
the same directory as the HP SUM log files.
Including other arguments on the command line can modify the contents of the
report. Using the /target argument will allow reports to be generated for
different targets.
(This CLI does not apply to firmware updates on the HP Integrity
BL860c/BL870c/BL890c i2 Servers.)
Using input files
/inputfile “filename”
This argument enables you to script the deployment of firmware and software to
multiple remote systems at one time. For details of the file format and commands,
see "Input files (on page 75)".
/deleteinputfile
“filename”
This argument enables you to instruct HP SUM to delete the input file after it has
been read in.
Component configuration for Windows components only
To configure components without using the HP Smart Update Manager GUI, issue the command,
hpsum_config <component_to_configure>. This command presents the same configuration screens seen
in the HP Smart Update Manager GUI. You must run this command from a CD or other read-only media, or
the component cannot be configured. Configuration for a given component only needs to be executed one
time. The configuration is stored within the component and is propagated to all target servers when deployed
through HP Smart Update Manager GUI or command line. To change the configuration, rerun
hpsum_config against the component and a new configuration writes out. If a component does not need
configuration, the hpsum_config command returns to the console.
To configure components to be deployed on all editions of the Windows Server® 2008 with the Server Core
option, you must access the system as a remote host using HP Smart Update Manager running on a system
with a supported Windows® operating system, and then configure the components before deployment.
Command-line examples
The following command-line parameter examples can be executed within these environments:
• Windows® PSPs:
o ProLiant Support Pack for Microsoft® Windows Server™ 2003 v7.90 (BP000323.xml)
o ProLiant Support Pack for Microsoft® Windows Server™ 2003 v7.80 (BP000315.xml)
• Firmware:
o System ROM
o Smart Array controller
o Hard drives
o iLO
• Software—later version of:
o HP Insight Diagnostics Online Edition for Windows Server™ 2003 (cp008097.exe)
o HP System Management Homepage for Windows® (cp008257.exe)
• HP Smart Update Manager