INTRODUCTION

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:

Regedit Provisioing mode SCCM 2012 client

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

SOLUTION

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:

Force SCCM 2012 client out of Provisioning Mode Task Sequence

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.