How to use Hash of TPM from AD to reset your TPM password

re: How to use Hash of TPM from AD to reset your TPM password

Bryan Powell — Mon, 06 May 2013 20:21:19 GMT

I too am getting the error referenced by David. However, it still occurs whether or not the tpm file is accessed locally or from a USB or network share.

One thing I noticed is Windows 8 backup seems to have a 27 character hash, but your example is 28. Is our backup not working correctly? It is in the format as follows for Windows 8:

CN=<27 chararcter hash>,CN=TPM Devices,DC=domain,DC=company,DC=com

re: How to use Hash of TPM from AD to reset your TPM password

David Rich — Thu, 21 Mar 2013 17:51:40 GMT

hahaha DUMMY moment.

this method works fine but the .tpm file you create cannot be used from the local bitlocker encrypted drive

(duh you can't store your hash on the drive!)

the same file can be used to reset the key from a network share flash drive etc

re: How to use Hash of TPM from AD to reset your TPM password

David Rich — Thu, 21 Mar 2013 17:20:33 GMT

I know this is an old thread but i'm having the same problem as above. i have followed your steps, saved the file un utf-8 encoding, made sure file extensions were not hidden.

first off i cannot browse to it, i have to type in the path so it isn't showing up properly as a .tpm file.

when i do put in the path manually the result is tpm.msc telling me:

"If you build the file manually, verify that it has the correct syntax for a tpm owner password file."

re: How to use Hash of TPM from AD to reset your TPM password

Darrell Poteet — Thu, 08 Dec 2011 15:28:00 GMT

The article is excellent, but unfortunately the process does not work in our environment. We are doing a copy and paste of the TPM Hash from AD into a template created from your example. We are naming the file "machinename.tpm" but are denied the reset after browsing to the file.

Any thoughts as to what behavior would cause this?

re: How to use Hash of TPM from AD to reset your TPM password

Keenan Buck — Mon, 06 Sep 2010 20:15:01 GMT

A very good brief yet concise article ... Thank you