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

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.

How to run GPResult on a remote client with PowerShell

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...