Issue: Create and deploy WES7 images with ConfigMgr 1511

In a customer environment, Windows Embedded Standard (WES) 7 is used in combination with ConfigMgr. With ConfigMgr 2012 R2 this wasn't an issue it all. After the ConfigMgr 1511 upgrade however, deployment of the WES 7 image stops at initializing the ConfigMgr client. Situation is, a ConfigMgr client is part of the image, and it can't be upgraded during deployment. When looking in task manager no CCMsetup.exe proces is active. When looking in Services, no SMS Agent Host service is running (because it's disabled). When looking in smsts.log the following line is displayed: Failed to register task sequence with the newly installed client.

End of story! No applications were installed and deployment is hanging on this part for multiple hours! That sucks bigtime..

Errors seen in ccmsetup.log
ITaskService: GetFolder failed with 0x80070003
Failed to delete task Configuration Manager Client Retry Task. Error 0x80070003
Failed to delete task Configuration Manager Client Upgrade Task. Error 0x80070003
Failed to get client version for sending state messages. Error 0x8004100e
Failed to send status 100. Error (87D00215)
Failed to connect to policy namespace. Error 0x8004100e
Failed to revoke client upgrade local policy. Error 0x8004100e
Failed to get client version for sending state messages. Error 0x8004100e
Failed to send status 100. Error (87D00215)
Error while calculating path to state file.
Loading the client state failed.
CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint.

Errors seen in smsts.log
Unable to read SMS client cert from environment. Not restoring SMS client cert.
CoCreateInstance failed 0x80070422
Failed to register task sequence with the newly installed client. (0x4B2FD068). Continuing..
Failed to show task sequence action progress dialog. Error code 0x800706be

Errors seen in LocationServices.log
Unexpected row count (0) retrieved from AD.
Failed to retrieve MP certificate encryption info from AD.

I did create another image, using CCMclean.exe on the existing installed client. I installed the ConfigMgr 1511 client after that with good results. Did a capture with ConfigMgr too without any problems. During deployment of this image the same behaviour was seen, no CCMsetup.exe running, no enabled SMS Agent Host service and no task sequence progress. For it seems ConfigMgr 1511 and WES 7 aren't good friends here? When logon on the client (after breaking deployment progress) the ConfigMgr client is seems to be active, but without a site code. No good result if you ask me..

After that I installed and configured MDT 2013 Update 2 (done within 30 minutes) and created an image with that. Good point with MDT is that no ConfigMgr client needs to be installed, so you have a really clean image. The capture was done at first try without any problems. I decided to use ConfigMgr for deployment again of multiple PXE servers otherwise. Trick is with ConfigMgr 1511 and the WES7 image created with MDT 2013U2 no issue is seen during initializing the ConfigMgr client. Hurray! So next time be wise, and create your image with MDT. ConfigMgr will do the job afterwards :-)

Tweet

Nicho Las

Blog Download Apk.

Subscribe to receive free email updates: