#Remove open software updater update

In addition to declining expired updates in WSUS, Configuration Manager can add non-clustered indexes to the WSUS databases and remove obsolete updates from the WSUS databases.

#Remove open software updater update

You have additional WSUS maintenance tasks that Configuration Manager can run to maintain healthy software update points. The following WSUS Server Cleanup Wizard options aren't run on the CAS, primary, and secondary sites:

The updates are declined in WSUS for CAS, primary, and secondary sites.

The Expired updates option for WSUS servers on CAS, primary, and secondary sites.

The WSUS cleanup option occurs after every sync and does the following cleanup items: Starting version 1810, you can specify supersedence rules for feature updates separately from non-feature updates in the Software Update Point component properties. WSUS cleanup behavior starting in version 1810 The following WSUS Server Cleanup Wizard options aren't run on the CAS and primary sites:ДЇor more information and instructions, see The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance blog post.

For example, if you use 2 months for this setting, then updates that have been superseded will be declined in WSUS and expired in Configuration Manager when the superceding update is 2 months old.ДЄll WSUS maintenance needs to be run manually on secondary site WSUS databases. The 'Months to wait before a superseded update is expired' is based on the creation date of the superseding update.

A cleanup for software update configuration items in the Configuration Manager database occurs every seven days and removes unneeded updates from the console.

The updates are declined in WSUS for CAS and primary sites but not for secondary sites.

The update configuration items meeting the supersedence behavior criteria are expired in the Configuration Manager console.

The list is based on the supersedence behavior in the Software Update Point component properties.

Configuration Manager builds a list of superseded updates from its database.

WSUS servers for secondary sites don't run the WSUS cleanup for expired updates.

The Expired updates option for WSUS servers on CAS and primary sites.

Starting version 1806, the WSUS cleanup option occurs after every sync and does the following cleanup items: WSUS cleanup behavior starting in version 1806 For more information and instructions, see The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance blog post.

This cleanup won't remove expired updates from the Configuration Manager console if they're currently deployed.ДЄdditional maintenance is still needed on the top-level WSUS database and all other WSUS databases in the environment.

The Expired updates option from the WSUS cleanup wizard on the top-level site's WSUS server only.ДЄ cleanup for software update configuration items in the Configuration Manager database occurs every seven days and removes unneeded updates from the console. WSUS cleanup behavior in version 1802 and earlierД«efore Configuration Manager version 1806, the WSUS cleanup option runs the following item: In version 1806, the option is renamed to Run WSUS cleanup after synchronization.Д¬lick OK (Click Close if you're running version 1806). Modify the behavior if needed.Д¬lick the Supersedence Rules tab, select Run WSUS cleanup wizard. Select the site at the top of your Configuration Manager hierarchy.Д¬lick Configure Site Components in the Settings group, and then click Software Update Point to open Software Update Point Component Properties. In the Configuration Manager console, navigate to Administration > Overview > Site Configuration > Sites. Schedule the WSUS cleanup job by running the following steps: When you first select to run the WSUS cleanup task, it will run after the next software updates synchronization. You can schedule and run WSUS cleanup tasks from the Configuration Manager console from the Software Update Point Component properties. Applies to: Configuration Manager (current branch)