We have Poweredge R760 and Poweredge R660xs servers in our infrastructure and all of them are connected to our on-premise OpenManage Enterprise appliance.
From the compliance report i noticed that there is a TPM Module update available (from version 7.2.3.1 to version 7.2.4.1).
However, this specific update fails on all servers when attempting to do it via OME.
I attempted to update the firmware manually but it gives me the following error: "This DUP requires TPM bootloader version 2.0.0.26 or earlier. Version 2.0.0.32 found.\nparts 948W4, 151Y6, 0PTVP, T2FR2, and VR2WC are supported. Parts T9CVK and K6K71 require the other DUP"
Note that the majority of servers are running ESXi version 8.0.3 and few of them are Windows Server 2025.
The error that i mentioned above was returned from a windows server.
I searched online and i found many other cases of people facing the same issue but i was not able to find a solution to that.
This could happen if you have other TPM part number installed.
How to fix it
Identify the TPM part in iDRAC
On any affected R760 / R660xs:Open iDRAC → Hardware → Inventory → Security (or similar) and note the TPM part number (you’ll see something like T9CVK, K6K71, 151Y6, 948W4, etc.).
You can also export the inventory via iDRAC/OME to confirm this at scale.
Match the correct TPM 7.2.4.1 DUPUse Dell’s support pages for your exact server model, but in general for 15G/16G PE:
Update manually on one test hostFor a Windows Server 2025 host (no BitLocker or with BitLocker suspended):Download the correct DUP (2XHC3 or 256M6) for R760/R660xs from Dell Support.
Run the .exe in Windows (elevated), follow prompts, then reboot when prompted.Verify in iDRAC: TPM firmware shows 7.2.4.1 and compliance clears for that host.For ESXi hosts you can either:Use Lifecycle Controller (F10) with the correct DUPs on a USB / network share.
Or mount the DUP via a live OS that supports the package, if Dell documents that method for these specific DUPs.Fix it in OpenManage EnterpriseOME’s catalog is almost certainly pointing one generic TPM update (e.g., 2XHC3) at all R760/R660xs, even the ones with T9CVK/K6K71. That makes compliance show “update needed” and the job then fails.
To resolve:Import both TPM DUPs into your OME / repository (2XHC3 and 256M6).
If possible, create two custom baselines:Baseline A with 2XHC3 for systems whose TPM inventory shows 948W4/151Y6/0PTVP/T2FR2/VR2WC.Baseline B with 256M6 for systems whose TPM inventory shows T9CVK/K6K71.Assign baselines accordingly (using device groups or filters based on a naming/tagging convention linked to TPM type).If OME can’t distinguish TPM part in rules, you may need to:Leave the generic catalog as-is but exclude TPM from global compliance, and handle TPM via dedicated baselines/groups; orAccept that OME will show “non‑compliant” but run the correct DUP manually or via an out‑of‑band job targeted only at the right subset of hosts.
with kind regards Martin/ Liebe Grüße Martin
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!
Like you mentioned in your last post i found the service tag of the servers and from Dell Support site i used it to identify the correct package for the update.
Then from the server's iDRAC i uploaded the package.
I will use this method for all because it will be the same procedure for all servers irrespective installed OS
Dell-Martin S
Moderator
•
3883 Posts
•
25810 Points
0
1
Posted February 19th, 2026 14:22
Hi,
you could check your service TAG too for part numbers on our Website.
But you could try the steps that I wrote earlier without checking it, because it seems to be the other modules.
For providing such information it would be better to do this not in an open for everyone contact method.
with kind regards Martin/ Liebe Grüße Martin
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!
DELL-Martin S
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell