locked
WSUS clients not reporting to server RRS feed

  • Question

  • Hi All,

    i have setup a WSUS server and everything is find except that the client computers did not report to the server. I have configured a GPO already based on what i saw and read from the forums and youtube. What would be missing?

    Any idea would be great!

    Thank you very much and more power.

    Thursday, July 18, 2019 8:33 AM

All replies

  • Hi,
      

    Based on your description, I recommend the following to help you troubleshoot the issue:
      

    1. Please check your WSUS deployment process again according to the steps mentioned in the official article: "Configure WSUS"
    2. After completing the first step of checking, if the client has not yet reported to the WSUS server, please refer to the method mentioned in this article for troubleshooting: "Tips for troubleshooting WSUS Agents that are not reporting to the WSUS server"
        

    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, July 19, 2019 2:24 AM
  • Hi Sir,

    Thank you for your advise but i have read and tried everything that has written on the links you posted but still my WSUS server still not getting the computers report or contact into it.

    i have placed the group policy on the domain level, User OU level and even on the Computer/Machines OU level but still the same no computers reporting or contacting to the WSUS server.

    Any idea?


    • Edited by HeraldSison Wednesday, July 24, 2019 5:58 AM
    Wednesday, July 24, 2019 5:43 AM
  • Hi,
       

    Please perform the following steps to check:
       

    1. On the client side, to use CMD as an administrator, enter the following command:
      gpresult /h gpo.htm
      This will generate a report named gpo.htm under the User/<current username> path in the system partition. Open gpo.htm and check the Windows Components / Windows Updates section to see if the applied policy is correct.
         
    2. On the client side, use a browser on the client to access the following address:
      http://<WSUSservername>:8530/iuident.cab
      http://<WSUSservername>:8530/selfupdate/wuident.cab
      * Modify the port number according to the actual environment.
      If the WSUS server is functioning properly, you should see a File Download window opening. 
         
    3. On the client side, To use CMD as an administrator, enter the following command:
      > wuauclt /detectnow (For Windows 7)
      > usoclient.exe startscan (For Windows 10)
      Wait a while to check if the WSUS server receives a report from the computer.
         

    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, July 25, 2019 6:04 AM
  • Delete the affected clients from the WSUS MMC console and then run the client side script:

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

    Also, check to verify the GPOs are correctly set. See 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, August 8, 2019 5:57 AM