CCTK --tpmactivation=activate Fails in OSD

hi,

Did  you enable the TPM first ?

The command is the following :

cctk.exe --tpm=on --valsetuppwd=password

If you did, then you have to activate the TPM manually (Via the BIOS setup) to be able to clear it.

I have had this problem a couple times. What resolved it for me was to proceed with my imaging process to install Windows 7, and then launch tpm.msc to clear the TPM from there.

Hi J3L2404,

Please refer to the video mentioned below for enabling and activating TPM using DCC (CCTK).

Note that clearing TPM is possible only in BIOS screen due to security restrictions.

This issue seems to be something hardware related. I am able to image other laptops using this same task sequence and it works just fine. The TPM settings are done in the TS using CCTK.

Hi J3L2404,

So, were you able to clear the TPM that was activated using DCC(CCTK)?

I'm not the original poster.. but no I never clear the TPM using CCTK because once it's set we don't care what it's set to as long as it's active and had ownership taken

Reviving this older thread.... The computer which I originally posted about was finally resolved somehow. One of the Technicians here was able to get it to image eventually but we are not sure what he did to actually solve the problem. Now we are having the exact same issue again. It seems like the issue arises when a laptop TPM was previously configured using CCTK and we are trying to reimage it again. What we would typically do is go into the BIOS and clear the TPM before imaging the laptop. This has always worked in the past, at least until these two recent computers.

The commands I run in my task sequence are in WinPE:

•  x:\CCTK\X64\HAPI\hapint -i -k C-C-T-K -p X:\CCTK\X64\HAPI\
• x:\CCTK\x64\CCTK.exe --setuppwd=password
• X:\CCTK\x64\CCTK.exe --tpm=on --valsetuppwd=password
• Restart the PC back in to WinPE
• x:\CCTK\X64\HAPI\hapint -i -k C-C-T-K -p X:\CCTK\X64\HAPI\
• x:\CCTK\x64\CCTK.exe --tpmactivation=activate --valsetuppwd=password
• x:\CCTK\x64\cctk --setuppwd=  --valsetuppwd=password
• Restart the PC back in to WinPE

The failure is happening on the step where we do --tpmactivation=activate --valsetuppwd=password. The error is:

Error in Setting the Value. Note: To set TPM - 1. Admin Password must be set , 2. TPM must not be owned and 3. TPM must be deactivated. 

Command line returned 262 

Process completed with exit code 262 

Hi Jmarcum, 

Please give us information on System Model number and the BIOS version of the machine where you see the issue. And also please give a try with the latest Dell Command | Configure 3.1 (cctk) version here. 

Thanks, 

Karthik.C

Would it be okay to simply replace cctk.exe in my ConfigMgr package with the new one or do I need to do more than that?

This is happening on a Latitude E6550 and it was also doing the same on a E6440. Both are using the latest BIOS.

We are having the same problem in our organization. Using the latest version of cctk we are able to Enable TPM but it will not activate using cctk. I need to deploy this to 1600 plus end users and really dont want to have to "touch" each one for the Activation part. Please provide a solution. Thanks!

Hi Jmarcum, 

Please install a new version of Dell Command | Configure ( cctk 3.1 ) and create a new SCE.

Regards,

Karthik.C

Hello,

I am running into the same problem on the Latitude E6420. Using CCTK 3.1, BIOS version A22. I am using CCTK with MDT, and other Latitude laptops have been working fine. The above issue occurs when trying to activate TPM (after Enable or if Enable is already set). I have been using this model to test TPM and BitLocker, and the only difference on this laptop, compared to the others that are working fine, is that it was BitLockered. But, I cleared TPM, deactivated it, and turned it off, before deploying again. Are there steps that must be taken prior to reimaging a Dell that previously had an encrypted drive so CCTK activation will work?

CCTK will support only TPM enable, disable and activation.  Hard drive has to be decrypted before working or enabling TPM through BIOS or  CCTK