locked
WSUS some machines slow at reporting in RRS feed

  • Question

  • Hello,

    Seems some workstations are slow at reporting in, but the contact time is up to date, I need these workstations to get the updates that are pending, what can I do?


    Wednesday, July 5, 2017 10:33 AM

All replies

  • Hello,

    Please use the following procedure to obtain a complete detection/reporting event:

    1. Record the system time
    2. Restart the Automatic Updates service (net stop/start wuauserv)
    3. Run the command wuauclt /resetauthorization /detectnow
    4. Wait thirty minutes
    5. Post all entries from the WindowsUpdate.log starting at the time recorded in Step #1

    Regards,

    Yan Li


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

    Thursday, July 6, 2017 6:50 AM
  • Hi,

    from PowerShell I run Get-WindowsUpdatelog then the report on the desktop just shows 1000s of these:

    1601/01/01 00:00:00.0000000 420   4504                  Unknown( 35): GUID=31ca3cef-8afe-c510-1cb4-36acd097dd79 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   4504                  Unknown( 10): GUID=31ca3cef-8afe-c510-1cb4-36acd097dd79 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   4504                  Unknown( 10): GUID=fceb5510-7e12-b0a1-8d1b-e6a079483552 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   4504                  Unknown( 10): GUID=fceb5510-7e12-b0a1-8d1b-e6a079483552 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   4504                  Unknown( 27): GUID=63557808-a162-9d44-2947-0ee68c9231e2 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   4616                  Unknown( 35): GUID=31ca3cef-8afe-c510-1cb4-36acd097dd79 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   4616                  Unknown( 10): GUID=31ca3cef-8afe-c510-1cb4-36acd097dd79 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   2552                  Unknown( 35): GUID=31ca3cef-8afe-c510-1cb4-36acd097dd79 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   2552                  Unknown( 10): GUID=31ca3cef-8afe-c510-1cb4-36acd097dd79 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   2552                  Unknown( 10): GUID=fceb5510-7e12-b0a1-8d1b-e6a079483552 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   2552                  Unknown( 10): GUID=fceb5510-7e12-b0a1-8d1b-e6a079483552 (No Format Information found).
    1601/01/01 00:00:00.0000000 420   2552                  Unknown( 27): GUID=63557808-a162-9d44-2947-0ee68c9231e2 (No Format Information found).

    Friday, July 7, 2017 3:41 PM
  • My script should fix your issue. It probably has to do with a fragmented database, along with a mass amount of superseded updates that need declining. My script will take care of it all for you and will make your WSUS far more responsive.

    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

    Sunday, July 9, 2017 4:46 AM