The TPM, when used with BitLocker, measures a system state. Upon detection of a changed ROM image, it 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. For some newer models of HP ProLiant servers, if a TPM is detected in your system or with any remote server selected as a target, 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 in the following situations:
If HP SUM detects a TPM, a warning message appears:
CAUTION: A Trusted Platform Module (TPM) has been detected in this system. Failure to perform proper OS encryption procedures will results in loss of access to your data if recovery key is not available. Recommended procedure for Microsoft Windows (R) BitLocker (TM) is to \”suspend\” BitLocker prior to System ROM or Option ROM firmware flash. If you do not have your recovery key or have not suspended BitLocker, exit this flash. Failure to follow these instructions will results in loss of access to your data.
To enable firmware updates without the need to type in the TPM password on each server, the BitLocker Drive Encryption must be temporarily disabled. Disabling the BitLocker Drive Encryption keeps the hard drive data encrypted. However, BitLocker uses a plain text decryption key that is stored on the hard drive to read the information. After the firmware updates have been completed, the BitLocker Drive Encryption can be re-enabled. Once the BitLocker Drive Encryption has been re-enabled, the plain text key is removed and BitLocker secures the drive again.
|
|
|
![[CAUTION: ]](images/caution.png) |
CAUTION: Temporarily disabling BitLocker Drive Encryption can compromise drive security and should only be attempted in a secure environment. If you are unable to provide a secure environment, HP recommends providing the boot password and leaving BitLocker Drive Encryption enabled throughout the firmware update process. This requires setting the |
|
|
To temporarily disable BitLocker support to allow firmware updates:
-
Click Start, and then search for
gpedit.mscin the Search Text box. -
When the Local Group Policy Editor starts, click Local Computer Policy.
-
Click Computer Configuration → Administrative Templates → Windows Components → BitLocker Drive Encryption.
-
When the BitLocker settings are displayed, double-click Control Panel Setup: Enable Advanced startup options.
To enable advanced startup options:
The following table describes TPM detection scenarios that you might encounter.
| Scenario | Result |
|---|---|
| If TPM is detected and enabled, the installation is not silent, and a system ROM must be updated. | A warning message appears. Select OK to continue. The installation is not canceled. |
If TPM is detected and enabled, the installation is silent, the /tpmbypass switch is not given, and any firmware updated must be applied to the server. |
No warning appears. A new log file is generated (%systemdrive%\cpqsystem\log\cpqstub.log). Because the installation is silent, the installation is terminated and cannot continue. |
| If TPM is detected and enabled with Option ROM Measuring, the installation is not silent, and a system ROM must be updated. | A warning message appears. After selecting OK, you can continue. The installation is not canceled. |
If TPM is detected and enabled with Option ROM Measuring, the installation is silent, the /tpmbypass switch is not given, and any firmware updated must be applied to the server. |
No warning appears. A new log file is generated (%systemdrive%\cpqsystem\log\cpqstub.log). Because the installation is silent, the installation is terminated and cannot continue. |
If TPM is detected and enabled, the installation is silent, the installation occurs, and the /tpmbypass switch is supplied. |
The installation occurs. |