locked
Re-index the WSUS 3.0 Database and WSUS v10 RRS feed

  • Question

  • Have we verified that the script for re-indexing WSUS 3.0 database works for later versions? I re-installed my WSUS on 2016 server. It says the version is 10.xsomethingx. I would just feel more comfortable knowing whether the old script actually works in some definitive way, maybe updating the download page if it is or reworking the script so we're not spinning our wheels on something that runs but doesn't actually help.

    Thanks!

    • Moved by Bill_Stewart Tuesday, August 8, 2017 4:36 PM Move to more appropriate forum
    Monday, August 7, 2017 8:52 PM

All replies

  • You need to post in WSUS forum.  Your question is a WSUS issue and not a scripting issue.

    WSUS 10 is likely the version of the database and not the WSUS version.  The DB version is dependent on how you installed WSUS.


    \_(ツ)_/

    Monday, August 7, 2017 9:02 PM
  • Hi,

    That script works in 2012R2 .

    It may also works in 2016 WSUS , you can backup the WID first then run that script .

    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.

    • Proposed as answer by Elton_Ji Friday, September 15, 2017 8:43 AM
    Friday, September 15, 2017 8:42 AM
  • The re-indexing script does in fact work on 2016, however it is only 1 step in the Maintenance of WSUS.

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need!

    http://community.spiceworks.com/scripts/show/2998-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

    Monday, September 18, 2017 2:36 AM