Dynamic collections in Microsoft Configuration Manager (SCCM/ConfigMgr) allow administrators to automate device grouping using WQL queries. Instead of manually adding systems, you can build collections that update automatically based on attributes like hardware model, OS version, or Active Directory OU. In this guide, we’ll walk through creating dynamic collections step by step and explore key attribute classes you can leverage for smarter deployments.
How to Create a Dynamic / Query-Based Collection
In the Configuration Manager console, navigate to Asset and Compliance. Right‑click Device Collections, and then select Create Device Collection.
On the General page, enter a Name for your collection. Next, click Browse under Limiting Collection, and select the collection you want to use as the membership boundary for your new collection.
A limiting collection defines the boundary for membership. Any query‑based collection you create will only include devices that are already part of the limiting collection. In other words, your new collection becomes a subset of the limiting collection.
On the Membership Rules page, click on Add Rule and select Query Rule from the drop-down list.
On the Query Rule Properties dialog box, enter a name for the query rule and then click on Edit Query Statement.
In the Query Statement Properties dialog box, select the Criteria tab and click on Add (Yellow Start) to add a new query rule.
In the Criterion Properties dialog box, select the following.
Criterion Type: Simple value
Where: Click on Select…
In the Select Attribute dialog box, select the following
Attribute class: System Resource
Attribute: System OU Name
Click on Ok to return to the previous dialog box.
Back to the Criterion Properties dialog box, select the following
Operator: is like
Value: Click on Value…
In the Values dialog box, you will see the list of all Active Directory OUs that have been discovered as part of Active Directory system discovery.
Select the desired OU and click on Ok to return to the previous window.
Back on the Criterion Properties dialog box, verify the query rule and click on Ok.
You are now back to the Query Statement Properties dialog box. Click on Ok to close the dialog box.
On the Query Rule Properties dialog box, click on Ok to return to the Create Device Collection Wizard.
On the Membership Rules page, select Use incremental updates for this collection if you want to enable incremental updates.
Click on Next
On the Summary page, review the collection details and click Next. The collection will be created, and you will then see the Progress and Completion pages confirming the process.
Different Attribute Classes and Attribute Names for Dynamic Collections
In the demonstration above, we used the System Resource class with the System OU Name attribute. This allows the collection membership to be populated dynamically based on the Active Directory Organizational Unit (OU) name.
Attribute class: System Resource
Attribute Name: System OU Name
SCCM provides many SMS Provider WMI Server classes (also called attribute classes) that you can use to build device collections based on different criteria. By selecting the appropriate class and attribute, you can dynamically group devices according to hardware details, operating system properties, Active Directory information, or other configuration data
Other posts in this series
The following blog posts provide detailed coverage of the attribute classes most commonly used when creating dynamic collections or SCCM queries. The process for creating a dynamic collection remains the same as described above—you simply select the appropriate Attribute Class and Attribute Name based on your requirements.
Each post also includes complete WQL queries that you can copy and paste directly into the Query Editor to quickly build your collections.
Explore these related guides to build dynamic collections and queries more effectively:
- Operating System Attribute Queries – Learn how to target collections based on OS version and edition.
- Computer System Attribute Queries – Create collections filtered by hardware model or manufacturer.
- Software Attribute Queries – Identify devices with specific installed applications or software versions.
- SCCM Device Collection Based on Computer Hardware Details – Target collections using manufacturer, model, or chassis type.
- SCCM Collection Based on OS Optional Features – Query devices by Windows optional features such as .NET Framework or Hyper‑V.
Frequently Asked Questions (FAQs)
Q1. What is a dynamic collection in SCCM?
A dynamic collection is a device or user collection in SCCM that automatically updates its membership based on query rules (WQL). This ensures that devices meeting specific criteria are always included without manual intervention.
Q2. What is the role of a limiting collection?
A limiting collection defines the boundary for membership. Any new query‑based collection you create will only include devices that are already part of the limiting collection, making it a subset.
Q3. Can I use multiple attribute classes in one query?
Yes. You can combine different attribute classes (such as Operating System, Computer System, or System Resource) to refine your query and target devices more precisely.
Q4. What are incremental updates in SCCM collections?
Incremental updates allow SCCM to refresh collection membership more frequently without running a full update cycle. This helps keep collections current while reducing load on the site server.
Q5. Where can I find ready‑to‑use queries?
This blog series includes complete WQL queries for common scenarios. You can copy and paste them directly into the Query Editor to quickly build collections.
Conclusion
Dynamic collections in SCCM (ConfigMgr) are a powerful way to automate device grouping and streamline deployments. By leveraging SMS Provider WMI Server classes and attributes, administrators can build collections that adapt to organizational changes—whether based on Active Directory OUs, hardware models, or operating system versions. Using limiting collections ensures proper scoping, while incremental updates keep memberships fresh without heavy server load.
With the examples and queries provided in this series, you can quickly create collections tailored to your environment, saving time and improving accuracy in your configuration management workflows
Related Posts:
- How to Create Dynamic Collection in SCCM
- Enclosure Chassis Types Value & Description | ConfigMgr | SCCM
- ConfigMgr: Maintenance Window for member of specific collection – SQL Query
- SCCM Dynamic Collection for Windows 10 / 11 Devices
- SCCM Device Collection Equivalents in Microsoft Intune for App Deployment
- SCCM Dynamic Collection Based on Device Type | Collection Queries
- SCCM Collection Based on Operating System Optional Features
- SCCM Device Collection Based on Installed Software Products & Inventoried Files
- SCCM Device Collection Based on Computer Hardware Details
- SCCM Collection Queries for Opearting System Attribute Class
- SCCM Collection Queries for System Resource (SMS_R_System) Attribute Class
- SCCM Dynamic Collection using Application Deployment Status
- SCCM Dynamic Collection Based on Configuration Baseline Compliance Status
- How to Create , View and Organize SCCM Maintenance Windows
- How to Provision Windows 10 / 11 Device using Intune and Windows Autopilot
Subscribe to Techuisitive Newsletter
Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.