locked
Huge Performance Issues RRS feed

  • Question

  • Hi,

    I've been using WSUS in my environment for a few months now, with approx. 600 clients. However, I have only had about 5 updates approved.

    Today we decided to roll out all applicable updates to approx. 8 test machines, with a view to deploying out all applicable updates to the rest of our estate in a weeks time.

    However, I have approved all of the applicable updates (approx. 20,000) and this seems to have broken WSUS. The console keeps crashing on me, CPU is at 100% etc.

    I think a better way may be to approve a smaller amount of updates at a time, but as the console keeps kicking me out, I don't know how to do this. After I reboot the server, the CPU goes down for a period of time, but then spikes up again.

    Is there a way for me to force WSUS to stop what it's doing, so I can go in and fix my mistake?

    Thanks
    Monday, July 10, 2017 8:30 PM

All replies

  • Hi Sir,

    >>However, I have approved all of the applicable updates (approx. 20,000) 

    AFAIK , it is not recommended to approve such amount of updates .

    IMHO , re-install WSUS server is a short-cut for you .

     

    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.

    Wednesday, July 12, 2017 9:34 AM
  • My script will probably fix this issue as it cleans out the clutter, and all superseded updates. It will leave you with a nice clean system.

    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. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. 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. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, 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

    • Proposed as answer by Elton_Ji Sunday, August 13, 2017 3:05 PM
    Thursday, July 13, 2017 4:02 AM