Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

← Ideas

Improve SCCM's built in WSUS cleanup and maintenance task

Preview SCCM versions have a basic WSUS cleanup and maintenance task. It should be evolved and expanded to include SQL index optimization, IIS configuration optimization, and deletes of declined updates.

45 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Ben Whitmore commented  ·   ·  Flag as inappropriate

    There has been a lot of great work around WSUS maintenance in 1906. I would love to see a meta data clean-up option too. Let me pose a scenario.

    You choose to import 3rd party updates via MEMCM Software Updates. Importing the Dell catalog will add around 4500 objects into your metadata. Despite the new client update agents not having memory leaks like back in the 2008 x86 days, 4500 objects is a good increase in the metadata the clients have to evaluate.

    If a customer then chooses to remove the 3rd party catalog, the updates are expired and deleted on the 7 day WSUS maintenance cycle in MEMCM. This cycle does not delete the updates/categories from the metadata so the clients are still having to process it when they perform a scan cycle.

    Having the option to remove metadata of retired updates that are expired and deleted will only improve update scan efficiency.

  • Jay Connor commented  ·   ·  Flag as inappropriate

    Please fix or add the option to select the port of the WSUS DB instance.

    I don't understand the alias workaround completely and whether it would work when the SCCM instance has the default port

  • Dorian Stanley commented  ·   ·  Flag as inappropriate

    Many of us have been waiting patiently for this. I would LOVE to see my WSUS server become more self-sufficient and less hands-on.

  • Anonymous commented  ·   ·  Flag as inappropriate

    When we will get the cleanup option for entire hierarchy? Now seems only possible in CAS, as per Wsus cleanup procedure decline and cleanup must follow a pattern, if this option is only on the CAS how is this going to work on the scenario of TOP level Wsus on a remote box. Need more changes to be actually usable in production environment.

  • Phillip commented  ·   ·  Flag as inappropriate

    Will this be for the full solution...i.e. to all secondaries as well? Or other remote SUP servers further down the line?

Ideas: Software Updates

Categories

Feedback and Knowledge Base

(thinking…)