locked
Client Side Targeting & Downstream Replica RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We are having an issue getting Client Side Targeting to work at the remote site.

    Setup: 

    • 2x WSUS 3.2 running on Server 2008 R2.  Main site is the Master, remote site is downstream replica.
    • 4 Groups created in WSUS:  Main site PCs, Main site Servers, Remote site PCs, Remote site Servers.
    • Have 4 separate GPOs configured for Client Side Targeting pointed to the respective WSUS Groups.
    • Have 2 separate GPOs configured for specifying Microsoft Update location, main site points to main WSUS Server, remote site points to remote WSUS Server
    • The main WSUS Server is synchronizing from Microsoft Update, and the downstream replica from main site
    • Both synchronizations are successful each day
    • Main site WSUS console appears to see all PCs and Servers
    • In Main site WSUS console, Main site Servers are showing up in WSUS Group correctly, and some PCs, most are in "unassigned"
    • In Main site WSUS console, No Remote site Servers or PCs are showing up in Remote site Groups
    • In Remote site WSUS console, it sees some remote site PCs under "unassigned", does not see any main site PCs or Servers, and sees nothing under any WSUS Groups

    Any ideas?

    Monday, February 1, 2016 7:14 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    >>In Remote site WSUS console, it sees some remote site PCs under "unassigned", does not see any main site PCs or Servers,

    The replica server is only able to see the clients which use it as the update source. It's normal. The main server is able to see all of the clients because the replica server roll up the information.

    If WSUS can't find the group reported by a specific client, this client will be put into the unassigned group.

    First, we should check the result of the group policy on the clients having this issue.:

    • gpupdate /force
    • gpresult /h C:\report.html

    Please make sure that the group name in the report is exactly same with the group name on WSUS.

    Also, please check the windowsupdate.log of the clients with this issue. It may give some hints.

    Best Regards.

    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by Steven_Lee0510 Sunday, February 28, 2016 1:05 PM
    Tuesday, February 2, 2016 12:50 PM