NPCT750 7.2.2.0 TPM Firmware Update Issue

Question

Hi all, I'm trying to add the new NPCT750 7.2.2.0 firmware update to an SCCM Operating System Deployment (OSD) task sequence but there seems to be an issue with the new package on the Dell Latitude 7390 and Optiplex 7070.I am updating and configuring the BIOS (ensure TPM is activated etc.) in WinPE before applying the operating system. All the steps I'm running below worked fine with the previous 7.2.0.2 A03 update. I run these steps after the 'Setup Windows and Configuration Manager' task sequence step, so this is taking place within the newly-installed Windows OS, not the WinPE environment. I have validated that all these steps work when running the commands and restarting test computers manually outside of an OSD task sequence. The important steps look like this:Disable BitlockerDisable TPM auto-provisioning and clear the TPM with PowerShell>Disable-TpmAutoProvisioning>(Get-WMIObject -Namespace 'root\CIMV2\Security\MicrosoftTpm' -Class Win32_TPM).SetPhysicalPresenceRequest(14)Restart computerInitialise TPM with PowerShell>Initialize-TpmRun TPM firmware update with command line>DELLTPM_NPCT750_7.2.2.0_v1.exe /s /p=xxx /l='xxx'Restart computerEnable TPM auto-provisioning with PowerShell>Enable-TpmAutoProvisioning The log shows that the firmware update tool is completing successfully with 'Exit Code = 2 (Reboot Required)', but after the subsequent restart the firmware is not updated. Again, this same set of steps works for the old 7.2.0.2 A03 update for the Latitude 7390, and the firmware will be updated after the restart. I have also attempted adding things like 'cmd / c' and 'start /wait' before the .exe file, in case the task sequence was progressing before the firmware update completed (not supported by the success exit code in the log, but I thought it was worth attempting), but this does not fix the issue. Do you have any recommendations for successfully running this TPM firmware update in an OSD environment? Can this be investigated as a potential issue with the firmware update utility? Many thanks!

SamV01 · Answer

Turns out the error was on my end. When I paid attention to what was happening on screen when the computers restart to apply the firmware update, an error came up to say the TPM was owned and the update failed. This was after the firmware update utility had run in Windows and reported a success.

Removing the 'Initialise TPM' step fixed the ownership problem. I'm not sure why this was a problem as this step worked with the 7.2.0.2 update utility, and the 7.2.2.0 update utility didn't throw any errors to suggest the TPM was owned. It may be ownership didn't apply until Windows restarted to apply the update, after the utility had been run.

Latitude

Was this post helpful?