locked
Windows 10 Pro Not Reporting RRS feed

  • Question

  • For years, I've had WSUS running on 2012R2 server. All was well for Windows 7 updates. Once we began migrating to Win 10, WSUS would show status of "Not yet reporting" for all Windows 10 machines.

    I did some research and figured I would spin up a new WSUS running on Win 2019 server to try and resolve.

    Same issues. Windows 7 reports as normal and all Win 10 workstations report as Not yet reporting on this brand new WSUS server.

    The 2019 WSUS is still running as a downstream server to the 2012R2.

    What can be done to properly report the Win 10 machines?

    Thursday, May 2, 2019 11:25 AM

All replies

  • Hi Decki,
      

    Thank you for posting here.
    The following two articles describe the troubleshooting steps for such failures, please try to check:
      

    Reply back with the results would be happy to help.
     

    Regards,
    Yic

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

    Friday, May 3, 2019 1:35 AM
  • Take a look at my guide below:

    https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/

    It gives you the client side script and explains WHAT it's doing and WHY.


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Sunday, May 5, 2019 12:25 PM
  • Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation, as always.
     

    Regards,
    Yic

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

    Wednesday, May 8, 2019 1:37 AM
  • Still not working. I went through your guides, but still having issues.  I still have many Win 10 workstations not reporting to WSUS on 2019. Any other suggestions for a fix?

    • Edited by decki Wednesday, May 8, 2019 5:43 PM
    Wednesday, May 8, 2019 4:32 PM
  • Hi Decki,
      

    I noticed that your WSUS server is based on Windows Server 2012 R2 WSUS 6.3. In order to support Windows 10 and Server 2016/2019, please make sure that the prerequisites are as follows:
      

    1. Please check if the WSUS server has already installed KB2919355 and KB3159706?
      Or have you installed the latest monthly rollups?
        
    2. Open an elevated Command Prompt window, and then run the following command (case sensitive, assume "C" as the system volume):
      > "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
        
    3. Restart the WSUS service.
        

    Reply back with the results would be happy to help.
      

    Regards,
    Yic

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

    Thursday, May 9, 2019 2:49 AM
  • If you have one of the first 2 KB's installed that Yic mentioned, you'll need to follow part 3 of my 8 part blog series on How to Setup, Manage, and Maintain WSUS as it deals with Windows as a Service (WaaS)

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-3-windows-as-a-service-waas-and-group-policy-administrative-templates/


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Thursday, May 9, 2019 3:40 AM
  • Also, are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Thursday, May 9, 2019 3:41 AM
  • I have spun up a new 2019 server which is now my downstream server.

    I have then changed the GPO to point to the new 2019 server.

    The KBs mentioned in your post do not apply to 2019 it appears.

    I have waited many days for things to sync between the 2012R2 server and the new 2019 server, which appear to have completed. WIN 10 clients still not reporting.

    Do I need to break the connection between the original 2012R2 WSUS and the new 2019 downstream server maybe?

    Friday, May 10, 2019 1:29 PM
  • No, I'd be verifying that the GPOs are actually changing on the client.

    From an Administrative Command Prompt on an affected client, run the following:
    gpresult /h gpo.htm
    and share the result with your favourite method or pastebin it so that we can see it.


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Saturday, May 11, 2019 2:04 AM
  • GPO is working fine. All clients have been pointed to the new 2019 WSUS server. So strange, none of my WIn 10 systems are reporting to WSUS. Even clean installs cannot report. Please assist further.
    Thursday, May 23, 2019 11:57 AM
  • Try to download the WSUS iuident CAB file from the client machine.

    http://server.domain.local:8530/selfupdate/iuident.cab
    https://server.domain.local:8531/selfupdate/iuident.cab

    and then try to browse to:

    http://server.domain.local:8530/ClientWebService/client.asmx
    https://server.domain.local:8531/ClientWebService/client.asmx

    If you can download it and browse to it, that's the port/url to use in your GPO. If you can't, check firewall settings and port settings.

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Thursday, May 23, 2019 2:27 PM
  • Ok, so I was able to download the CAB file from the client machine.

    Browsing to the ClientWebService gave me a page showing scripts for C# and VB.

    I then added the FQDN instead of just the PQDN. I doubt that should make a difference, but we'll see.

    Thursday, May 23, 2019 2:51 PM
  • Ok, I believe I got this working. Just to recall the situation, my original WSUS server was running on 2012R2. Once we began to upgrade to WIN10 is when we started having issues with WIN10 reporting to the 2012R2 server.

    I then spun up a new 2019 server and installed WSUS and configured as a downstream server to the 2012R2. Pointed GPO to 2019 server and let it do its thing for a few days. Unfortunately, still had the same problem with WIN 10 not reporting.

    I then found a post about uninstalling WSUS and reinstall with a clean database on the 2019.

    I went through these steps by following that post and running these under Admin in Powershell:

    1. Uninstall-WindowsFeature -Name UpdateServices,Windows-Internal-Database -Restart
    2. Post restart, delete EVERYTHING in the C:\Windows\WID\
    3. Install-WindowsFeature UpdateServices -Restart

    I then had to reconfigure all of my settings, but once done, it appears many of the WIN10 clients are now reporting. I only have about 25% of my clients being seen by the server, but within another day or so, I should begin to see all of them.



    Friday, May 24, 2019 11:13 AM