SCCM WQL Query – No ConfigMgr Client Installed

Finding Computers Without the Configuration Manager Client Installed If you’re trying to track down devices in Active Directory that have never had the Configuration Manager (SCCM) client pushed to them, or where the client install has failed silently, a WQL query against your discovery data is the quickest way to find them. The query below […]

SCCM Wql Query No Configmgr Client Installed

Finding Computers Without the Configuration Manager Client Installed

If you’re trying to track down devices in Active Directory that have never had the Configuration Manager (SCCM) client pushed to them, or where the client install has failed silently, a WQL query against your discovery data is the quickest way to find them. The query below returns every discovered resource where the client flag is either false or hasn’t been set at all:
select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Client = 0 or SMS_R_System.Client is null
To use it, open the Configuration Manager console, go to Monitoring > Queries, right-click and choose Create Query, then paste this into the query statement’s WQL editor (Edit Query Statement > Show Query Language). Bear in mind this only tells you what the site database has discovered — a device that was never picked up by an AD System or Network Discovery method won’t show up at all, so it’s worth cross-checking the result set against your full AD computer list if you suspect gaps in discovery itself.

Still Current on Configuration Manager 2603 (Updated for 2026)

This WQL query still runs unchanged against Configuration Manager 2603, the current branch release as of 2026 — the underlying SMS_R_System.Client flag and discovery data model haven’t changed. The manual WQL approach shown here remains more flexible than the built-in reporting views, since you can freely combine it with other SMS_R_System properties (OU, OS version, last logon) to narrow the result set further. Worth repeating the original caveat with extra emphasis: this only surfaces devices the site database already knows about. A machine that’s never been picked up by AD System Discovery or Network Discovery won’t appear in these results at all, so pair this query with a fresh AD computer export if you suspect discovery gaps rather than just missing client installs.

Resources

🛠️

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, Active Directory, PowerShell, and enterprise infrastructure.

He founded TechyGeeksHome in 2010 and has published over 1,500 practical guides covering real-world IT problems and solutions. When not solving IT problems,

Andrew develops free Windows utilities including Ultimate Settings Panel, which has been downloaded over 850,000 times.

3 thoughts on “SCCM WQL Query – No ConfigMgr Client Installed

Comments are closed.