Hi @aurora,
This can be expected behavior for a Mac that was disenrolled while it was offline.
When a device is disenrolled from Hexnode, there are two separate parts to the process:
1. The device is marked as disenrolled in the Hexnode portal. This removes it from the active device inventory under Manage > Endpoints and prevents it from continuing to consume an active license.
2. The MDM profile and Hexnode management components are removed from the device itself. This part requires the device to come online and receive the disenrollment command.
If the Mac was powered off or disconnected from the internet when the disenroll action was initiated, the portal can show the device as disenrolled, while the actual removal on the Mac completes only when it reconnects later.
In this case, the recent activity such as “MDM agent removed from device” indicates that the Mac came online and processed the pending disenrollment. The compliance notification was triggered because the device checked in during that process. It does not mean the Mac has been re-enrolled.
Regards,
Sienna Carter
Hexnode UEM