"CCTK --tpmactivation=activate" sometimes fails to enable TPM

"Which systems and BIOS versions are you using. This issue was addressed on some systems with a BIOS update."

Hope someone is still monitoring this thread.  I have the same problem with my test machine, a Lattitude E6500.  If I run the SCE to activate, the log says the activation was successful, but when I run CCTK --tpmactivation after a reboot, the TPM is NOT activated.  If I use the Windows 7 TPM console, I can activate the TPM successfully, but I can't automate that.

BIOS version on the test machine is A25. dated 4/13/2011.

Thanks,

Tom

Hi Thomas,

The support team will ask for you to try the latest BIOS (A27 from 5/5/12) before doing anything.  Can you upgrade the BIOS and let me know if that affects your issue?

Warren

Forgot to post the code.... Here it is:

###########################################################################
#
# NAME: Enable-TPM.PS1
#
# AUTHOR:  Dustin Hedges
#
# COMMENT: Attempts to activate the TPM chip using manage-bde.exe.
#
# VERSION HISTORY:
# 1.0 4/4/2012 - Initial release
#
###########################################################################

$cmd = "$env:WinDir\System32\manage-bde.exe -TPM -TurnOn"
Invoke-Expression $cmd | Out-Null
switch ($LASTEXITCODE) {
 
	-1 {
 
	Write-Host TPM Already Activated
	Exit 0
	}
	-2147217406 {
 
	Write-Host "ERROR: A compatible Trusted Platform Module (TPM) was not detected."
	Exit 1
	}
	default {
 
	Write-Host "Last Exit Code $LASTEXITCODE"
	Exit $LASTEXITCODE
	}
}

Hi Warren,

Upgraded BIOS to version A27.  Same behaviorl.  The SCE log says activation is successful, but the TPM is not activated.  Next steps?

Thanks,

Tom

we are having a similiar issue using on e6410 bios version 11. We are issuing the cctl tpmactivation=activate,   it returns.  After doing a cctk --tpmactivation command it says deactivate. We have manually rebooted and stil showing deactivated.

This has occured on a few e6140,  we are using the tpmactivcate command to prepare for a mbam/bitlocker deployment on a large number of machines.

Update: during testing i have found that if tpm was on already, the tpmactivation worked.  If tpm had to be turned on, i had to reboot after turning on tpm, then the tpmactivation worked. 

of course having cctk report it as activated when it was not is super annoying.

As others have mentioned tpm ownership needs to be off as well

Hi!

I have this exact problem, but only with the new Latitude E6230.
My package works perfect on several Latitude models but this week we got an new E6230 and it
looks a little bit different... For example, the Windows key is the icon for Windows 8. 

I have tried the solution you mentioned but it doesnt work! All of the other options like
setting password or turning on the TPM works, but it still deactivated. 

Does this have to do with a newer bios or something? 

I am having an issue with 'cctk Version 2.1.1 137 (Windows - Sep 24 2012). I have a Dell Optiplex 620, Bios Ver A07.

The "tpm" and "tpmactivation" commands are not appearing in the list of commands you get from the --help command. I do however see the tpm and tpm activation in the GUI portion where you extract .exe files etc.

Does anybody have an idea on what may be causing this issue?

According to Dell web site, BIOS is at least at A11: www.dell.com/.../driverdetails

I am not a Dell employee, I cannot explain why they would ship you a machine with an old BIOS revision installed.

Well... The computers that doesn't work is brand new...So hopefully Dell doesn't  ship out brand new computers with too old bios.

And like i said, it's only the newest model that this doesn't work with. All the other (older) models works great!

Regards