Choosing Hp Sum Or Hp Sim; Disabling Bitlocker To Permit Firmware Updates - HP ProLiant DL320e User Manual

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

Choosing HP SUM or HP SIM

Use HP SUM to update 1–100 servers concurrently. You can use HP SIM to update more than 10
servers concurrently.
HP SIM versions 7.0 and later include the functionality of HP SUM. This allows you to use HP SIM
to update firmware, software, and drivers in the same session. You do not need to update these
items separately.

Disabling BitLocker to permit firmware updates

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 HP ProLiant servers, HP
SUM utilities for HP iLO, Smart Array, NIC, and BIOS warn users prior to a flash. If the user does
not temporarily disable BitLocker and does not cancel the flash, the BitLocker recovery key is needed
to access the user data upon reboot.
A recovery event is triggered if:
You do not temporarily disable BitLocker before flashing the system BIOS when using the
Microsoft BitLocker Drive Encryption.
You have optionally selected to measure HP iLO, Smart Array, and NIC firmware.
If HP SUM detects a TPM, a warning message appears.
12 Introduction
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.