locked
Windows 10 and Server 2016 WSUS clients show Not yet reported RRS feed

  • Question

  • All my Windows 10 and Server 2016 WSUS clients show "Not yet reported".  This is a freshly loaded Windows 2016 Server with a clean load of WSUS.  All other 2008, 2012 and Windows 7 boxes report in fine and have the same GPOs applied to them.  This seems to have started on or around September 16th, as they were reporting in prior to then.  We did a fresh install today, hence the "Not yet reported", prior to the fresh install they said last reported ~9/17/2017.  If I show the Last Contact column in WSUS, they all show contacted very recent (within two hours).  I have another WSUS server at another location configured exactly the same with the same type of client OS and they all report in properly.  We are using a remote SQL 2012 Enterprise installation for the database on a Server 2016 box.  We do use SSL for encryption and browsing to https://xxx-xxx-xxx-pmgr:8531/Selfupdate/ produces the proper blank page.

    BTW, all the updates are functioning properly, they just aren't reporting which affects reporting.
    Thursday, October 26, 2017 7:57 PM

All replies

  • Hello,

    Do you mean that Windows 10 and Windows server 2016 can get updates from your WSUS server, but they show as Not yet reported?

    Have you checked Windowsupdate.log on them? Please make sure they are pointing to the new WSUS server for updates. 

    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.

    Tuesday, October 31, 2017 5:28 AM
  • That is exactly what I am saying.

    When I try to convert the Windowsupdate.log with the PowerShell command Get-WindowsUpdateLog I still get 1600/12/31 18:00:00.0000000 1208  2508                  Unknown( 10): GUID=638e22b1-a858-3f40-8a43-af2c2ff651a4 (No Format Information found).

    even though I have tried these as well:


    Tuesday, October 31, 2017 11:17 AM
  • My script will fix this issue. Yes, even on a new WSUS server. Remember, new does not mean that it's optimized or clean!

    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

    Tuesday, October 31, 2017 5:40 PM
  • How exactly will this script fix my specific problem, I see your same post on everybody's questions on WSUS.  What specific portion of the script will fix this very specific issue?  I already have a script that does all of this except your number 10.  I use this from SQL along with a scheduled task for re-indexing:

    USE SUSDB
    GO
    DELETE FROM tbEventInstance WHERE EventNamespaceID = '2' AND EVENTID IN ('381', '382', '384', '386', '387', '389')

    And this as a PowerShell script on WSUS:

    #Change server name and port number and $True if it is on SSL
    
    $Computer = $env:COMPUTERNAME
    [String]$updateServer1 = $Computer
    [Boolean]$useSecureConnection = $True
    [Int32]$portNumber = 8531
    
    # Load .NET assembly
    
    [void][reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")
    
    $count = 0
    
    # Connect to WSUS Server
    
    $updateServer = [Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer($updateServer1,$useSecureConnection,$portNumber)
    
    write-host "<<<Connected sucessfully >>>" -foregroundcolor "yellow"
    
    $updatescope = New-Object Microsoft.UpdateServices.Administration.UpdateScope
    
    $u=$updateServer.GetUpdates($updatescope )
    
    foreach ($u1 in $u )
    
    {
    
    if ( $u1.IsSuperseded -eq 'True' `
     -or $u1.Title -like '*2005*' `
     -or $u1.Title -like '*2007 Microsoft*' `
     -or $u1.Title -like '*2010*' `
     -or $u1.Title -like '*10 Pro N*' `
     -or $u1.Title -like '*10 Education*' `
     -or $u1.Title -like '*10 Enterprise N,*' `
     -or $u1.Title -like '*10 Version 1511*' `
     -or $u1.Title -like '*10 Version 1607*' `
     -or $u1.Title -like '*15042*' `
     -or $u1.Title -like '*AMD64*' `
     -or $u1.Title -like '*64-Bit Edition*' `
     -or $u1.Title -like '*Accounting*' `
     -or $u1.Title -like '*Business*' `
     -or $u1.Title -like '*Calendar*' `
     -or $u1.Title -like '*CardSpace*' `
     -or $u1.Title -like '*Excel 2002*' `
     -or $u1.Title -like '*Excel 2007*' `
     -or $u1.Title -like '*Groove*' `
     -or $u1.Title -like '*Infopath*' `
     -or $u1.Title -like '*Insider Preview*' `
     -or $u1.Title -like '*IntelliType*' `
     -or $u1.Title -like '*Internet Explorer 10*' `
     -or $u1.Title -like '*Internet Explorer 5*' `
     -or $u1.Title -like '*Internet Explorer 6*' `
     -or $u1.Title -like '*Internet Explorer 7*' `
     -or $u1.Title -like '*Internet Explorer 8*' `
     -or $u1.Title -like '*Itanium*' `
     -or $u1.Title -like '*Lang Pack*' `
     -or $u1.Title -like '*Language Pack*' `
     -or $u1.Title -like '*Lync*' `
     -or $u1.Title -like '*Windows Malicious Software Removal*' `
     -or $u1.Title -like '*Office 2003*' `
     -or $u1.Title -like '*Office 2007*' `
     -or $u1.Title -like '*OneDrive*' `
     -or $u1.Title -like '*OneNote*' `
     -or $u1.Title -like '*Outlook*' `
     -or $u1.Title -like '*PowerPoint*' `
     -or $u1.Title -like '*Project*' `
     -or $u1.Title -like '*Publisher*' `
     -or $u1.Title -like '*SharePoint*' `
     -or $u1.Title -like '*Silverlight*' `
     -or $u1.Title -like '*SkyDrive*' `
     -or $u1.Title -like '*Skype*' `
     -or $u1.Title -like '*Technical Preview*' `
     -or $u1.Title -like '*for Windows Server 2003*' `
     -or $u1.Title -like '*for Windows XP*' `
     -or $u1.Title -like '*upgrade to Windows 10*' `
     -or $u1.Title -like '*Visio*' `
     -or $u1.Title -like '*Windows 10 Pro*' `
     -or $u1.Title -like '*Windows 10 Team*' `
     -or $u1.Title -like '*Works Suite*')
    
    
    {
    
    write-host Decline Update : $u1.Title
    
    $u1.Decline()
    
    $count=$count + 1
    
    }
    
    }
    
    write-host Total Declined Updates: $count
    
    trap
    
    {
    
    write-host "Error Occurred"
    
    write-host "Exception Message: "
    
    write-host $_.Exception.Message
    
    write-host $_.Exception.StackTrace
    
    exit
    
    }
    Invoke-WsusServerCleanup -CleanupObsoleteComputers -CleanupObsoleteUpdates -CleanupUnneededContentFiles -CompressUpdates -DeclineExpiredUpdates -DeclineSupersededUpdates

    Tuesday, October 31, 2017 6:17 PM
  • 1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster. (No one else has this - your script doesn't deal with this)
    2. Remove all Drivers from the WSUS Database (Default; Optional). (Your script doesn't deal with this)
    3. (Your script takes care of #3 along with many other options - good for your implementation - that's great)
    4. Remove declined updates from the WSUS Database. (Your script doesn't deal with this)
    5. (Your script takes care of #5 - that's great)
    6. Compress Update Revisions. (Your script doesn't deal with this)
    7. Remove Obsolete Updates.(Your script doesn't deal with this)
    8. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).(Your script doesn't deal with this as a feature, but does take care of this using the Invoke-WsusServerCleanup with -CleanupObsoleteComputers - but it's not configurable.... moot point though. that's great.)
    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. (Your script doesn't deal with this but since this is manual, this doesn't necessarily count)
    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.(Your script doesn't deal with this but since this is manual, this doesn't necessarily count)
    11. Run the Recommended SQL database Maintenance script on the actual SQL database. (Your scheduled task for re-indexing takes care of #11 - that's great)
    12. Run the Server Cleanup Wizard. (Your script takes care of #5 - that's great)

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



    • Edited by AJTek.caMVP Tuesday, October 31, 2017 7:38 PM made #8 more clear.
    Tuesday, October 31, 2017 7:35 PM
  • This script, albeit nice, did not fix the problem.  We started to have the issue at another site after upgrading from Server 2012 to 2016.  We ended up having to run a WSUS reset.  As soon step 7 was complete, all computers starting reporting in.

    How to Do a Reset:

    Note: You may want to execute the procedure below during off hours as your WSUS server will be downloading quite a bit of data, ours for this site was ~60GB.

    1. Close any open WSUS consoles.

    2. Go to Administrative Tools – Services and STOP the Update Services service.

    3. In Windows Explorer browse to the WSUSContent folder (typically D:\WSUS\WSUSContent or C:\WSUS\WSUSContent)

    4. Delete ALL the files and folders in the WSUSContent folder.

    5. Go to Administrative Tools – Services and START the Update Services service.

    6. Open a command prompt and navigate to the folder: C:\Program Files\Update Services\Tools.

    7. Run the command WSUSUtil.exe RESET

    • Proposed as answer by onefiscus Tuesday, April 3, 2018 3:40 PM
    Tuesday, April 3, 2018 11:12 AM