Jump to content


jesterrace

damaged client after setup? no self singed cert

Recommended Posts

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....

  • Like 1

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

Hi Guys! I'm having same problem after adding a bunch of apps/agents to the TS. Can you tell me where in the TS you add the reg key command lines, after the initial setup windows and config manager or just as the final step or with a restart reg key reg key restart to end the TS or such?

Thank you!!!

x

Share this post


Link to post
Share on other sites

danubex

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

 

Share this post


Link to post
Share on other sites

I found the problem and it had nothing to do with registry settings or similar..

 

I had, at the end of my TS, inserted a reboot...

When you add a reboot to your TS it automatically sets an option to boot into the Bootimage associated with the TS.. which means instead of booting into the installed OS it booted into the bootimage.. and thus set registry keys to reflect this.. being in provisioning mode..

Share this post


Link to post
Share on other sites

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...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...