Devices reporting as not compliant in SCCM/MECM

Bob Wilkerson 1 Reputation point
2021-11-03T19:05:35.34+00:00

This has been bugging me for a while. Since I updated my SCCM site server to 2107 I have devices that show as not compliant with the Anti-Malware policy and gives a very odd date of when it was last checked as 12/31/1969.

146199-sccm-not-compliant.png

There is not much to set on this compliance policy and I even recreated a new one to apply. If I remove the policy from being applied the devices show as compliant with the correct date and time.

Maybe this is something I am doing wrong but I am pretty positive this compliance policy worked before the update to 2107

Microsoft Configuration Manager
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rahul Jindal [MVP] 9,146 Reputation points MVP
    2021-11-04T07:15:50.45+00:00

    This is the first I have heard. But usual takers would be the health of the client after the site was upgraded. See if the updating the client fixes things or not.

    0 comments
  2. AllenLiu-MSFT 40,316 Reputation points Microsoft Vendor
    2021-11-04T07:56:08.487+00:00

    Hi, @Bob Wilkerson
    Thank you for posting in Microsoft Q&A forum.

    There is a new feature in SCCM 2107, an Audit option for potentially unwanted applications (PUA) was added in the Antimalware policy settings, you may check if you have configured related Antimalware policy setting:
    https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/whats-new-in-version-2107#audit-mode-for-potentially-unwanted-applications
    https://learn.microsoft.com/en-us/mem/configmgr/protect/deploy-use/endpoint-antimalware-policies#real-time-protection-settings

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.