Which is weird, because 2 Dell E7240’s side by side one works, one doesn’t. Same TS used.
Is it possible this is something with the BIOS? I mean these machines cannot be anymore same. And I am not sure what it is actually referencing. The options are the same. Is ‘%s’ supposed to mean something? It must not like this: --tpmactivation=activate Thanks, Kevin Johnston Junior System Administrator HALOGEN SOFTWARE INC<http://www.halogensoftware.com/>. Talent Management Solution of Choice Tel: 613.270.1011 Ext. 4450| Fax: 613.270.8311 From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, August 14, 2015 12:46 PM To: [email protected] Subject: RE: [mssms] Dell TPM error during OSD Dell - Internal Use - Confidential I see an error code of 106 in the log. Which is “Invalid argument for the provided option” based on the cross-ref here -> http://en.community.dell.com/techcenter/systems-management/w/wiki/1953.dell-client-configuration-toolkit-cctk-error-codes Thanks, Warren Byle Dell | Business Client Systems Management Product Manager office +1 512 724 2626 [email protected]<mailto:[email protected]> Client Command Suite<http://dell.com/command> Join the conversation Twitter: WarrenByle<http://twitter.com/WarrenByle> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Friday, August 14, 2015 9:49 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: RE: [mssms] Dell TPM error during OSD I thought I had attached a scrubbed version of the smsts.log Should be the TPM_Error.log file Thanks, Kevin Johnston Junior System Administrator HALOGEN SOFTWARE INC<http://www.halogensoftware.com/>. Talent Management Solution of Choice Tel: 613.270.1011 Ext. 4450| Fax: 613.270.8311 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Friday, August 14, 2015 10:40 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Dell TPM error during OSD does the smsts.log reveal anything, i didn't see you attaching that yet... On Fri, Aug 14, 2015 at 4:36 PM, Kevin Johnston <[email protected]<mailto:[email protected]>> wrote: Yes. I thought it was weird, so I upgraded from BIOS A14 to A15. Cleared out the TPM. Started over again and Still fails. I reimaged the machine without Bitlocker to see if it would fail anywhere else, and it worked fine. Then started over again, and still fails. I am almost tempted to just image it normally and activate the TPM myself (if that will work) but I was hoping this has been seen before. Thanks, Kevin Johnston From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Niall Brady Sent: Friday, August 14, 2015 10:26 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Dell TPM error during OSD as it's only happening on one machine have you tried clearing the tpm and upgrading the bios, then try again ? On Fri, Aug 14, 2015 at 2:45 PM, Kevin Johnston <[email protected]<mailto:[email protected]>> wrote: I have a Dell Latitude E7240. I have this one stubborn laptop that refuses to have the TPM activated during my OSD. All other E7240’s work fine but this one. In the smsts.log file I see this error: Failed to run the action: Activate TPM. Unknown error (Error:00000106; Source: unknown) My task sequence does the following (with what the command line is): Enable TPM Task: Enable HAPI - x:\CCTK\HAPI\hapint.exe -i -k C-C-T-K -p X:\CCTK\HAPI\ Set temp BIOS password -X:\CCTK\cctk.exe --setuppwd=12345 Enable TPM - x:\CCTK\cctk.exe --tpm=on --valsetuppwd=12345 Remove Temp Password - X:\CCTK\cctk.exe --setuppwd= --valsetuppwd=12345 Restart Activate TPM Task: Enable HAPI - x:\CCTK\HAPI\hapint -i -k C-C-T-K -p X:\CCTK\HAPI\ Set temp BIOS password - X:\CCTK\cctk.exe --setuppwd=12345 Activate TPM – This is where it fails - x:\CCTK\cctk.exe --tpmactivation=activate --valsetuppwd=12345 Remove Temp password - X:\CCTK\cctk.exe --setuppwd= --valsetuppwd=12345 Restart computer This is the first time I have ever had it fail, The Error lookup tool states: Insert the diskette for drive %1. I have attached a stripped version of the log. Thanks, Kevin Johnston
