SCCM Task Sequence - Software Updates Step 0x80244010 error

[pembertj]

Running into this error:

https://blogs.technet.microsoft.com/sus/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010/

or

https://social.technet.microsoft.com/Forums/systemcenter/en-US/7882521e-8a1d-40a5-95b9-d3105965cbf6/0x80244010-roundtrip-error?forum=configmgrgeneral

This only has seemed to start happening after we moved to SCCM v1511. Software update groups did not change when we updated - a machine that is imaging today should see the same # of updates that it did before the upgrade. Suggestions of adding more "software update steps" to the task sequence does not seem to help (as people have posted as a solution in various forums). I have added 10x Software update steps and still see the same behavior...

Just looking for any solutions. We keep our base up to date and these updates are deployed to the machines after the TS finishes as well, but it would be nice to figure out why this just started happening...

[blindpepper]

pembertj,

 

did you get this solved, having the same problem after upgrade to 1511 and 1602.

 

Mario

[YPCC]

As well as the multiple "software update" steps, have you added steps to actually force a scan for new updates?

 

Long story short, sccm scans for new updates and caches a list of required updates, those updates are installed, when you check for updates again it uses the cache to determine if anymore are required.

 

What you need to do is flush out the cache and force sscm to rescan for updates again. This is done by adding the WMIC command that triggers a update scan.

 

http://www.toolzz.com/?p=1059

 

Add this a few times, thatll ensure practically all updates get installed. Flakey but works! Microsoft do need to up their game on this feature. Really lacking.

[YPCC]

The other thing i have thought of but not tested is the deletion of c:\windows\softwaredistribution once the first batch have of updates have installed.

 

Not a great way, but anything to force the task sequence to forcibly check for updates rather than relying on cached info.

[pembertj]

Software update point and some other components were broken, after a complete uninstall of all related components (remove sup, wsus, wsus database, delete ADRs, Software update groups, software update packages, etc) and a re-install everything is working fine.