Configuration Manager Client Version: Reporting on What’s Installed

Reporting on exactly which ConfigMgr client version your managed devices are running is useful before and after a site upgrade, to confirm a client update has actually rolled out fleet-wide rather than assuming it based on the deployment status alone. Find Machines on a Specific Client Version 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 […]

Configuration Manager Report Query For Client Version
Reporting on exactly which ConfigMgr client version your managed devices are running is useful before and after a site upgrade, to confirm a client update has actually rolled out fleet-wide rather than assuming it based on the deployment status alone.

Find Machines on a Specific Client Version

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.ClientVersion = "5.00.7804.1000"
Swap the version string for whichever build you’re checking for, and change = to < or > to find machines below or above a given version instead of an exact match — handy for finding everything that still needs the update.

Find Machines With No Client 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 is null
This second query is useful for finding AD-discovered machines that have never had the SCCM client installed at all, as distinct from machines running an outdated client version.

Finding Today’s Actual Baseline Version First

The 5.00.7804.1000 example above is from an old SCCM 2012-era build and shouldn’t be copied literally — current Configuration Manager (the rebranded, subscription-updated successor to SCCM) uses much higher version numbers that change with every monthly-cadence update. Rather than guessing the exact string, pull your site’s actual current client version straight from the console: Administration > Site Configuration > Sites shows the site’s current version, or check Monitoring > Client Status for a built-in breakdown of client versions already deployed across the hierarchy, which is often faster than writing a query at all if you just need a quick health snapshot rather than a targeted list of stragglers. It’s also worth pairing a version-based query like this with the built-in Client Check results (client health evaluation status), since a machine can be running the correct client version and still be functionally unhealthy — version alone doesn’t guarantee the client is actually communicating properly with the site.

Resources

🛠️

Gear We Recommend

A few general tech accessories worth having alongside this.

Browse our General Tech Accessories 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.