locked
clients cannot connect to new replica server RRS feed

  • Question

  • Hi,

    I replaced old wsus replica server by a new one (Server 2019).

    1.The server properly syncs with Upstream and downloaded all the content.

    2. GPO on the clients machines shows that the client gets new server name correctly.

    3. in log files of client machines the name of new server appears but I cannot find the clue what is the real problem.

    I uploaded 2 clients log files. (one is from Windows 7 another from Server 2019).

    No one machine of the target subnet reports to the WSUS. So I make a conclusion that it is SERVER Problem.

    Firewall on the server is OFF.

    Please check logs and hopefully help with a problem solving.

    https://1drv.ms/u/s!Av7GxVRWTkZlgierFeniKWgOHH3W?e=AIiGvn

    Thanks.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Monday, August 19, 2019 1:48 PM

Answers

  • Hi,
      

    For this section of the client computer that points to the new WSUS server, check the group policy applied to these clients:
      

    • Specify intranet Microsoft update service location 
      (location: Policies > Administrative Templates > Windows Components > Windows Update)
      Check the address filled in by "Intranet Update" and "Intranet Statistics Server". It is recommended to use the FQDN + port number of the WSUS server. (e.g http://jr12vwsusrep:8530 or http://jr12vwsusrep.domain:8530)
        

    After the change is complete, wait for the client computer to update the latest Group Policy.
    As a verification, make sure that the client computer can access the following URL:
      

    • http://jr12vwsusrep:8530/selfupdate/iuident.cab
        

    If the WSUS server is functioning properly, you should see a File Download window opening.
    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.

    • Marked as answer by pob579 Tuesday, August 20, 2019 5:24 PM
    Tuesday, August 20, 2019 3:11 AM

All replies

  • Hi,
      

    For this section of the client computer that points to the new WSUS server, check the group policy applied to these clients:
      

    • Specify intranet Microsoft update service location 
      (location: Policies > Administrative Templates > Windows Components > Windows Update)
      Check the address filled in by "Intranet Update" and "Intranet Statistics Server". It is recommended to use the FQDN + port number of the WSUS server. (e.g http://jr12vwsusrep:8530 or http://jr12vwsusrep.domain:8530)
        

    After the change is complete, wait for the client computer to update the latest Group Policy.
    As a verification, make sure that the client computer can access the following URL:
      

    • http://jr12vwsusrep:8530/selfupdate/iuident.cab
        

    If the WSUS server is functioning properly, you should see a File Download window opening.
    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.

    • Marked as answer by pob579 Tuesday, August 20, 2019 5:24 PM
    Tuesday, August 20, 2019 3:11 AM
  • Susclient GUID  should be deleted to report that client to WSUS properly as below,

    a. Stop the automatic service 
    b. Delete the SUSclientID reg key

    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

    c. Restart the automatic service  
    d. Run wuauclt /resetauthorization /detectnow  
    e. Run wuauclt /reportnow

    follow up below guidance for further troubleshooting,

    https://gallery.technet.microsoft.com/office/Troubleshooting-WSUS-d63da113

    Tuesday, August 20, 2019 9:58 AM
  • Yic, added FQDN... works like a charm... Never used it before.

    There were some changes on DNS structure... probably it's affected the name entry.

    Thanks.

    Udara, the question was not about one client issue.

    Whole subnet not reported to a new server...


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Tuesday, August 20, 2019 5:24 PM