locked
Can't get computer to report to WSUS? RRS feed

  • Question

  • I'm setting up a WSUS server in the domain at work. I have 2 computers that I'm working with as my test computers. One is a Win10 and the other is a Server 2016. The Win10 reported to the WSUS just fine, the Server 2016 did not.

    I have ran the commands to try to get to report, but it's not working.

    wuauclt /detectnow

    wuauclt /reportnow


    It has been sitting there in the queue for like 3 days now with no status change.

    Any special commands or tricks to get it to report?

    Wednesday, August 28, 2019 6:36 PM

Answers

All replies

  • Hi,

    on the Windows Server 2016 check if it has received the WSUS-Information ("who is my wsus?") by checking the registry: 

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

    If you can find your WSUS Server in here, that means you win2016 has some issues reporting to the stated WSUS.

    In this case you can reset your WSUS ID as already described by me in the following thread: https://social.technet.microsoft.com/Forums/de-DE/26b8e5c8-7417-4581-b765-8130da92d2ad/does-sysprep-generalize-oobe-reset-also-the-wsussid?forum=windows_Serverde#cf0181cb-ba74-4b4d-8c2f-cb7b35d61c69

    If you can not find your WSUS in the Registry Setting, that means there is something wrong with your GPO you are using to distribute your wsus-server information.

    regards, pat

    Wednesday, August 28, 2019 7:44 PM
  • It does point to the correct WSUS in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.

    The SID's are all different, so there is no SID issue. 

    FYI, I did have 1 computer report just fine, but as I add more and more they are all listed as "Not yet reported".

    Wednesday, August 28, 2019 8:56 PM
  • Hi finsfree11,
      

    Please do the following on the client server 2016:
      

    1. Stop Windows Update service
    2. Delete everything in "C:\Windows\SoftwareDistribution".
      NOTE: not the SoftwareDistribution folder itself.
    3. Start Windows Update service
    4. Open powershell in administrator role and run script at a time:
      > (new-object -Comobject Microsoft.Update.AutoUpdate).Detectnow()
      Give it about 10 minutes and then refresh the WSUS console window to see if it connects. 
        

    This is the usual method to get Clients connected. 
    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, August 29, 2019 2:21 AM
  • Follow up My guidance . Definitely you will be able to fix,

    https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0

    Thursday, August 29, 2019 2:22 AM
  • Hi finsfree11,
      

    Please do the following on the client server 2016:
      

    1. Stop Windows Update service
    2. Delete everything in "C:\Windows\SoftwareDistribution".
      NOTE: not the SoftwareDistribution folder itself.
    3. Start Windows Update service
    4. Open powershell in administrator role and run script at a time:
      > (new-object -Comobject Microsoft.Update.AutoUpdate).Detectnow()
      Give it about 10 minutes and then refresh the WSUS console window to see if it connects. 
        

    This is the usual method to get Clients connected. 
    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.

    After following this to a "T" the server 2016 still wasn't able to report.

    Seems like only Server 2016 is has this issue...see attached

    Friday, August 30, 2019 1:43 AM
  • Also, why is it showing that the update installed but was not approved? How can you install something that hasn't been approved?

    Friday, August 30, 2019 2:02 AM
  • Follow up My guidance . Definitely you will be able to fix,

    https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0

    You're going to have to go into more detail with this. Also, the fact it wasn't tested with Server 2016 concerns me.


    Friday, August 30, 2019 2:08 AM
  • After following this to a "T" the server 2016 still wasn't able to report.

    Seems like only Server 2016 is has this issue...see attached

    Try to check their WindowsUpdate.log file on these unreportable Windows Server 2016 clients, and check the WSUS server name to see if there are any errors in the context (eg: The server returned HTTP status code '500').
       

    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, August 30, 2019 7:46 AM
  • After following this to a "T" the server 2016 still wasn't able to report.

    Seems like only Server 2016 is has this issue...see attached

    Try to check their WindowsUpdate.log file on these unreportable Windows Server 2016 clients, and check the WSUS server name to see if there are any errors in the context (eg: The server returned HTTP status code '500').
       

    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.

    Here are the results of the Get-WindowsUpdateLog command. I'm only posting what I thought was the issue. click "Ctrl & +" to make bigger....


    • Edited by finsfree11 Wednesday, September 4, 2019 8:54 PM
    Wednesday, September 4, 2019 8:52 PM
  • According to the log screenshot, Communication with WSUS server is failed.

    Use IP of the Server instead of FQDN and then check the status.

    Check firewall status for communication between WSUS and client PCs.

    Check below for step by step troubleshooting,

    https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0

    • Marked as answer by finsfree11 Friday, September 6, 2019 1:25 AM
    Thursday, September 5, 2019 2:28 AM
  • According to the log screenshot, Communication with WSUS server is failed.

    Use IP of the Server instead of FQDN and then check the status.

    Check firewall status for communication between WSUS and client PCs.

    Check below for step by step troubleshooting,

    https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0

    I did get 2 Server 2016 to report after changing from FQDN to IP address. I'm just waiting until tonight to be able to reboot the rest so they will get the new GPO settings. It only worked after a reboot.

    I'll keep you posted.

     

    Thursday, September 5, 2019 4:52 PM
  • No need to restart to apply group policies...

    use gpupdate /force command..

    Thursday, September 5, 2019 5:29 PM
  • If that doesn't work, here's the guide that will make it work.

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

    99.9999999% of the time this has worked for me and everyone else that I've helped. The small percentage that it didn't work on - the issue was something like the wrong GPOs, Firewall, Proxy, or DNS issues.


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

    Thursday, September 5, 2019 7:47 PM
  • Oh, and make sure IPv6 is ENABLED. And that the "Set the alternate download server:" is set to the same URL as noted in Part 4 of my blog series on How to Setup, Manage, and Maintain WSUS - https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-4-creating-your-gpos-for-an-inheritance-setup/

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

    Thursday, September 5, 2019 7:49 PM
  • According to the log screenshot, Communication with WSUS server is failed.

    Use IP of the Server instead of FQDN and then check the status.

    Check firewall status for communication between WSUS and client PCs.

    Check below for step by step troubleshooting,

    https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0

    Okay, every server and workstation reported after about 4 hours. Changing the FQDN to an IP address worked. You have to let it sit and do it's thing but eventually everything connected to the WSUS.

    Thank you so much for your help!

    Friday, September 6, 2019 1:29 AM