Skip to content

damaged client after setup? no self singed cert

Featured Replies

hi,

 

my client runs through the whole setup. All seemed to work well.

But i after SCCM my client shows me no certificate.

 

Regards

J

  • Author

yes, no Certs in the SMS section in MMC. will check if the client is registered.

  • 2 months later...

I also get this problem, and i dont know why. can anyone help?

Howdy all!

 

I was experiencing this exact issue during testing of our OSD in SCCM 2012. I ran through a premiere support call with MS and quite a bit of troubleshooting before determining the cause.

 

Reference to issue in SCCM 2007

 

 

Essentially, this issue is still present in SCCM 2012. During an OSD process, the SCCM client may get "stuck" in provisioning mode. I found that my OSD would complete and the client would register correctly with one task sequence, but if the application installation order changed, the client would get stuck in provisioning (no self-signed cert). Odd that the application install would affect the "Setup windows and config manager step....

 

As mentioned in the blog article - checking the registry keys will identify if the client is getting stuck or if your issue is possibly caused by another factor. I have included the following at the end of my task sequences to ensure that clients will always register (or at least until the problem is fixed by other means.....*cough* SP1 *cough*)

 

(taken from email exchange MS Engineer)

 

Right after the "Setup Windows and ConfigMgr" step, add two "Run Command Lines" to set the registry values correctly. Here are the two commands to be run:

 

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f
REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f

 

Please let me know if this helps at all....

Cheers AndrewNZ I will give it a shot tommorow. Thanks for the help will post back to see if it works. The wierd thing is that it only happens on 2 units that i have.

  • 1 month later...

Howdy all!

 

I was experiencing this exact issue during testing of our OSD in SCCM 2012. I ran through a premiere support call with MS and quite a bit of troubleshooting before determining the cause.

 

Reference to issue in SCCM 2007

 

 

Essentially, this issue is still present in SCCM 2012. During an OSD process, the SCCM client may get "stuck" in provisioning mode. I found that my OSD would complete and the client would register correctly with one task sequence, but if the application installation order changed, the client would get stuck in provisioning (no self-signed cert). Odd that the application install would affect the "Setup windows and config manager step....

 

As mentioned in the blog article - checking the registry keys will identify if the client is getting stuck or if your issue is possibly caused by another factor. I have included the following at the end of my task sequences to ensure that clients will always register (or at least until the problem is fixed by other means.....*cough* SP1 *cough*)

 

(taken from email exchange MS Engineer)

 

Right after the "Setup Windows and ConfigMgr" step, add two "Run Command Lines" to set the registry values correctly. Here are the two commands to be run:

 

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f
REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f

 

Please let me know if this helps at all....

 

I can confirm that this worked on my Configuration Manager 2012 site!

Thanks a lot!

  • 11 months later...

Great, thanks! This fixed my problem as well.

  • 1 month later...
  • 3 weeks later...

Thanks, i tried this on a client and it worked as well.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.