I have a Mac that’s currently enrolled in Hexnode, but it recently changed to non-compliant in our environment after an OS update. On the device itself:
- It still appears enrolled
- The Sync action doesn’t seem to change anything
- All of the configuration profiles that used to be there are now missing
I’m not an admin on our Hexnode console, so I can’t see the device record, compliance policies, or logs directly. I’ve already reached out to Hexnode support, but while that’s in motion, I wanted to ask this community:
- Have you seen a case where an enrolled Mac goes non-compliant and drops profiles but still looks enrolled on the device?
- From the admin side of the console, what should I ask our IT administrator to check (e.g., device status, last check-in, policy changes, profile push failures, etc.)?
- Are there any common misconfigurations or recent Hexnode changes that might cause this behavior, specifically on macOS?
23 Views
