locked
WSUS console crashing frequenty RRS feed

  • Question

  • Hello Friends,

    we have stand alone WSUS on Windows server 2016 with WID (Windows Internal DB) installation through which we are managing approx 6000 clients on several physical location.

    Issue is that -> wsus console is crashing frequently so should we migrate with full version of SQL server or let it be remain WID.  

    Means how we can prevent wsus console to crash. 

    If someone has any idea please help me.


    Amit Kumar

    Friday, October 13, 2017 10:34 AM

All replies

  • Hello Nedim,

    Its alreday done as you have said very long time ago.

    Do you think it make sense to move the database to a real SQL server to prevent crashes.



    Amit Kumar

    Friday, October 13, 2017 2:38 PM
  • My script fixes these issues. It also allows you to worry about WSUS much less and get back your freedom :)

    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

    Saturday, October 14, 2017 1:56 AM
  • Hi,

    In addition to the suggestion provided by Adam , I'd suggest you try to close WSUS console then move (or copy then remove) the files out in the following path:

    C:\Users\Administrator\AppData\Roaming\Microsoft\MMC

    Then , check if the issue persists .

    If it persists , please check if the updates detection interval is too short for clients within GPO setting "Automatic Updates detection frequency " .

    Any further information please feel free to let us know .

    By the way , If you suspect the issue is related to the overload I/O operation , please check the performance of that disk where holding WID data .

     

    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.


    • Edited by Elton_Ji Monday, October 16, 2017 8:06 AM
    Monday, October 16, 2017 8:06 AM