What's new 
Some of our Macs are showing as non-compliant against the Default macOS Compliance Policy in Hexnode. I’m not sure what exactly is failing. Is there a way to see whether it’s FileVault, passcode, OS version, or something else causing the non-compliance?
35 Views
Replies (3)
Marked SolutionPending Review
Hexnode Expert
4 weeks ago
Sep 04, 2026
Marked SolutionPending Review
Hi @gnishilda,
You can view the reason for compliance failure from the device details page.
Go to Manage > Devices, open the affected Mac, and check the Device Summary > Compliance Info section. If the device is marked non-compliant, the warning icon in this section should show the specific condition that failed, such as FileVault not being enabled, passcode requirements not being met, or another configured compliance rule.
If the device was recently remediated, run the Scan Device remote action once to refresh the latest device state in Hexnode. After the scan completes, check the Compliance Info section again.
Regards,
Sienna Carter
Hexnode UEM
Marked SolutionPending Review
Participant
4 weeks ago
Sep 04, 2026
Marked SolutionPending Review
I checked Compliance Info and the Mac seems to be compliant with FileVault and passcode. It still had a warning at first, though. Does that mean the compliance status was just not updated yet?
Marked SolutionPending Review
Hexnode Expert
4 weeks ago
Sep 04, 2026
Marked SolutionPending Review
Hi @gnishilda
This happens if the local device state has changed but the latest inventory or compliance data has not yet been refreshed in Hexnode.
If FileVault and passcode requirements are already satisfied, run Scan Device again and restart the Mac. Once the device comes back online and reports its updated status, the compliance state should be recalculated. In similar cases, the non-compliant warning clears after the scan and restart.
Regards,
Sienna Carter
Hexnode UEM
Save