Setup Windows and ConfigMgr Step Hangs after v1511 upgrade

[pembertj]

Upgraded to v1511 in late December and recently tried to re-capture a base image (Windows 10). I found that the base image will capture ok (all applications, Software Updates, etc install just fine) and the WIM is captured with no issues. If I take that base image and try to use it during site-wide OSD it will hang for a long time on the Setup Windows and ConfigMgr Step and will then completely freeze on the first application install that we have during the Windows Phase. These task sequences (base and osd) are the exact same ones that we were using before the v1511 upgrade.

 

 

After comparing this log to old "good" logs it seems to me as though the SCCM Client is not being properly prepared on the "Prepare ConfigMgr Client" step at the end of the base image, and then it causes issues during OSD. Let me know any other logs that may be of interest...

Certificate Issuer 1 [CN=aabc Root Certificate; DC=aabc; DC=com]	ccmsetup	1/8/2016 11:56:33 PM	612 (0x0264)
Finding certificate by issuer chain returned error 80092004	ccmsetup	1/8/2016 11:56:33 PM	612 (0x0264)
Completed searching client certificates based on Certificate Issuers	ccmsetup	1/8/2016 11:56:33 PM	612 (0x0264)
Unable to find any Certificate based on Certificate Issuers	ccmsetup	1/8/2016 11:56:33 PM	612 (0x0264)
Raising event:

instance of CCM_ServiceHost_CertRetrieval_Status
{
	DateTime = "20160109055633.941000+000";
	HRESULT = "0x87d00215";
	ProcessID = 624;
	ThreadID = 612;
};
	ccmsetup	1/8/2016 11:56:33 PM	612 (0x0264)
Status Agent hasn't been initialized yet. Attempting to create pending event.	ccmsetup	1/8/2016 11:56:33 PM	612 (0x0264)

ccmsetup.bad.log

[anyweb]

you are not the only one with the issue, see below

 

Technet:

https://social.technet.microsoft.com/Forums/en-US/46052503-6954-4058-b17b-08499e1e0263/client-will-not-initialise?forum=ConfigMgrCBOSD

 

 

If you have the same issue, please “vote” on the appropriate connect site. Thank you!

 

Connect Site:

https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/2153746

[pembertj]

you are not the only one with the issue, see below

 

Technet:

https://social.technet.microsoft.com/Forums/en-US/46052503-6954-4058-b17b-08499e1e0263/client-will-not-initialise?forum=ConfigMgrCBOSD

 

 

If you have the same issue, please “vote” on the appropriate connect site. Thank you!

 

Connect Site:

https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/2153746

 

 

Damn, thanks anyweb - I will try some of those suggestions. I've been digging around on the web all weekend looking for a solution to this one and didn't find that post on technet...

[chappy]

I used the Workaround that the guy on TechNet suggested. I added an additional step (Run Commandline) to run this command C:\Windows\CCM\ccmrepair.exe right after the "Setup Windows and ConfigMgr" step to fix the issue. I added it into my build and capture TS and once the new Image was captured i was able to use it without any issues.

[pembertj]

Adding the steps mentioned (to my base image) mentioned in the technet article worked for me.

after step "Setup Windows and ConfigMgr"

system reboot

put a "Run Command Line" for CCM Service Repair for 1511 Client

Command Line = C:\Windows\CCM\ccmrepair.exe