locked
WSUS freed 130GB of space RRS feed

  • Question

  • Hi,

    Today I was doing a clean up on WSUS using the wizard (as I always do) and today it freed 130 GB.

    I have never seen it clean so much space. There was some changes on a Microsoft product or something?

    My WSUS is on version 3.0 on W2K8 SP2.

    Wednesday, January 24, 2018 4:16 PM

Answers

  • There was some changes on a Microsoft product or something?


    On Januari 22/23 (depending on time zone) Microsoft expired literally thousands of Office updates. Just check the synchronization results from those dates.

    Rolf Lidvall, Swedish Radio (Ltd)

    • Proposed as answer by Rolf Lidvall Thursday, January 25, 2018 12:46 PM
    • Marked as answer by Vandrey Trindade Thursday, January 25, 2018 12:46 PM
    Thursday, January 25, 2018 12:33 PM

All replies

  • I'm pretty sure you can free even more if you WAM it!

    Please have a look at the WSUS Automated Maintenance (WAM) system. It is an automated maintenance system for WSUS, the last system you'll ever need to maintain WSUS!

    https://community.spiceworks.com/scripts/show/2998-wsus-automated-maintenance-formerly-adamj-clean-wsus

    What it does:

    1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster.
    2. Remove all Drivers from the WSUS Database (Default; Optional).
    3. Shrink your WSUSContent folder's size by declining multiple types of updates including by default any superseded updates, preview updates, expired updates, Itanium updates, and beta updates. Optional extras: Language Packs, IE7, IE8, IE9, IE10, Embedded, NonEnglishUpdates, ComputerUpdates32bit, WinXP.
    4. Remove declined updates from the WSUS Database.
    5. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    6. Compress Update Revisions.
    7. Remove Obsolete Updates.
    8. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    9. Application Pool Memory Configuration to display the current private memory limit and easily set it to any configurable amount including 0 for unlimited. This is a manual execution only.
    10. Checks to see if you have a dirty database, and if you do, fixes it. This is primarily for Server 2012 WSUS, and is a manual execution only.
    11. Run the Recommended SQL database Maintenance script on the actual SQL database.
    12. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use so don't over think it. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment (email settings only if you are accepting all the defaults), simply run:

    .\Clean-WSUS.ps1 -FirstRun

    If you wish to view or increase the Application Pool Memory Configuration, or run the Dirty Database Check, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.


    Adam Marshall, MCSE: Security
    http://www.adamj.org
    Microsoft MVP - Windows and Devices for IT

    Thursday, January 25, 2018 12:35 AM
  • Hi,

    Today I was doing a clean up on WSUS using the wizard (as I always do) and today it freed 130 GB.

    I have never seen it clean so much space. There was some changes on a Microsoft product or something?

    My WSUS is on version 3.0 on W2K8 SP2.

    Hi,

    AFAIK , there is no change on WSUS side .

    It would be a normal behavior .

    That might be caused by :

    1.downstream server under that 2008R2 was removed recently

    2. recently declined lots of updates .

     

     

    Best Regards,

    Elton


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

    Thursday, January 25, 2018 9:33 AM
  • There was some changes on a Microsoft product or something?


    On Januari 22/23 (depending on time zone) Microsoft expired literally thousands of Office updates. Just check the synchronization results from those dates.

    Rolf Lidvall, Swedish Radio (Ltd)

    • Proposed as answer by Rolf Lidvall Thursday, January 25, 2018 12:46 PM
    • Marked as answer by Vandrey Trindade Thursday, January 25, 2018 12:46 PM
    Thursday, January 25, 2018 12:33 PM
  • Rold Lidvall,

    Thanks!

    Thursday, January 25, 2018 12:44 PM
  • Elton_Ji,

    Well I didn't do any of those two actions.

    But ok, no problem! I was just trying to figure it out.

    Thursday, January 25, 2018 12:45 PM
  • Rold Lidvall,

    Thanks!

    No problem, checking the "Synchronizations" view once a day is a good measure if you're a patch manager.

    Rolf Lidvall, Swedish Radio (Ltd)

    Thursday, January 25, 2018 12:51 PM