Compliance Policy troublestooting

Copper Contributor


I have created a custom compliance policy to check whether third-party antivirus software is installed and deployed it to some test devices. This device group includes 35 devices, all of which are running either Windows 11 or Windows 10 22H2. However, 10 out of the 35 devices show the status as "not applicable."

I would like to know how to troubleshoot this issue on the client side. Specifically, when I assign a compliance policy to a device, what happens first, and which logs or events can show that this policy has been received?



1 Reply
The IME log and the registry would be the first locations to start looking... just like I am mentioning in this blog