I think there is a typo in the Powershell command. Try this instead:
*gwmi* *-Class* Win32_TPM *-Namespace* root\CIMV2\Security\MicrosoftTpm | *%
*{$_.IsEndorsementKeyPairPresent()}****
Note: I don't know what you are all talking about and haven't really
followed this particular thread. I just looked at the powershell command
and believe there was a typo in the syntax.
On Tue, Oct 1, 2013 at 3:13 PM, Murray, Mike <[email protected]> wrote:
> Are you using PowerShell to run this command? Can you give me some
> instruction, as I’m kind of a noob with PowerShell. :)****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Craig Andrew (OIZ)
> *Sent:* Monday, September 30, 2013 11:09 PM
> *To:* [email protected]
> *Subject:* AW: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> *gwmi* *-Class* Win32_TPM *-Namespace* root\CIMV2\Security\MicrosoftTpm |
> *%*{$oTPM.IsEndorsementKeyPairPresent()}****
>
> ** **
>
> If the machine is delivered with TPM enabled but not activated then there
> will be. In some other circumstances it is possible this pairing may exist.
> Basically you cannot activate zero-touch when this pairing exists so it is
> worth checking.****
>
> ** **
>
> ** **
>
> *Von:* [email protected] [
> mailto:[email protected] <[email protected]>] *Im
> Auftrag von *Murray, Mike
> *Gesendet:* Montag, 30. September 2013 20:13
> *An:* [email protected]
> *Betreff:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> Is there a way to see if there is existing ownership? I wouldn’t think
> there would be.****
>
> ** **
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Craig Andrew (OIZ)
> *Sent:* Friday, September 27, 2013 2:40 PM
>
> *To:* [email protected]
> *Subject:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> Hi Mike,****
>
> Did you try with a space instead of a = ?****
>
> Have you checked for existing ownership pairings?****
>
> Andrew****
>
> ** **
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Murray, Mike
> *Sent:* Freitag, 27. September 2013 23:22
>
> *To:* [email protected]
> *Subject:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> Well, running these from a command prompt at an existing imaged
> workstation just don’t seem to do anything. Argh.****
>
> ** **
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Powell, Tom
> *Sent:* Friday, September 27, 2013 3:10 AM
>
> *To:* [email protected]
> *Subject:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> In our TS we have:****
>
> ** **
>
> path\CCTK --setuppwd=PASSWORD****
>
> ** **
>
> path\CCTK --tpm=on --valsetuppwd=PASSWORD****
>
> ** **
>
> A reboot****
>
> ** **
>
> path\CCTK --tpmactivation=activate --valsetuppwd=PASSWORD****
>
> ** **
>
> A reboot****
>
> ** **
>
> path\CCTK --setuppwd= --valsetuppwd=PASSWORD****
>
> ** **
>
> Reboot****
>
> ** **
>
> You can also use –logfile=\path you want\... for each step****
>
> ** **
>
> Tom****
>
> ** **
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Craig Andrew (OIZ)
> *Sent:* 27 September 2013 09:56
> *To:* [email protected]
> *Subject:* AW: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> cctk.exe --tpmactivation=activate --valsetuppwd=password****
>
> This does not work. There is an error in the cctk code. You need to use
> following (note space instead of =):****
>
> cctk.exe --tpmactivation=activate –valsetuppwd password****
>
> ** **
>
> Also, if there is an ownership pairing on the chip then it will not
> activate, you will need the clean the chip first.****
>
> See my post here:****
>
>
> http://andrewdcraig.wordpress.com/2013/02/18/enable-tpm-in-a-task-sequence-dell/
> ****
>
> ** **
>
> I haven’t yet found a way to get around the f10 prompt, and I don’t
> believe it can be done because of the nature of the process of cleaning an
> ownership pairing. Rebooting between each step is not necessary in many
> cases, that is why I do it, to catch the others. Dell say it can all be
> done silently but I have yet to see a working model which involves cleaning
> a pairing that doesn’t involve interaction.****
>
> ** **
>
> Andrew****
>
> ** **
>
> *Von:* [email protected] [mailto:[email protected]
> .com <[email protected]>] *Im Auftrag von *Murray, Mike
> *Gesendet:* Freitag, 27. September 2013 01:02
> *An:* [email protected]
> *Betreff:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> Well, I tried all of the following commands at the command prompt, they
> seemed to work OK. But when I checked BIOS, TPM was still not activated.**
> **
>
> ** **
>
> cctk.exe --setuppwd=password****
>
> ** **
>
> cctk.exe --tpm=on --valsetuppwd=password****
>
> ** **
>
> cctk.exe --tpmactivation=activate --valsetuppwd=password****
>
> ** **
>
> cctk.exe --setuppwd= --valsetuppwd=password****
>
> ** **
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Niall Brady
> *Sent:* Thursday, September 26, 2013 2:43 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] Using SCCM and Dell CCTK****
>
> ** **
>
> correct as I show in the link above, (look for Remove Temporary password
> in the screenshot)
>
> also note that i'm doing everything in WinPE hence the cctk 'hapi'
> references. Most people do the tpm stuff while still in Windows. ****
>
> ** **
>
> On Thu, Sep 26, 2013 at 11:37 PM, Murray, Mike <[email protected]>
> wrote:****
>
> So I could initially set the password, then remove it? ****
>
> ****
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Powell, Tom
> *Sent:* Thursday, September 26, 2013 2:31 PM
> *To:* [email protected]
> *Cc:* [email protected]****
>
>
> *Subject:* Re: [mssms] Using SCCM and Dell CCTK****
>
> ****
>
> Yup. ****
>
> ****
>
> Set bios password / enable tpm / other bios settings / remove bios
> password if not required. ****
>
> ****
>
> Kinda the same with HPs tool as well. ****
>
> ****
>
> Tom
>
> Sent from my iPhone****
>
>
> On 26 Sep 2013, at 22:14, "Keiffer, Scott" <[email protected]>
> wrote:****
>
> I am pretty sure you have to have a bios password set in order for the
> activation to actually work.****
>
> ****
>
> ---------------****
>
> Scott Keiffer****
>
> Senior Systems Administrator****
>
> Cockrell School of Engineering - IT Group****
>
> University of Texas at Austin****
>
> [email protected]****
>
> 512-814-8872****
>
> ****
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Murray, Mike
> *Sent:* Thursday, September 26, 2013 3:49 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ****
>
> I created an EXE with the CCTK that should enable TPM and activate it. The
> log (attached) says successful in both steps, but TPM is still not
> activated (it is on, though).****
>
> ****
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Murray, Mike
> *Sent:* Thursday, September 26, 2013 12:39 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ****
>
> I guess I should’ve clarified, I’m hoping to enable TPM on existing
> clients in SCCM. We will also add it to our TS when doing OSD, but we have
> a bunch of machines out there without it enabled.****
>
> ****
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *[email protected]
> *Sent:* Thursday, September 26, 2013 12:15 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Using SCCM and Dell CCTK****
>
> ****
>
> Glad to hear that CCTK is being put to good use! As always, let me know
> if you see anything that we can do to make your life easier with Dell
> systems management tools.****
>
> ****
>
> Thanks,****
>
> ****
>
> ****
>
> *Warren Byle*****
>
> *Dell* | Business Client Systems Management****
>
> Product Manager****
>
> *office* +1 512 724 2626****
>
> [email protected]****
>
> ****
>
> Join the conversation****
>
> Dell TechCenter <http://www.delltechcenter.com/>****
>
> Twitter: WarrenByle <http://twitter.com/WarrenByle>****
>
> ****
>
> Warren****
>
> ****
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Niall Brady
> *Sent:* Thursday, September 26, 2013 1:45 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] Using SCCM and Dell CCTK****
>
> ****
>
> and here's an older post i did about the modular cctk bits in the task
> sequence, I use the same methodology in CM12
>
>
> http://www.windows-noob.com/forums/index.php?/topic/3875-customising-windows-7-deployments-part-5/
> ****
>
> ****
>
> On Thu, Sep 26, 2013 at 8:43 PM, Niall Brady <[email protected]> wrote:****
>
> works great, you don't have to add them to the boot wim files if you don't
> want to and instead you can be modular in the task sequence,****
>
> this task sequence includes examples of just that:-****
>
> - CM12 in a Lab -The CM12 BitLocker FrontEnd HTA -
> video<http://www.windows-noob.com/forums/index.php?/topic/7636-the-cm12-bitlocker-frontend-hta-video/>
> ****
> - CM12 in a Lab - The CM12 BitLocker FrontEnd
> HTA<http://www.windows-noob.com/forums/index.php?/topic/7294-the-cm12-bitlocker-frontend-hta>
> ****
>
> if only all OEM manufacturers produced tools for doing bios actions as
> Dell do, kudos to Dell !****
>
> ****
>
> ****
>
> On Thu, Sep 26, 2013 at 8:39 PM, Murray, Mike <[email protected]>
> wrote:****
>
> Anyone have experience deploying BIOS settings via SCCM and the Dell CCTK?
> I am specifically interested in enabling the TPM chip, as our security
> office is interested in using Bitlocker. I found this doc:****
>
> ****
>
> http://en.community.dell.com/techcenter/extras/m/white_papers/20209083.aspx
> ****
>
> ****
>
> I’m just interested in hearing your stories of doing this, particularly
> with TPM. Any recommendations, gotchas, etc.****
>
> ****
>
> Also, if we do enable TPM, is there more that needs to be done on the
> client?****
>
> ****
>
> ****
>
> Best Regards,****
>
> ****
>
> Mike Murray****
>
> Desktop Management Coordinator - IT Support Services****
>
> California State University, Chico****
>
> 530.898.4357
> [email protected]****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
>
