Configuration Manager: WQL Query to find the machines based on Deployment Status

WQL Query to find the machines falls under unknown tab for any application or software update deployments:

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

Join SMS_SUMDeploymentAssetDetails D

On SMS_R_System.resourceID = D.resourceID

Where D.assignmentID = '<Assignment ID>' and D.StatusType = '<Status No>'

To 'Assignment ID', Open Configuration Manager Console > Monitoring > Overview > Deployment > Select and right click the deployment and tick the Assignment ID

Once you selected Assignment ID, a column will be added like below then copy the ID for your query:

And for machine status, below are the values for the respective status (Screenshot from Microsoft Document - SMS_SUMDeploymentAssetDetails Server WMI Class):

For example for Unknown machines:

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

Join SMS_SUMDeploymentAssetDetails D

On SMS_R_System.resourceID = D.resourceID

Where D.assignmentID = '16779116' and D.StatusType = '4'

Configuration Manager: How to force the machine to send DDR, Location Request, MP, and compliance report

To force any windows machine/computer's client agent to trigger sending DDR, Location Request, MP, and compliance report to Configuration Manager, please use the below command and run as administrator:

([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000012}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000024}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000111}'); [wmi]"ROOT\ccm\invagt:InventoryActionStatus.InventoryActionID='{00000000-0000-0000-0000-000000000003}'" | remove-wmiobject ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000003}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000021}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000022}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000040}') | out-null; "Eval. MachinePolicy"; [void]([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000113}'); ([wmiclass]'ROOT\ccm:SMS_Client').TriggerSchedule('{00000000-0000-0000-0000-000000000108}'); "Update scan and evaluation" (New-Object -ComObject Microsoft.CCM.UpdatesStore).RefreshServerComplianceState()

Configuration Manager: Client Status and Categories

You might have came across below four client check categories during application or software update deployments - Unknown in Configuration Manager:

• Client check failed/Active
• Client check failed/Inactive
• Client check passed/Active
• Client check passed/Inactive

In this post, we'll see what these categories really implies. The distinction between Active and Inactive machines are an arbitrary date limit (by default, 7 days) for when it talked to Configuration Manager final. So the machines falls beneath "Client check passed/Inactive" implies the final commination with ConfigMgr, the client check was great, but haven't listened anything in at least 7 days.

Active implies the client has communicated with Configuration Manager since the limit. For case, in the event that the limit is set at the default of 7 days and a client communicated with the server 5 days prior, it would appear up as "Active" within the console.

You can change the limit in the Monitoring workspace by right clicking on Client Activity:

Client Status Settings window looks like below screenshot:

Client status update can be scheduled by right clicking on Client Activity:

Statistics of Click Status:

    Statistics dashboard in the client status will give you the detailed view of clients which are active/inactive:

Below are few examples of client check failures: