OSD - client stuck in ProvisioningMode - help

Question

Guys,
CM newbie here.. I am attempting a very simple OSD via TS, and like many of the post related to (provisioing mode = true) I am stuck.
I read atleast 40 post on various sites that mentions this issue, with the work around being to modify registry keys after the task "Setup Windows and ConfigMgr"  (as mentioned
Here and in many places on this forum). I understand that this is a "work-around" and doesnt address the issue, but this never works for me as the machine reboot directly after "Setup Windows
and ConfigMgr" (and reg keys never get applies and neither does anything after this step). 
I've also read the multiple reboots after Software Update can cause this, which i do not have. Also, I dont have a single reboot task in the TS and I still get the same results. My Setup is CM2012r2-cu1 and i just added the CU1 patch to the "Setup Windows
and ConfigMgr" task using steps similar to this.
I though the issue was solved once I added the patch as I could have swore my first deployment works successfully (provisioning mode=false), but I have re-ran the same TS several times and Im still stuck in provisioning mode.
During the installation of "Setup Windows and ConfigMgr" when booted to the OS, if I bring up the console and change these reg values before the machine reboots (about a 10 second window), the TS run as expect and my packages in the TS are deployed.
I have attached a screenshot of the the most basic TS that I have and the issue of being stuck in provisioning mode still persist. I removed the "Run Commandline" task of modifing the registry keys after the "Setup Windows and ConfigMgr"
task as it wasn't setting the value anyways.  Any idea where am I going wrong? 

Answer 1

Hi Torsten,
Thanks for the reply.  The client appears to install successfully. Below are the
all of the fails that are in the ccmsetup.log file, as well as the success return code at the end.  Also, the machine is in a Workgroup at the time of Client installation.
Failers:
1) Unexpected row count (0) retrieved from AD.
ccmsetup 9/9/2014 9:25:56 PM
1892 (0x0764)
2) Failed to get site version from AD with error 0x80004005
ccmsetup 9/9/2014 9:25:56 PM
1892 (0x0764)
3) File 'C:\WINDOWS\system32\msrdc.dll' does not exist. Discovery failed.
ccmsetup 9/9/2014 9:25:57 PM
1892 (0x0764)
4) File 'C:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed.
ccmsetup 9/9/2014 9:25:57 PM
1892 (0x0764)
5) Failed to load mdmregistration.dll with error 0x8007007e
ccmsetup 9/9/2014 9:25:58 PM
1892 (0x0764)
6) Failed to load mdmregistration.dll. Continue deployment.
ccmsetup 9/9/2014 9:25:58 PM
1892 (0x0764)
7) MSI: Action 21:26:31: SmsGenerateFailureMIF. ccmsetup
9/9/2014 9:26:31 PM 1892 (0x0764)
8) MSI: Action 21:26:34: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint.
ccmsetup 9/9/2014 9:26:34 PM
1892 (0x0764)
9) MSI: Action 21:26:36: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents.
ccmsetup 9/9/2014 9:26:36 PM
1892 (0x0764)
10) MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent.
ccmsetup 9/9/2014 9:26:37 PM
1892 (0x0764)
11) MSI: Action 21:26:57: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint.
ccmsetup 9/9/2014 9:26:57 PM
1892 (0x0764)
Success
1) File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation succeeded.
ccmsetup 9/9/2014 9:27:17 PM
1892 (0x0764)
2) CcmSetup is exiting with return code 0 ccmsetup
9/9/2014 9:27:17 PM 1892 (0x0764)