Skip to main content

How to configure WSUS computer groups with Active Directory

By
I was not able to find a way to synchronize your AD computer groups with WSUS. I was able to find a procedure to allow you to use Group Policy to assign your clients into WSUS groups.

The first thing you need to do is to determine how your clients will be grouped. For those using Group Policy already, this may be in place.

Either create new group policies for each category of computer, our use an existing GPO.
To enable client-side targeting
1. In Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components, and then click Windows Update.
2. In the details pane, click Enable client-side targeting.
3. Click Enabled and type the name of the computer group in the box.
4. Click OK.

On the WSUS server, you now need to create the computer groups that you intend to use.
1. On the WSUS console toolbar, click Computers.
2. Under Tasks, click Create a computer group.
3. In the Group name box, type Test, and then click OK.

Now you must configure WSUS to allow the clients to populate themselves in the computer groups.
To specify the method for assigning computers to groups
1. On the WSUS console toolbar, click Options, and then click Computer Options.
2. In Computer Options, do one of the following:
3. Click Use Group Policy or registry settings on computers.
4. Under Tasks, click Save settings, and then click OK.

Labels:

Comments

Unknown said…
how do i get win7 clients to assign them self to win7 computer group
and server2008 clientes to assign them self to server2008 computer group?
I have created a gpo for both groups
and enabled client side target to one of the groups but then all clients assign themself to that group.
March 27, 2013 at 3:10 AM
Jason Yoder, MCT said…
Michael,

Check the scoping of your GPOs to make sure that GPOA does not get applied to computer group B. You can separate them into different OUs. You can use security group filtering of WMI filtering.

Jason
March 27, 2013 at 6:13 AM
Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more