locked
Server 2016 - WSUS initial setup hangs at Connecting to Microsoft RRS feed

  • Question

  • Howdy,

    I have a brand new Server 2016 machine that I installed WSUS on.  This is going to be the upstream server so I told it to talk to Microsoft to get information.

    I got as far as the Download update information from Microsoft Update screen and clicked Start Connecting.  It's now been sitting here for over an hour with a green bar going across the screen but I can't tell if it's doing anything or not.

    I just tried clicking Stop Connecting and then Start Connecting again but it's still just stuck showing the bar going across.

    Is there some way to tell what (if anything) it's doing or if it's having trouble connecting or anything like that?

    Thanks.

    Wednesday, December 6, 2017 3:47 PM

Answers

  • Well, I decided to reboot the server and give it another try and that seemed to do he trick.  It finally got done with the Connection piece.

    Thanks,

    • Marked as answer by Kelemvor33 Wednesday, December 6, 2017 4:47 PM
    Wednesday, December 6, 2017 4:47 PM

All replies

  • Well, I decided to reboot the server and give it another try and that seemed to do he trick.  It finally got done with the Connection piece.

    Thanks,

    • Marked as answer by Kelemvor33 Wednesday, December 6, 2017 4:47 PM
    Wednesday, December 6, 2017 4:47 PM
  • Once setup and working, Optimize it and keep it working properly using my script. Remember, a new WSUS Server does not mean that it's clean or optimized!

    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
    Microsoft MVP - Windows and Devices for IT

    Wednesday, December 6, 2017 5:50 PM