I'm trying to get powershell's 8.1 tpm cmdlets to run on my WinPE 5 OSD 64 boot disk.  (Configmgr 2012 R2)

I've found, WinPE-SecureStartup, listed in the WADK source directory but not in the optional components of the Boot Image Properties.

Also tried using Dism with the Add packages (Optional Components Reference) but when I import it into SCCM and make bootable media, running powershell get-tpm errors out with: get-tpm  : The term 'get-tpm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify the path is correct and try again. I'm going to verify the path next.

Does anyone know how to add optional components to the SCCM boot image properties? It seems like that would be an easier way to go than starting from scratch with WADK and dism.

WinPE-SecureStartup is part of the default components, added by ConfigMgr, in the boot image. You can find it on the top of the Optional Components tab of the boot image.

"WinPE-SecureStartup is part of the default components, added by ConfigMgr, in the boot image."

Yes, your right its loaded by default.

I guess its not the component that needs to be added to run TPM Cmdlets in Powershell.

I've been able to run get-tpm from the full operating system of windows 8.1.

Is it possible to add software to a WinPE boot disk that will let you run it in a windows PE environment?

When I run powershell get-command it's not listed.

WinPE-PowerShell

Dependencies: Install WinPE-WMI > WinPE-NetFX > WinPE-Scripting before you install WinPE-PowerShell.

WinPE-SecureStartup

Dependencies: Install WinPE-WMI before you install WinPE-SecureStartup.

WinPE: Add packages (Optional Components Reference)

WinPE-PowerShell was my starting point.

It loads its prerequisites when you add it from the SCCM\boot image (x64) properties\ optional components.

Unfortunately when I boot the WINPE 5.0 with PowerShell 4.0 and manually launch Powershell and type:

get-command. It lists about 100 commands from all the loaded and unloaded modules.

But no tpm cmdlets or get-tpm.

I've compared my WinPE modules with the ones available by running powershell from a Windows 8.1 64 desktop.

By running get-module -ListAvailable -All

On the 8.1 64 desktop there is a module called TrustedPlatFormModule located  in the default module path:

c:\Windows\system32\WindowsPowerShell\v1.0\modules\TrustedPlatFormModule\trustedPlatformModule.psd1

WinPE uses the same path starting with X:\ but no TrustedPlatformModule directory or files are listed.

Has anyone actually got a response by typing get-tpm from a WinPE powershell command prompt?

If so what am I doing wrong here?

I put in a support case with Microsoft and they say that TPM Cmdlets won't run from WINPE at this Time.

I put in a support case with Microsoft and they say that TPM Cmdlets won't run from WINPE at this Time.

• Marked as answer by Daniel JiSunMicrosoft contingent staff, Moderator Friday, June 05, 2015 9:38 AM

Is there any update on this?

To me, it sounds weird since if you run a machine through deployment, you can actually manipulate bitlocker from PE (get ownership of TPM, set password, and so on).

I have a similar issue, I have a machine whose wrong pin has blocked the TPM (and the recovery key is missing). I am trying to use unblock-tpm to allow the system to accept pins again, and with that, the TPM will pass along the key to unlock the drive.

If this was a normal desktop/laptop, i would just swap the drives and use a full fledge OS, but unfortunately, this is a Surface Pro 3 tablet, and I don't have that choice.