Announcement

Collapse
No announcement yet.

Client reporting to different doman WSUS server pull updates from microsoft

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Client reporting to different doman WSUS server pull updates from microsoft

    Hi,

    Trying to get a Windows 10 client to update from a WSUS server on a different site - the client is updating but its not reporting into the WSUS server. Looking at the client logs I notice the following

    2017/10/18 14:48:02.2359142 4816 4880 Agent [0]12D0.1310::10/18/2017-14:48:02.235 [agent]WSUS server: NULL
    2017/10/18 14:48:02.2359149 4816 4880 Agent [0]12D0.1310::10/18/2017-14:48:02.235 [agent]WSUS status server: NULL
    2017/10/18 14:48:02.2359152 4816 4880 Agent [0]12D0.1310::10/18/2017-14:48:02.235 [agent]Alternate Download Server: NULL

    But within the registry of that machine its configured to point to a WSUS server to report (image attached)



    Any thoughts? Thanks


  • #2
    Is it using the correct port number?
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2

    Comment


    • #3
      Yep I can telnet to the port and it connects so no firewall issues or anything

      Comment


      • #4
        Interestingly enough if you enable UseWUServer it populates [agent]WSUS status server: https://updates...

        So that event is referring to a WSUS server (for updates) rather than reporting to a WSUS server it would seem?

        Comment


        • #5
          Which operating system? If it's Windows 10 you might want to keep Dual scan in mind too.
          https://batchpatch.com/dual-scan-dif...reators-update

          Comment


          • #6
            Got this one working in the end, used group policy to apply the majority of settings and then applied the settings which weren't available in GP via registry.

            Comment

            Working...
            X