A customer that recently upgraded to Configuration Manager 1511 CB ran into an issue with deploying newly captured OS images. The task sequence is hanging on client initialization and fails eventually. Images captured before the upgrade could still be deployed without any issues.
This blog post details how we resolved this.
When deploying an OS image captured using a Build and Capture task sequence in Configuration Manager 1511 the client hangs on the client initialization step. In the smsts.log we see an entry Waiting for the CCMExec service to be fully operational . After that there is one more entry referring to loading TSRES.DLL .
This is a known bug in Configuration Manager 1511 which is logged on Connect (ID 2153746).
Feedback on the connect item indicates this will be fixed in an upcoming update to the Configuration Manager current branch. The workaround for now is to not include the client in the image.
Note : in 1602 Technical Preview this issue has already been fixed.
There is another way to work around this if you do not want to pursue the alternative not to include the client in the image.
For this you would need to modify the Build and Capture task sequence to include two additional steps:
- Step 1 : run ccmrepair
- Step 2 : reboot the system
- An example is shown in the screenshot below.
When deploying the newly captured image using the modified task sequence the client will no longer hang on initializing.
Once the next update of Configuraiton Manager CB is implemented in your environment these two steps can be removed again.
Hope it helps!
Time for my weekly wrap-up of stuff to catch up with:
- Very helpful blog post from the Microsoft PFE team on how to use the same external ethernet adapter for deploying multiple devices with ConfigMgr OSD.
- Garth at Enhansoft explains in detail how to enable workstation logon audit policy in order to collect top console user details with Configuration Manager.
- On the System Center ConfigMgr team blog you can learn how to collect IMEI from devices enrolled in Windows Intune with System Center 2012 R2 Configuration Manager. IMEI is short for International Mobile Equipment Identity, which is a unique identifier for mobile devices.
- Released: KB2905359 – Installation of the Configuration Manager client agent fails with error code 80041002.
See you next week!
Last week I was on vacation so I skipped my weekly review. I am not back in full force yet but did have some time to check the radar and list up some interesting blips. Here they are for this week:
- Beginning of the week Microsoft announced the Unified Technology Event for Enterprises, or MUTEE. After writing off MMS last year it seems the other large conference TechEd will cease to exist in its current form as well. MUTEE will be the result of the merger of all these events. As a result of this there will be MUTEE, WPC and Build left on the conference agenda of Microsoft.
- The ConfigMgr blog has an interesting article on how to configure a reporting services point for HTTPS.
- Need some advice on Configuration Manager 2012 SQL Maintenance Plans, Index Optimization or other recommendations? Look no further.
- Interesting blog by Johan on how to list Applications configured for Task Sequence Deployments.
- OSD : how to sync the BIOS date in WinPE to avoid PXE Boot failures.
- Released: KB2978017 :
Cumulative Update 5 for System Center 2012 Configuration Manager Service Pack 1
Until next week!