Windows 10 1607 clients not updating via SCCM?

[altecsole]

We use WSUS for updates via SCCM and this works fine for Windows 7 and Server 2008/2012 clients. However, we seem to have a problem with Windows 10 1607.

 

The Deployment Status in SCCM show Uknown - Client Check passed/Active.

 

On the Windows 10 1607 clients the WUAHandler.log shows the following errors:

 

OnSearchComplete - Failed to end search job. Error = 0x80244007.

Scan failed with error = 0x80244007.

 

The WindowsUpdate.log on the same clients shows lots of errors for WebServices WS error:

 

2017/02/28 15:32:19.3156427 1340 13284 WebServices WS error: The character value 11 (0xB) is not valid.

2017/02/28 15:32:19.3156453 1340 13284 WebServices WS error: The body of the received message contained a fault.

2017/02/28 15:32:19.3156467 1340 13284 WebServices WS error: The body of the received message contained a fault.

2017/02/28 15:32:19.3156484 1340 13284 WebServices WS error: The body of the received message contained a fault.

2017/02/28 15:32:19.3156504 1340 13284 WebServices WS error: Serialization failure occurred when writing an element with WS_WRITE_OPTION '1', name 'RegisterComputer' and namespace 'http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService'.

2017/02/28 15:32:19.3156524 1340 13284 WebServices WS error: Serialization failure occurred when writing a field with WS_TYPE '26 (0x1A)', WS_FIELD_MAPPING '2', name 'computerInfo' and namespace 'http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService'.

2017/02/28 15:32:19.3156544 1340 13284 WebServices WS error: Serialization failure occurred when writing a field with WS_TYPE '17 (0x11)', WS_FIELD_MAPPING '2', name 'DeviceType' and namespace 'http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService'.

I've downloaded and run the Windows Update Troubleshooter (latestwu.diagcab) and this seemed to detect and fix some problems, but the errors are still there.

Has anybody any ideas how to fix this? I can manually update clients via Windows Updates, but that's obviously a non-starter for us.

Many thanks for taking the time to read and reply.

Jim

[Ariendg]

Looks like this can be the same problem I experienced with WSUS.

 

https://social.technet.microsoft.com/Forums/en-US/9941646e-648d-49e2-97a4-088e5cc0d917/windows-10-1607-stuck-when-downloading-updates-from-wsus-in-mdt-windows-update-task-sequence?forum=win10itprosetup

 

Don't install (original) build 1607 without CU/Rollups because there are quite some deployment bugs under the hood..

Johan also has blog post about this: http://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2

I haven't tried the new v1607 media from VLSC, because my W10 deployment was breaking too much already. It seems the best option IMO.

 

I believe first patch fixed it for me was KB3194798. You can keep track on the updates on https://support.microsoft.com/en-us/help/4000825/windows-10-and-windows-server-2016-update-history and always take the latest and greatest.

Good luck.

[altecsole]

Looks like this can be the same problem I experienced with WSUS.

 

https://social.technet.microsoft.com/Forums/en-US/9941646e-648d-49e2-97a4-088e5cc0d917/windows-10-1607-stuck-when-downloading-updates-from-wsus-in-mdt-windows-update-task-sequence?forum=win10itprosetup

 

Don't install (original) build 1607 without CU/Rollups because there are quite some deployment bugs under the hood..

Johan also has blog post about this: http://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2

I haven't tried the new v1607 media from VLSC, because my W10 deployment was breaking too much already. It seems the best option IMO.

 

I believe first patch fixed it for me was KB3194798. You can keep track on the updates on https://support.microsoft.com/en-us/help/4000825/windows-10-and-windows-server-2016-update-history and always take the latest and greatest.

Good luck

 

 

Many thanks taking the time to reply, it's much appreciated. I'll go through those posts and see if I can make some progress. Cheers.

[altecsole]

Looks like this can be the same problem I experienced with WSUS.

 

 

Nothing I've read seems to offer a fix for my issue. I've tried a few things, like adding .esd and .msu as mime types on IIS, but that's not made any difference. Also, some of the updates that people have mentioned must have been superseded because they won't install on my clients.

I've posted on the Microsoft WSUS forum (https://social.technet.microsoft.com/Forums/windowsserver/en-US/33237c84-bacf-4d80-96a0-1dd440357870/windows-10-1607-client-update-error-0x80244007-showing-webservices-ws-errors-in-windowsupdatelog?forum=winserverwsus ), so hopefully, that may offer some suggestions.

[Ariendg]

If updates are working for Windows 7 I would not advise changing settings on the back-end. The base update mechanism is not changed that much from w7 to w10.

Also try to find the latest Windows Update Agent download.