locked
Quick Advice needed RRS feed

  • Question

  • Hi Guys,

    I am getting a little anxious here with our WSUS downstream Replica servers.

    Today I looked at the progress of our downloads and for some reason it is showing that there are 134,070.82 of 155,184.897MB downloaded so far. The updates are showing as 17199 but on the Upstream server I am only seeing 5114.

    Unfortunately I am unable to delete the updates that are showing as Not Approved because the Approve and Decline options are greyed out. I don't even know how they actually got to the downstream server as Not Approved as the Upstream server does not show as many Not approved as the downstream servers? This situation is really bizarre and I would like to sort it out soonest.

    Can anyone offer any advice of how I am able to delete this unapproved updates that appear on the downstream servers. Or offer any advice on any other issues that I am getting.

    Your help would be greatly appreciated in this hour of need :).

    Regards.

    Wednesday, January 10, 2018 9:27 AM

All replies

  • Hi,

    >>Today I looked at the progress of our downloads and for some reason it is showing that there are 134,070.82 of 155,184.897MB downloaded so far. The updates are showing as 17199 but on the Upstream server I am only seeing 5114.

    It seems that the downstream server is not in "replica" mode .

    If you are going to get a same downstream server as the upstream server , it is strongly recommended to use replica mode .

    Other wise (autonomous mode) , if you download update which doesn't exist in upstream server , the update will be first downloaded in upstream server .

    So , I'd suggest you rebuild downstream server .

    In addition , the upstream serve may downloaded these unwanted updates ,please follow the following article to do re-sync content for upstream WSUS server :

    https://blogs.technet.microsoft.com/gborger/2009/02/27/what-to-do-when-your-wsuscontent-folder-grows-too-large/

    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 Monday, January 15, 2018 1:52 AM
    Thursday, January 11, 2018 9:56 AM
  • Elton is right about the replica mode/autonomous mode - Replica's are far better and easier to manage as you only have to approve the update in 1 place, and everything across the network stays consistent.

    Alternatively use WAM to maintain WSUS Automatically.

    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

    • Proposed as answer by Elton_Ji Monday, January 15, 2018 1:52 AM
    Thursday, January 11, 2018 3:21 PM