locked
KB3159706 Woes - Some clients failing some are not RRS feed

  • Question

  • Installed 3159706 followed the postinstall /servicing steps. Already had the .NET activation installed. Some users are able to scan for updates from WSUS, some are not (about a 50/50 split). Using HTTP, not HTTPS. Clients that fail get error 80244008.

    1. I've tried toggling upgrades off and on (with syncing inbetween) 
    2. Browsing http://hostname:8530/ClientWebService/Client.asmx?singleWsdl works
    3. I've tried reinstalling WSUS (remove role, reboot, install role)
    4. I've tried uninstalltion of WSUS, deleted database, started over. (I have SCCM so this wasn't an incredibly awful choice)
    5. I've tried uninstalling 3159706, then everything was broken and had to drop the database again and re-uninstall the role...again. This works in getting WSUS workable again, but we'll need the Win10 upgrades feature over this summer.

    Any help?


    Jonathan W Topping

    Monday, July 4, 2016 12:19 PM

Answers

  • This helped. I was sure this was a WSUS issue, but it turns out WSUS caused a client issue throughout my environment. I had to perform the Windows Update reset steps (https://support.microsoft.com/en-us/kb/971058) on all affected machines to get them to sync to WSUS again. So far 3/3 of these have worked.

    Any idea if there is a easier method for this?


    Jonathan W Topping

    Thursday, July 7, 2016 6:02 PM

All replies

  • Hi zztopping,

    Error 8024408 is caused by a parsing fault in the SOAP packet generated by the client.

    And according to your description, half of the clients can update from WSUS after installing KB3159706, then have you troubleshot the clients that having problems to update from WSUS with KB3159706 before you uninstall it.

    Could you provide some information about what steps you have done to troubleshoot the original one before you reinstall and rebuilt WSUS?

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, July 5, 2016 7:59 AM
  • This helped. I was sure this was a WSUS issue, but it turns out WSUS caused a client issue throughout my environment. I had to perform the Windows Update reset steps (https://support.microsoft.com/en-us/kb/971058) on all affected machines to get them to sync to WSUS again. So far 3/3 of these have worked.

    Any idea if there is a easier method for this?


    Jonathan W Topping

    Thursday, July 7, 2016 6:02 PM
  • Hi zztopping,

    >Any idea if there is a easier method for this?

    Maybe GPO or script could help.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, July 11, 2016 8:02 AM