Hello @liam_t ,
Yes, that behavior usually points to a split between the Hexnode UEM Agent and the macOS MDM management profile.
The Hexnode Agent may still show the device as enrolled and may be able to perform agent-based actions such as reporting location. However, device management actions that depend on the macOS MDM profile can fail if the management profile is missing, expired, or no longer trusted by macOS.
A few checks and recovery steps:
- On the Mac, check whether the Hexnode MDM profile is present under System Settings/System Preferences > Profiles or Device Management.
- If the profile is missing, try renewing enrollment from Terminal: sudo profiles renew -type enrollment
- If the device is not assigned through Apple Business Manager and the renew command does not restore the profile, manually reinstall the MDM profile using macOS open enrollment:
- In Hexnode UEM, go to Enroll > Platform-Specific > macOS > Email or SMS > Switch to Open Enrollment.
- Open the enrollment URL on the affected Mac.
- Download the MDM profile.
- Open the downloaded profile and install it with local administrator approval.
On older macOS versions, the Profiles pane may not open automatically. In that case, open Finder > Downloads, locate the downloaded profile, and double-click it. This should open the Profiles section so the downloaded Hexnode profile can be installed.
Once the profile is installed successfully, the device should check in again and manual Sync from the Hexnode app should succeed.
Regards,
Simon scott
Hexnode UEM