16 WSUS clients fail with WARNING: SyncServerUpdatesInternal failed: 0x80244010″.

First remove Superseded updates through the WSUS Cleanup wizard.

Image:Example1.jpg

There is no feature in the product to automatically decline superseded updates on approval of the newer update, and in fact, you really do not want that feature. The “Best Practice” in dealing with this situation is:

  • 1. Approve the newer update.
  • 2. Verify that all systems have installed the newer update.
  • 3. Verify that all systems now report the superseded update as Not Applicable.
  • 4. THEN it is safe to decline the superseded update.

*To SEARCH for superseded updates, you need only enable the Superseded flag column in the All Updates view, and sort on that column. There will be four groups:

  • 1. Updates which have never been superseded (blank icon).
  • 2. Updates which have been superseded, but have never superseded another update (icon with blue square at bottom).
  • 3. Updates which have been superseded and have superseded another update (icon with blue square in middle).
  • 4. Updates which have superseded another update (icon with blue square at top).
  • There’s no way to filter based on the approval status of the updates in group, but if you’ve verified that all necessary/applicable updates in group are approved and installed, then you’d be free to decline groups.

Leave a comment