Configuration Manager | Compliance state unknown

Unknown compliance generally ties to scan agent status. Are the devices in question receiving the update deployment assignments and installing updates or is that not working either?

Please verify the scan status of Scan 3 - Last Scan Status by Collection under Scan Deport, and determine whether all unknown devices have completed their scan and are reported as "Scan Completed"

1. Scan Status Verification:
   • Review the status of Scan 3 - Last Scan Status by Collection in the console.
   • Check if all devices categorized as "Unknown" have transitioned to a completed scan state.
2. Log Validation on Sample Clients:
   • Select a few client devices from the affected group.
   • Review the following logs for errors or scan-related issues:
     • ScanAgent.log
     • WUAHandler.log
   • Confirm whether the scan has been successfully completed or if any errors persist.
3. Force Update Compliance State (if scan is complete):
   • If the scan has been completed without errors, execute the following PowerShell commands on the client to manually trigger a compliance state update to the database:
   powershell Get-WmiObject -Namespace "root\CCM\StateMsg" -Query "select * from CCM_StateMsg where (TopicType = 300 or TopicType = 301) and TopicID =''" | Set-WmiInstance -Arguments @{MessageSent = $true} $UpdatesStore = New-Object -ComObject Microsoft.CCM.UpdatesStore $UpdatesStore.RefreshServerComplianceState()