VxRail: 14G Nodes Disable an Active TPM 1.2 Module Permanently or Upgrade to a TPM 2.0 Module by Temporarily Disabling the TPM 1.2
Summary: This article describes two methods of handling nodes with active TPM 1.2 modules that you are planning to upgrade to ESXi 8.0 and later. No reimaging is required with these steps. You can disable the active TPM 1.2 module permanently or upgrade the active TPM 1.2 module to a TPM 2.0 module by temporarily disabling the TPM 1.2 module before the upgrade. ...
Symptoms
This article describes two methods of handling nodes with TPM 1.2 modules:
- Disabling an active TPM 1.2 module permanently before the upgrade
- Upgrade from an active TPM 1.2 module to a TPM 2.0 module by temporarily disabling the TPM 1.2 module before the upgrade
Cause
Article 204703 is the preferred method for dealing with Dell VxRail: Clusters with 14G nodes that have an active TPM 1.2 module either fail the VxRail 8.0.x LCM precheck with an error message or a warning message.
Resolution
Prerequisites:
- Follow article 204006 Dell VxRail: How to gather the recovery keys for TPM security enabled VxRail nodes to capture the recovery keys from all the nodes.
The recovery keys are needed if there is an incident during TPM upgrade that necessitates a replacement of the motherboard, such as snapped plastics, slot damage during removal, ESD damage, and so forth.
- Verify that the vSAN cluster is in a healthy state.
Log in to your vCenter and go to VxRail Cluster > Monitor > vSAN > Skyline Health and ensure the vSAN is healthy. If there are any errors or warnings, resolve them before continuing. The only exception to this is if you are using a system that is not connected to the Internet and the errors are related to Internet access.
- Disable any VMware vSphere services that you have that are using the TPM 1.2 module.
- The TPM 1.2 modules in the current nodes must be functioning (no hardware errors).
- OPTIONAL: If you plan on upgrading the TPM 1.2 module with a TPM 2.0 module, you must procure (contact Dell Sales) a TPM 2.0 module for every node you want to upgrade.
Resolution Steps:
Estimated Time:
- Disable TPM Module: 20 minutes per node (the node reboot time and how long a node takes to go into maintenance mode affects the time).
- Powering off and replacing the TPM Module (optional): 15 minutes per node
The recommendation is to do this procedure one node at a time. If this is a large cluster with an N+2 or greater number of nodes, it may be possible to do more than one node at a time. Care should be taken to understand the impact to workloads and data availability before considering that approach.
- Go to your vCenter Web Client and log in with an administrative account.
- Go to the main menu and select Inventory.
- Expand the VxRail cluster.
- Right-click your node and select Maintenance Mode > Enter Maintenance Mode.
- Ensure Move powered-off and suspended virtual machine to other hosts in the cluster is checked and that Ensure accessibility is selected next to vSAN data migration.

- Click OK and wait until the node enters maintenance mode before moving onto the next step. You can monitor the progress in the Recent Tasks pane.
- Set the TPM Security property to Off through iDRAC or BIOS of the node.
- iDRAC instructions:
- Log in to the iDRAC of the node.
- Go to Configuration > BIOS Settings > System Security.
- Set TPM Security to Off.
- Click Apply.
- Click Apply And Reboot.
- Go to Maintenance > Job Queue.
- Monitor the job queue and wait for the tasks to finish successfully.
- BIOS instructions:
- Log in to the iDRAC of the node.
- Under Virtual Console, go to Start the Virtual Console and wait for it to open.
- You see the ESXi direct console interface. Press F12 on the keyboard and enter your root password when prompted.
- Press F11 to restart the server.
- While the server is booting, press F2 to enter System Setup.
- On the System Setup Main Menu screen, click System BIOS > System Security Settings.
- Next to the TPM Security option, select Off.
- Save the setting.
- Restart your system and wait for ESXi to boot.
- Get your node's Managed Object ID (MOID).
- Go to https://<vcenter_ip>/mob and browse to your VMware vCenter’s Managed Object Browser (MOB).
- When prompted for a username and password, enter the same credentials, you would use to access your vCenter Web Client. Ensure that this account has administrator access.
- Select the active link in the value column for each of the following items: Content > rootFolder > childEntity > hostFolder > childEntity
- This page displays a host value. The Managed Object ID (MOID) for each host displays next to host. In the example below they are highlighted in yellow.

- Browse to https://<vcenter_ip>/mob/?moid=<Node_MOID>&doPath=capability
- Check the tpmVersion. If the procedure worked correctly, the value should be Unset.

- OPTIONAL: Power off the node and follow this procedure from the Dell PowerEdge R640 Installation and Service Manual to upgrade the TPM 1.2 module to the TPM 2.0 module.
- If the node is powered off, power it on and wait for ESXi to boot.
- Browse to your vCenter Web Client and log in with an administrative account.
- Go to the main menu and select Inventory.
- Expand the VxRail cluster.
- Right-click your node and select Maintenance Mode > Exit Maintenance Mode. Wait for the host to exit maintenance mode.
- From the vSphere Web Client, go to VxRail Cluster > Monitor > vSAN > Skyline Health and ensure the vSAN is healthy. If there are any errors or warnings, resolve them before continuing. As mentioned earlier, the only exception to this would be if you are using a system that is not connected to the Internet and the errors are related to Internet access. All other errors and warnings should be actioned.