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

HP SUM User Interface 25
HP SUM User Interface
Deployment scenarios
HP SUM deploys firmware and software on a local host or one or more remote hosts. The remote hosts must
be online and running the same operating system as the system running HP SUM. For example, when the
remote hosts are running Linux, HP SUM must also be running on a Linux operating system.
The following table describes when typical HP SUM deployment scenarios are used.
Scenario Used when
Graphical deployment on a local host
•
Are not familiar with command line tools.
•
Are deploying components on a local, single host.
•
Do not require scripting.
Scripted deployment on a local host
•
Are familiar with command line tools.
•
Are deploying components on a local, single host.
•
Must perform a customized, scripted deployment.
Graphical deployment to a remote host
•
Are not familiar with command line tools.
•
Are deploying components on one or more remote hosts.
•
Do not require scripting.
Scripted deployment to a remote host
•
Are familiar with command line tools.
•
Are deploying components on one or more hosts.
•
Must perform a customized, scripted deployment to one or
more host systems.
Graphical deployment on a local host
To deploy components to a single local host, use the HP SUM GUI.
1. Ensure all minimum requirements are met as described in "Minimum requirements (on page 7)."
2. Ensure that the components to be deployed are accessible to the local host.
For information about performing the deployment using the GUI, see "Local host installations (on page 27)."
Scripted deployment on a local host
To deploy components to a local host using the command-line interface:
1. Ensure all minimum requirements are fulfilled as described in "Minimum requirements (on page 7)."
2. Ensure that the components to be deployed are accessible to the local host.
3. Create a script to customize the deployment. See "Scripted deployment (on page 66)" for more
information.
4. Execute the script.