Deployment Scenarios; Trusted Platform Module - HP Integrity Superdome 2 16-socket User Manual

Term
Offline
These terms can be used in combination to designate the type of environment required for updates
to occur, such as local-online or remote-online.

Deployment scenarios

HP SUM deploys firmware and software on a local host or one or more remote hosts. If the host
running HP SUM is using a Windows operating system, you can update Windows, Linux, or
VMware target. HP Integrity servers can be running HP-UX or other operating systems, but the
updates are driven by a Windows or Linux workstation that performs the updates through the iLO
or OA.
NOTE: HP SUM can detect updates that are available for a VMware server and generate reports,
it cannot deploy updates.
The following table describes when typical HP SUM deployment scenarios are used.
Scenario
Graphical deployment on a local host
Scripted deployment on a local host
Graphical deployment to a remote host
Scripted deployment to a remote host

Trusted Platform Module

The TPM, when used with BitLocker, measures a system state and, upon detection of a changed
ROM image, restricts access to the Windows file system if the user cannot provide the recovery
key. HP SUM detects if a TPM is enabled in your system. If a TPM is detected in your system or
with any remote server selected as a target, for some newer models of ProLiant servers, HP SUM
utilities for HP iLO, Smart Array, NIC, and BIOS warn users prior to a flash. If the user does not
12 Introduction
Definition
firmware. You might need to reboot the target to activate
the firmware.
In offline mode, the HP SUM boots a small Linux kernel
and enables updates to occur on a single server.
Only updates the local system
Only uses a single repository
NOTE: Some features of HP SUM that require the
regular local host operating systems are not supported
in offline mode
Used when
You are not familiar with command line tools.
You are deploying components on a local, single host.
Updates do not require scripting.
You are familiar with command line tools.
You are deploying components on a local, single host.
Updates require a customized, scripted deployment.
You are not familiar with command line tools.
You are deploying components on one or more remote
hosts.
Updates do not require scripting.
You are familiar with command line tools.
You are deploying components on one or more hosts.
Updates require a customized, scripted deployment to
one or more host systems.