locked
last contact work, last report don't work RRS feed

  • Question

  • Unfortunatly all my clients does not report to WSUS since 24 days. Last contact to WSUS works. Due to windowsupdate.log and IIS.log the download and report requests from clients to IIS on WSUS will be answered with  HTTP-Error 500. WSUS has Version 6.3.9600.18324 and runs on Windows 2012 R2. Clients have Win7 and Win10. Any idea? Thanks in advance.

    Monday, May 29, 2017 1:48 PM

All replies

  • What version of Win10? 1607 RTM? It had a known issue communicating with WSUS After the upgrade to RTM. It's fixed by installing manually or with another 3rd party tool, any CU after September 2016.

    Win7, on the other hand, should report.

    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

    Tuesday, May 30, 2017 2:14 AM
  • Hi,

    For this error:  HTTP-Error 500.

    Please check if the following KB is helpful:

    https://support.microsoft.com/en-us/help/2737219/unable-to-connect-to-wsus-administration-website

    Besides, i found a similar thread for your reference:

    https://social.technet.microsoft.com/Forums/windows/en-US/58affc4a-7611-43cc-a985-190cce0ff65e/unable-to-browse-the-default-website-after-installing-wsus?forum=winserverwsus

    Best regards,

    Andy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, May 30, 2017 2:57 AM
  • Hi Adam, thanks for your reply. I use your script already. See my notes on Spiceworks under detlevfritsche.
    Tuesday, May 30, 2017 8:01 AM
  • Hallo Andy, thanks for your reply. I have checked your threads, but unfortunatly, they do not concern.
    Tuesday, May 30, 2017 8:04 AM
  • Hallo Andy, thanks for your reply. I have checked your threads, but unfortunatly, they do not concern.

    DetF, please check if the following links is helpful:

    https://technet.microsoft.com/en-us/library/cc708627%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

    https://blogs.technet.microsoft.com/sus/2009/11/17/tips-for-troubleshooting-wsus-agents-that-are-not-reporting-to-the-wsus-server/

    Best regards,

    Andy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 5, 2017 9:01 AM
  • I'm sorry I must have missed your comment (page 26 for my records). I see you were using 2.07 - have you tried 2.11?

    As for my "optimizations",

    1. Remove all Drivers from the WSUS Database. (Done through SQL on -FirstRun, but using PowerShell API calls on daily runs)
    2. Shrink your WSUSContent folder's size by declining superseded updates. (PowerShell API Calls)
    3. Remove declined updates from the WSUS Database. (PowerShell API Calls)
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs). (SQL Query)
    5. Compress Update Revisions. (SQL Query running a built in Stored procedure)
    6. Remove Obsolete Updates. (SQL Query running a built in Stored procedure)
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days). (PowerShell API Calls)
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount. (PowerShell API Calls to IIS)
    9. Run the Recommended SQL database Maintenance script on the actual SQL database. (Done through SQL Script that Microsoft recommends to use and that many MVPs and Microsoft Helpers recommend)
    10. Run the Server Cleanup Wizard. (PowerShell API)

    I'm not doing much 'optimizations' of my own, just automating what has been recommended through time. I guess you can say that my optimizations are how often these are run.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Tuesday, June 6, 2017 1:04 AM