Wsus target group not updating cultural dating diferences by country
Any clues as to what I'm doing wrong, or where to start troubleshooting?I've ran more times than I care to mention, but they just don't want to budge into the correct group.Let’s start with the description of the server policy Server WSUSPolicy.Windows Update In our environment, we suggest to use this policy to install WSUS updates to Windows servers.I have two WSUS v3 servers, our company has a single domain AD that spans two sites, and each site has one WSUS server.The stub site's WSUS server is configured as a replica. all appear to propagate fine from the primary server to the replica.
It does not suit us, so we specify that the computers are to be distributed into groups using the client side targeting (group policies or registry parameters).
The next step – configure Windows clients to use a deployed WSUS server.
In this article we will consider how to configure clients of the WSUS server using Active Directory GPO (Group Policies).
Groups have been configured on wsus-primary, and have replicated to wsus-replica.
On the wsus-primary console, all appears well with clients that connect directly to it, however all the clients from the remote site (that normally talk to wsus-replica) appear in the group 'Unassigned Computers', despite the group policy results wizard showing they are picking up the policy that sets the correct group name.