Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

60269

November 18th, 2012 19:00

cctk.exe --tpmactivation=activate MDT 2010 does not work

Hello

Dell Latitude E6330, BIOS A06 (latest as of today)

CCTK 2.1.1

MDT 2010.  Running CCTK during Windows (Version 7)

The command line "cctk.exe --tpmactivation=activate" does not activate the TPM chip.

Before this command I am importing an INI file using CCTK to set a bunch of BIOS settings which also includes the command to turn the TPM on.

I have cleared the TPM settings using the BIOS.  I have restored defaults.

Cheers

Robert

1.1K Posts

November 20th, 2012 09:00

I think there is an issue with the latest BIOS version regarding TPM activation with CCTK.  I'm not sure if you can revert to an older BIOS to workaround the issue until it is fixed.

November 19th, 2012 07:00

Make sure you are rebooting the system in between the "Enable" and "Activate" commands.  Also make sure you have a BIOS password set when activating via command line.

November 19th, 2012 14:00

I have tried the reboot between enable and activate but not setting a BIOS password.  I will give this a try.

Thanks for your response.

Cheers

Robert

November 19th, 2012 18:00

No go.  These are my commands in MDT

XCOPY source to C:\Temp\CCTK

Enable HAPI - hapint.exe -i -k C-C-T-K -p "hapint.exe"

Set BIOS Asset Tag - cctk.exe --asset=%OSDComputerName%

Apply BIOS Settings - cctk.exe -i e6330.ini (the ini file contains many settings one of them is enable TPM)

Set BIOS Password - cctk.exe --setuppwd=password

Restart Computer

Activate TPM - cctk.exe --tpmactivation=activate --valsetuppwd=password

At the BitLocker stage of the MDT sequence an error is generated that "Check to see if TPM is enabled".  And sure enough the TPM is enabled but not activated.

Seems to me that the CCTK will not set this option for this particular model.

Cheers

Robert

November 20th, 2012 14:00

Yes I agree.

I wont bother reverting to an older BIOS version.  We have around 250 laptops to build and running short on time.  And I would assume the latest BIOS is best for other features, cant really justify reverting to an older BIOS for just this reason.  The build team will just have to set the TPM manually before each build.  Will add about 30sec to a minute for each build.  Far from a show stopper.

Thanks for the responses

Cheers

Robert

1 Message

November 22nd, 2012 00:00

I second this issue.

I tried enabling and activating TPM on Dell Latitude E5430 and E6530 (both BIOS A07) using CCTK, for use with Bitlocker.

My steps are (scripted):

- Install Dell CCTK 2.1
- Set bios password
- Turn TPM ON
- Reboot
- Activate TPM
- Reboot

According to the log, everything works perfect..

Now, if i check TPM Activation status using CCTK, it returns 'Activated' - but if i check the actual setting in BIOS, TPM is ON, but it's Deactivated. Also tried running CCTK manually, same result. The Bitlocker activation script also detect it's deactivated, so encryption doesn't happen.

We're about to ship 300+ laptops, and unlike Robert i believe this is a critical error. Maybe not a showstopper, but it's forcing hands-on on a job that's supposed to be automated. So... if i'm missing something, please advice - and if not, please fix this Dell!

1.1K Posts

November 26th, 2012 10:00

I encourage you to open a formal support ticket for the following reasons:

1. To ensure that your issue is logged and is being worked on.

2. There may be an interim BIOS that is available.

5 Posts

November 30th, 2012 13:00

I opened a ticket and they confirmed there is an issue with the current BIOS version that prevents you from being able to properly set the TPM chip.  They said you can either downgrade to an A02 BIOS version or manually set it in the BIOS.  They are working on a fix in a future BIOS update, but didn't give an ETA.

1 Message

February 14th, 2013 09:00

Updated my E6530's to A09 and still having an issue.  Is it a BIOS issue or CCTK tools issue?

Running CCTK 2.1.1.0

February 14th, 2013 11:00

It's an issue with the current BIOS version on certain hardware (including the Latitude E4 Series).  We'll need to wait for an updated BIOS revision to get that piece fixed.  As Warren stated above, if you submit a support ticket then hopefully they'll be able to divert more resources to get it fixed sooner.

No Events found!

Top