Hey folks, one of our Macs is showing as non compliant in Hexnode portal, but I can’t figure out why. Everything seems fine, the policies are applied, FileVault’s on, the OS is up to date, and the user is actively using the device. Any ideas?
21 Views
Replies (4)
Marked SolutionPending Review
Participant
Nov 16, 2025
Marked SolutionPending Review
Have you double checked the compliance policies? Sometimes there’s something misplaced there.
Marked SolutionPending Review
Participant
Nov 16, 2025
Marked SolutionPending Review
Yeah, I have checked them all. Everything looks good there too.
Marked SolutionPending Review
Hexnode Expert
Nov 16, 2025
Marked SolutionPending Review
Hi @remi, welcome to Hexnode Connect!
We looked into the case, and we think the non-compliant status could be due to the leftover data from the previous user being listed in the device’s action history. This can also sometimes get in the way of the current policies being applied correctly.
You can try the following steps to get it sorted:
- Open the Terminal app on the Mac that’s showing as non-compliant.
- Execute the following command to renew the device’s enrollment profile:
1sudo profiles renew -type enrollment
- Follow any prompts that appear.
- Once that’s done, go to Hexnode UEM console and trigger a Scan Device action by navigating to Manage > Devices > Scan Device.
Could you try this and let us know if it resolves the issue?
Regards,
Sienna Carter
Hexnode UEM
Marked SolutionPending Review
Participant
Nov 17, 2025
Marked SolutionPending Review
It worked! The device is now showing as compliant. Thanks a lot.
Save
