How to Use SCCM Collections and Query Rules Effectively

Collections are the targeting mechanism for almost everything in SCCM. Deployments, reports, and client settings all point at a collection rather than individual devices. Query-based (dynamic) membership rules are what make collections actually maintain themselves rather than requiring manual updates every time a device’s status changes. Direct vs query-based membership Direct membership (manually adding specific […]

How to Use SCCM Collections and Query Rules Effectively

Collections are the targeting mechanism for almost everything in SCCM. Deployments, reports, and client settings all point at a collection rather than individual devices. Query-based (dynamic) membership rules are what make collections actually maintain themselves rather than requiring manual updates every time a device’s status changes.

Direct vs query-based membership

Direct membership (manually adding specific devices) is fine for a genuinely static, small group like a pilot test set. For anything that should reflect a changing condition. “all Windows 11 devices,” “all laptops in the Sales OU,” “all devices that haven’t checked in for 30 days”. A query rule is the right tool, since it re-evaluates automatically on the collection’s refresh schedule.

A practical example query

A collection for all Windows 11 devices, built via WQL:

select SMS_R_SYSTEM.ResourceID from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Workstation 10.0.2%"

Watch collection refresh performance at scale

In large environments, avoid setting many collections to a frequent scheduled refresh interval (like every few minutes). Each refresh is a real query load against the site database. Use “incremental updates” for collections that genuinely need near-real-time membership, and a much longer scheduled interval (daily or longer) for everything else.

Nest collections to build layered targeting

Use “limiting collection” scoping to build hierarchies, for example, a broad “All Windows 11 Devices” collection, limited further by a “Sales Department” collection to get a precise, maintainable “Sales Department Windows 11 Devices” target for a specific deployment, rather than writing one increasingly complex query trying to capture every condition at once.

For official guidance, see Microsoft’s Configuration Manager documentation.

🛠️

Gear We Recommend

Testing configs is easier with a dedicated admin machine set up right. Here’s the kit we use.

Browse our Windows Admin Toolkit picks on Amazon

As an Amazon Associate, TechyGeeksHome earns from qualifying purchases.


Discover more from TechyGeeksHome

Subscribe to get the latest posts sent to your email.

Andrew Armstrong

Andrew Armstrong is a UK-based IT professional with 26+ years of hands-on experience in Windows, Windows Server, SCCM/ConfigMgr, Intune, Active Directory, PowerShell and enterprise infrastructure.

He founded TechyGeeksHome in 2010 and has published 770+ practical guides to real-world IT problems. He also builds free Windows utilities, including Ultimate Settings Panel, which has been downloaded over 850,000 times.