TPM Step-By-Step Guide - 2.14
TPM Step-By-Step Guide - 2.14
Step-by-Step Guide
DMIFIT Version 2.14 and later
Updated June 2017
HP has been moving to utilize version 2.0 of the Trusted Platform Module (TPM)
Firmware on its newer products. The previous version of TPM is version 1.2. As
there will be the possibility that customers have either upgraded or downgraded
the version of TPM firmware they are using from what was originally installed on
the system (or what was the default setting for that system), field engineers
need to be able to adjust TPM settings when replacing a system board.
Note: The procedures described in this guide are for HP Commercial Notebooks, Desktops and RPOS only. HP
Workstations will have the replacement system board set to the TPM firmware version of the system as it was
ordered / requested.
HP Desktop DMI Programming Step-by-Step Guide
Contents
HP TPM Strategy ........................................................................................................................................... 3
How to Determine the Required TPM Firmware Version ............................................................................ 6
New TPM Label on Replacement System Boards ....................................................................................... 8
Process Overview.......................................................................................................................................... 9
Configuring TPM firmware - Notebooks .................................................................................................... 11
Setting TPM Firmware Version - Desktops ................................................................................................ 15
What if TPM is Set Incorrectly ..................................................................................................................... 20
2
HP Desktop DMI Programming Step-by-Step Guide
HP TPM Strategy
HP is working to make the transition from TPM V1.2 to TPM V2.0 as smooth as possible. New systems
introduced in 2016 and beyond will have the latest TPM V2.0 firmware as a default. In addition, replacement
system boards for these products will be shipped with TPM set to V2.0. Older products or products that are
currently shipping (sustaining) in 2016 will have TPM set to V1.2 as default and replacement system boards for
those products will also have TPM set to V1.2. When the next generation of these products are introduced, they
will begin using the TPM V2.0 firmware.
The following table summarizes the TPM firmware default options by operating system.
*Hybrid Platforms are Intel Skylake processor in a Kabylake chipset, or AMD Carrizo processor in
Bristol Ridge chipset.
HP Desktop DMI Programming Step-by-Step Guide
4
HP Desktop DMI Programming Step-by-Step Guide
Smaller customers may not know their TPM firmware version. These customers are less likely to have changed
the firmware version or ordered a specific SKU with a unique TPM firmware version from the default version for
that system. In this case, the replacement system board likely already includes the correct TPM firmware
version.
3. View the TPM version of the current system board. The following graphic shows an example of a TPM
configured to V1.2.
6
HP Desktop DMI Programming Step-by-Step Guide
Operating System
Understanding what Operating System the customer is using can be useful in trying to determine if the TPM
firmware needs to be changed. As a general rule, customers running Windows 7 Operating System will most
likely be using TPM V1.2. If the customer is running the Windows 10 operating system, it is most likely that they
will have moved to TPM V2.0. In addition:
• For Windows 7, Windows 8.X, and Windows 10, a 64-bit operating system is required for TPM 2.0. A
32-bit operating system cannot run TPM V2.0.
• Enterprises can create their own images with Windows 10 32-bit with retail or volume license bits
directly from Microsoft, but TPM V2.0 does not work with Windows 10 32-bit.
HP Desktop DMI Programming Step-by-Step Guide
It is important to note that only system boards that support the new HP Common Core BIOS will feature the TPM
labels. Older system boards will not feature the label and will not require the field technician to configure TPM.
8
HP Desktop DMI Programming Step-by-Step Guide
Process Overview
As part of the system board replacement process, configuring the TPM Firmware version should take place after
updating the Intel ME Firmware but before Programing DMI, Committing ME (if applicable) and Locking the
System Board. As always, the first step in the process will be to gather all of the appropriate information. A
high-level overview of the process is outlined below:
Gather
Information &
Determine TPM
Update Intel ME
Firmware
Set TPM
Program DMI
Commit ME
Confirm Boot to
Windows
Lock MPM
HP Desktop DMI Programming Step-by-Step Guide
• Systems with BitLocker or other encryption should be unlocked before programming the DMI.
Ask the customer to disable the encryption before service. If the customer is not able to do
this prior to service, the customer will need to provide the recovery key.
• Remind the customer that with any system board replacement, the customer will need to use
their recovery key to re-create the encryption key stored by the new TPM. This is the only way
that the customer will be able to access their encrypted drive after system board replacement.
• Run the Intel ME Firmware Update Utility (the utility will run automatically upon booting to the
DOS USB Key).
10
HP Desktop DMI Programming Step-by-Step Guide
Important:
Tool indicates
current version
Important:
of TPM on the Tool provides a
system board. menu of options
available and
what to type to
run each option.
12
HP Desktop DMI Programming Step-by-Step Guide
2. At the prompt, type the appropriate file name to run the corresponding utility. In the example above,
you could type either of the following two commands:
Command Action
Note: Note that these menu options will change based upon your system. You should identify the action
required and enter the corresponding command line as shown on your screen.
Note: If the system board is already configured with the latest version of TPM V1.2, you will not see the option to
configure the latest version of TPM V1.2. You will only be presented the option to configure to V2.0.
For example, to switch from TPM V1.2 to TPM V2.0, type: 121to20.nsh<enter>.
After completion, the utility will confirm that the TPM firmware configuration was successful and the utility
will return you to the prompt.
Important:
Confirm that you
are set to the
version of TPM
required by the
customer.
14
HP Desktop DMI Programming Step-by-Step Guide
1. Press the Space Bar to continue boot and immediately press the Escape key.
This will take you to the Start-Up Menu.
16
HP Desktop DMI Programming Step-by-Step Guide
Important:
Tool indicates
current version
Important:
of TPM on the Tool provides a
menu of options
system5.board.
available and
6. what to type to
run each option.
Important: The file
name to type to run the
appropriate utility is
shown here.
7. At the prompt, type the appropriate file name to run the corresponding utility. In the example above,
you could type either of the following two commands:
Command Action
For example, to switch from TPM V1.2to TPM V2.0, type: 121to20.nsh <enter>.
After completion, the utility will confirm that the TPM firmware update was successful and the utility will
return you to the prompt.
8. At the prompt, reboot the system. The system returns to the “Panic Mode” screen.
Confirm TPM firmware version / TPM Enabled
Important:
Confirm that you
are set to the
version of TPM
required by the
customer.
21. Once the TPM settings are confirmed, you can proceed to program DMI Information under Main > Set
Machine Unique Data.
As the system is still in panic mode, it should lock MPM once the correct system information has been
entered.
18
HP Desktop DMI Programming Step-by-Step Guide
TPM on Windows 7
On a Windows 7 system that was not specifically configured to run TPM 2.0 (QFE with partition scheme changed
from MBR to GPT), we saw no impact on the boot process / recovery key entry when TPM was set incorrectly.
However, when the system is shut down and rebooted, it asked for the recovery keys again. This means that a
field agent would not detect any immediate issues on a Windows 7 system if they set TPM incorrectly. However,
upon reboot, the system would ask the customer for the recovery keys again. If uncertain, field agents should
reboot twice to confirm that the encryption keys regenerated TPM correctly. This use case (Windows 7 with TPM
2.0) is considered be a limited possibility as it takes specific steps by the customer to run TPM 2.0 on a Windows
7 system. As such, the customer would know if they changed TPM.
20