Data Centers

Making SMS 2007 collections based on organizational unit

This Systems Management Server 2007 tip instructs you on how to make a package go out to a select group of systems. Rick Vanover says that one of the better ways to deploy a package is through collections organized by the Active Directory organizational unit.

If you're new to Systems Management Server (SMS) 2007, don't let the cumbersome interface scare you away. Once you get past the learning curve, it's not too bad.

Here's a tip about how to make a package go out to a select group of systems. One of the better ways to deploy a package is through collections organized by the Active Directory organizational unit (OU). Getting the syntax down for the queries is a little rough without having a collection to work from to see correct query examples. But it's simple to make a query based on the OU of the computer accounts.

There are two ways to make this type of query for collection membership: from a query statement or from the Create Direct Membership Rule Wizard. I'll walk you through the process for a query statement because, once you make a collection, it is easier to modify the query statement from an existing item based on the OU path. Follow these steps to launch the New Collection Wizard:

  1. In the SMS Configuration Manager Console, go to Site Database | Computer Management | Collections and then right-click and choose New Collection.
  2. Populate a computer name and comment if needed and then click Next.
  3. In the Membership Rules section, launch the Query Rule Properties dialog box by clicking the Database icon.
  4. Click the Edit Query Statement button, select the Criteria tab, click the star icon for a new query, and then select System Resource as the Attribute Class and select System OU Name as an Attribute. Figure A is a screenshot of these steps.

Figure A

Figure A

Once you select the Attribute Class and Attribute, you will be prompted for a Value and an Operator. I generally make collections based directly on OUs and have one collection for each OU (servers, workstations, etc.). If you are specifying a full path, the FQDN of the Active Directory domain and a path to the OU is used to locate the OU in question. So, in my example, the path is CORP.AMCS.TLD/SERVERS/WIN2008 for the WIN2008 OU for servers of that type. You can see the query in Figure B. Figure B

Figure B

You can also browse the OUs by the Value field. Once the OU is placed in the criterion, save the changes to return back to the SMS Configuration Manager Console, and the new collection will display with the relevant system members.

Stay on top of the latest Windows Server 2003 and Windows Server 2008 tips and tricks with our free Windows Server newsletter, delivered each Wednesday. Automatically sign up today!

About

Rick Vanover is a software strategy specialist for Veeam Software, based in Columbus, Ohio. Rick has years of IT experience and focuses on virtualization, Windows-based server administration, and system hardware.

5 comments
matt_lee
matt_lee

Two recommendations: 1. In Figure A, set the Attribute name to "Netbois Name" 2. In Figure B, use System Resource - canonicalName. And lower case is like %fqdn/Sales%. ...that will pull any computer under the Sales OU, including sub OUs.

jusni
jusni

How do you make it show all computers, even those in Sub-OUs?

pubmo
pubmo

this does not work for specifying pc's that are not in a given ou...probably because there appear to be one systemouname attribute for each subfolder in AD that the pc's are in

jse79
jse79

Exactly, there is no SMS 2007. No where in the installation wizard, documentation, or management interface does this product call itself SMS... I mean, we don't still refer to Exchange Server as Microsoft Mail - and we don't still refer to ISA Server as Proxy Server...

bouska
bouska

Hmm, if I know Systems Management Server (SMS) finished with version 2003 and now there is System Center Configuration Manager (SCCM) 2007.

Editor's Picks