The other day I had an issue at a customer, where the installations of new computers ran without any errors, but once logging in, it was obvious that everything was not right.
The reason why we noticed that something was wrong, was that all new computers that had been installed, were missing the SCEP client. Looking at the server side, everything looked fine, so it had to be something on the client side.
Issues that were present:
1. SCEP was not being installed
2. Fewer Actions than usually for the Configuration Manager client
3. There was no Client Certificate for the client
I’ve seen this before with SCCM 2007, and then the problem was the client was still in Provisioning Mode.
Provisioning Mode is a mode that the client is in during OSD, which blocks policies from being applied during the installation. Once the task sequence is complete, the client should have been brought out of this mode, and get its policies correctly.One easy way to check this is opening the Registry Editor and checking this value:
Sure enough, the client was still in Provisioning Mode.
WHAT IS PROVISIONING MODE?
Provisioning mode is used by SCCM to prevent Group Policy objects to be applied during operating system deployment.
Gary Town has created an in-depth blog post describing SCCM Provisioning Mode.
WHY WAS CLIENT STILL IN PROVISIONING MODE?
When the deployment of a Task Sequence in SCCM is successful, the client should automatically be brought out of Provisioning Mode. Sometimes a step in the Task Sequence might cause this to fail
Before reading the below solution, note that the client is most likely still in Provisioning Mode for a reason. You should start by investigating why this is.
The solution is to change the value in the registry and then reinstall the client, but since this happens on almost all new installations, this would be some seriously tedious work.
The easiest solution is to add these two registry changes as seperate command line steps in your Task Sequence after the “Setup Windows and ConfigMgr” step:
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
Start a new installation and the client should automatically be brought out of Provisioning Mode.
Nickolaj Andersen has also written a good article how to accomplish this using Powershell.
- How To Install .NET Framework 3.5 on Windows Server 2012, Windows Server 2016 and Windows 10 968,511 views
- Issue with mounting new ISO files from TechNet in Windows 8 and Windows 8.1 Preview 63,986 views
- Solve SCCM Error “sending with winhttp failed; 80072ee7” in Windows PE 31,936 views
- Powershell: Script to set Outlook 2010/2013 signature using information populated from Active Directory 32,304 views
- How To Enable PXE in Hyper-V for Legacy Boot 109,458 views
- How to force specific sites to always run in Compatibility View using Group Policy 145,168 views
- How to change between a Full Installation (GUI) and Server Core in Windows Server 2012 64,346 views
- How To Solve WDS Issue with DHCP Port Conflict 12,350 views
- Hyper-V: Issue when starting virtual machine from downloaded ISO file 7,554 views
- How To Check Bitlocker Status using the Command Line 120,122 views
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell
What are Intel Modern Drivers for Graphics? https://t.co/h2d2GJOyJY #ConfigMgr
New blog post: How to deploy HP BIOS settings using SCCM and Powershell: https://t.co/JVKHBN86pN #sccm #configmgr #PowerShell
@miketerrill On topic of this, this might help with the initial clearing! https://t.co/2NnFlDU6lm @SCConfigMgr @modaly_it thank you for sharing
Friday #WaaS Tip: Record full Build Number Key during IPU. Helps support teams know which patch level was installed at time of upgrade to help correlate if any upgrade issues correspond to a specific patch level of the upgrade build. Blog Post Update coming soon (SetOSDinfo)3