HP Smart Update Best Practices Planning Guide

• Update single module—HP SUM does not allow you to update only a single module.
• Non-redundant configuration—If HP SUM detects that the VC module is non-redundant, it will
not allow you to perform any updates. This prevents an accidental server outage.
• Not part of a domain—HP SUM alerts you if the VC module is not part of a domain. HP SUM
requires the VC module to be part of a domain to perform discovery.
• Change activation order—If you want to change the activation order, insert time delay for VC
modules, or choose other non-default options.
• Back up configuration before flashing VC firmware—HP SUM does not issue the commands
to perform a backup for targets.
• The VC modules are managed by VCEM—If VC module is managed by VCEM, you need to
put the VC module into maintenance mode. After changing to maintenance mode, rescan the
VC module in HP SUM and continue with the update.
SCCM
Microsoft SCCM 2007 enables HP customers to use SCCM for update management and distribution
of HP ProLiant server system software and PSPs. See the documentation that comes with SCCM for
instructions on how to manage updates with SCCM.
HP has developed an Updates Catalog cabinet file (ProLiant.cab) containing an XML file that
conforms to the Microsoft update format to describe updates available from HP. This cabinet file
enables SCCM to understand and interpret the update status for ProLiant servers. You can monitor
ProLiant server update status and authorize and deploy software updates to servers. Deployment
of PSPs is comprehensive. You receive the benefit of deploying PSPs, which are tested together to
ensure a smooth installation. Using the SCUP tool, the HP catalog can be imported into the SCCM
server. The SCCM server can deploy software from the imported catalog to client servers. SCUP
works with the WSUS and SCCM. It is a separate installation by the administrator.
Managing and deploying HP ProLiant SmartStart components and ProLiant Support Packs only
requires SCCM 2007, WSUS, and SCUP installation. SCCM, WSUS, and SCUP must be installed
and verified before managing HP updates. See the documentation for detailed SCCM, WSUS,
and SCUP setup information on the Microsoft website at http://www.microsoft.com.
HP Server Updates Catalog should be used for monitoring and deploying software and firmware
upgrades, as well as new and upgrade installations of the SPP. Initial installations for individual
software and firmware are not supported due to the complexity of inter-component dependency.
Deployment of PSP is recommended for newly-configured ProLiant servers to ensure all relevant
software is installed.
SCCM 2007 uses the WSUS infrastructure for delivering software updates to managed devices.
Though some of the user experience is similar to SMS 2003, the architecture is different and uses
a custom HP-provided scan tool along with standard packages and advertisements. The new SCCM
infrastructure does not support the SMS 2003 Inventory Tool for HP ProLiant and Integrity Update.
Use SCCM to update PSPs, software updates, and specific firmware updates. If you have SCCM,
you need additional tools to complete firmware updates.
NOTE: SCCM cannot be used to update firmware on non-server targets, for example, OA, VC,
and other enclosure interconnects.
VMware ESXi firmware updates
VMware ESXi 5.0 and later
HP SUM 5.3.5 and later can update firmware for VMware ESXi 5.0 and later targets. Run HP
SUM on a Windows or Linux host system, and update your VMware targets over a network.
VMware updates are available in the HP SPP. For more information on released components, see
SCCM 31