Mac device suddenly showing as non-compliant, profiles missingSolved

Hi there,

Thanks for posting this on Hexnode Connect. We understand why this would be concerning, especially when the device still appears enrolled but suddenly shows as non compliant on the Hexnode UEM app.

To clarify first, any device in Hexnode does not typically become non compliant and lose all configuration profiles purely due to an OS update. A macOS device typically shifts to a non-compliant state only when it violates one or more rules defined in a compliance policy. This behavior is unusual.

The first thing to verify is whether the device was disenrolled. If so, all profiles will be automatically removed from the device. In this situation, we recommend contacting your IT administrator to see if they can still establish a connection. If the connection is lost, they can mark the device as disenrolled and re-enroll it.

If disenrollment is ruled out, ask your IT administrator to check the following:

• Action history to confirm whether any policy removal or device level action was triggered.
• Device status and last check in time to ensure the device is actively communicating with the server.
• Group association to verify whether the device is still part of the user or device groups through which policies and configuration profiles were applied. If the device moved out of a group, the associated profiles would be removed from the device.
• Review the device details page in the console to identify which specific compliance rule is causing the device to be marked as non-compliant.

We recommend reviewing these points to identify the exact cause. If the issue continues, please reach out to support@hexnode.com so our team can take a closer look.

If you have any further updates or observations, feel free to share them here on Hexnode Connect. We would be glad to help.

Best regards,
George
Hexnode UEM