Document
ConfigMgr Task Sequence failing on device rebuilds

ConfigMgr Task Sequence failing on device rebuilds

I is looking ’ve been look into an issue where device were fail on a rebuild . The error greet me on screen during OSD was 0x800705b4 . Looking at th

Related articles

7 Best Walking Shoes in 2024 (For All Types of Walkers) 精品分享:全新数睿通数据中台–基于 Flink+ TiDB 构建实时数仓 Urban fishing: Stocked ponds draw city dwellers, newbies How To Install Call Of Duty VPN & GeoFence From SBMMOFF | Warzone VPN Best VPN service 2024: 9 options our experts recommend

I is looking ’ve been look into an issue where device were fail on a rebuild . The error greet me on screen during OSD was 0x800705b4 .

Looking at the smsts.log file, the TS was failing when applying the Install Software Updates step and the 0x800705b4 error relates to that step timing out.

The strange thing was that the software updates were successfully applying to new devices but always failing on rebuilds. So it was time to dig deeper.

The locationservices.log sprung the first clue. The WSUS details had not populated, nothing had been set on the device. The only WSUS entries were as follows:

Attempting to persist WSUS location request for ContentID='{3767B81D-00B2-4D68-A3F4-0CD9C0FB4B34}’ and ContentVersion=’45’ LocationServices 30/11/2018 13:53:52 5660 (0x161C)
Attempting to create WSUS Location Request for ContentID='{3767B81D-00B2-4D68-A3F4-0CD9C0FB4B34}’ and Version=’45’ LocationServices 30/11/2018 13:53:52 5660 (0x161C)
Successfully created Location Request LocationServices 30/11/2018 13:53:52 5660 (0x161C)
persist WSUS location request locationservice 30/11/2018 13:53:52 5660 ( 0x161C )
attempt to send WSUS Location request for ContentID='{3767B81D-00B2 – 4D68 – A3F4 – 0CD9C0FB4B34 } ’ locationservice 30/11/2018 13:53:52 5660 ( 0x161C )

Also a repeated failure in the log.

Failed to send management point list Location Request Message to <management point server>

OK so some real issues here but again why only on a rebuild of a device?

The ccmmessaging.log assisted me further with my troubleshooting. The ccmmessaging log is your go to log when investigating communication between devices and management points. The log was filled with a nice sea of yellow and red with the repeated error.

Request to http://<management point server>/ccm_system/request cannot be fulfilled since use of metered network is not allowed. CcmMessaging 30/11/2018 14:04:00 6844 (0x1ABC)
Post to http://<management point server>/ccm_system/request failed with 0x87d00231. CcmMessaging 30/11/2018 14:04:00 6844 (0x1ABC)

So the rebuild thinks it is on a metered network, why?

A quick ipconfig check showed that a Mobile Broadband adapter was present in the device and it had an IP address and was connected. After pulling the SIM card from the device, the build was able to run and apply software updates.  Another option would have been to set the Default Client Setting to Allow client communications on metered Internet connections and then adjust this setting post build to the required level with a custom client setting.