"CCTK --tpmactivation=activate" sometimes fails to enable TPM
I am creating an SCCM Task Sequence to deploy Windows 7 with BitLocker encryption.
I have the command "CCTK.exe --tpmactivation=activate --valsetuppwd=password" in the Task Sequence, but I find that often, this does not work. After the command has executed, I issue a "reboot" task sequence step so that I can manually check in the BIOS to verify the TPM is active, and often I find that it is not. Other times it is sucessfully activated, even on the same computer.
I have made the Task Sequence execution pause after the above command has been issued, and opened a command prompt by pressing "F8" and if I issue the same command manually then reboot, TPM is activated.
I have also made the Task Sequence execution pause and opened a command prompt by pressing "F8" then copied the smsts.log file locally so I can examine the log file, and I find that it appears to state that TPM was activated, as can be seen in this log extract:
Executing command line: smsswd.exe /run: x:\CCTK\X86_64\CCTK.exe --tpmactivation=activate --valsetuppwd=password
=======================[ smsswd.exe ] =======================
PackageID = ''
BaseVar = '', ContinueOnError=''
SwdAction = '0001'
Command line for extension .exe is "%1" %*
Set command line: Run command line
Working dir 'not set'
Executing command line: Run command line
Process completed with exit code 0
tpmactivation=activate
Command line returned 0
Process completed with exit code 0
!--------------------------------------------------------------------------------------------!
Successfully complete the action (Activate TPM) with the exit win32 code 0
However, rebooting and going into the BIOS, i find that TPM is not activated.
Does anyone have any ideas why this is so unreliable?
This sounds like a timing issue. Can you run another process before rebooting to see if it will stabilize your output. It appears from the logs that the TPM activation is attemped successfully, but somehow it's getting broken by the task sequence.
I removed the task sequence step to reboot the computer, which I only added so that I was able to trap the restart and verify that TPM was activated within the BIOS. Once I removed the restart and simply allowed the task sequence to continue, I have not had any problems with the TPM failing to be enabled.
It does look like the act of initiating a reboot at that time did in fact "break" the TPM activation and was a timing issue, as you described.
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.
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?
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
DELL-Warren B
1 Rookie
•
1124 Posts
3768
0
Posted September 9th, 2011 14:00