Skip to main content

How to configure WSUS computer groups with Active Directory

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.

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.
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

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.