cctk 2.2.1 won't activate TPM on Newer model E6440, E7240 etc

here is the boise after running CCTK in osd ts. it won't activate.

Hi Ultra, 

This error likely indicates that TPM was previously owned (assuming this was a reimage).  I too only just started to notice this behavior with newly released versions of Dell BIOS on the E7000 series (haven't tested the E6430 series units yet).

To clear ownership the easiest way is to Clear TPM from the BIOS Screen.

FYI, you can check a full listing of CCTK exit codes here: http://en.community.dell.com/techcenter/systems-management/w/wiki/1953.dell-client-configuration-toolkit-cctk-error-codes.aspx

hi Dustin,

  thanks for  your reply. It makes sense because these are reimage computers. Now how can clear with command line, because computers are all over the world and can't have my tech going on each imaging computer and clear it, beat the purpose of OSD imaging.

thanks

I feel your pain and am in the exact same situation currently.  I am (presently) convinced that this was a change made in newer BIOS releases for the E6430/E7440 series Latitudes (and possibly some other models) however I haven't had the time to prove it out.

Rolling back to an older version of BIOS using the /f switch, taking ownership and then trying it would tell us if the behavior is CCTK or BIOS.  If you can, try rolling back 2 releases and test it.

i had roll back to A01, still same issue

anyone??/

Hi, I am working on getting a response to the queries. 

Thanks

Hi,

Currently CCTK won’t support TPM “clear” operation due to security reason and we can do “clear” operation only from BIOS screen.

Thanks,

Keerthan

Hi, Currently CCTK won’t support TPM “clear” operation due to security reason and we can do “clear” operation only from BIOS screen. Thanks, Keerthan

Are there any plans to address this.  We've had issues with 6430's and 6440's.  However, its not affecting every device, but I do see IsSrkAuthCompatible errors in the SCCM log.  Having to clean this manually before each reimage or even new deployment is tedious, and not a good solution.

Thanks

Matt