Mac Enrollment URL installation stalled or failed without an error codeSolved

Participant
Discussion
2 days ago Jul 24, 2026

A couple of Macs enrolled through the Enrollment URL took several hours before Hexnode finished installing. One of them failed at first without showing any error code, but after retrying the installation a few times it eventually went through and the device status changed to Success.

Is there any way to check what caused the delay or see when the connection synced again?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
2 days ago Jul 24, 2026
Marked SolutionPending Review

Hi @ed_evans,

This can happen when there is a temporary communication delay between the MDM server and Apple Push Notification service during macOS enrollment.

When a Mac is enrolled through the Enrollment URL, Hexnode relies on Apple push notifications to wake the device and process pending MDM commands. If that communication is delayed, installation commands may remain pending, take longer than expected, or fail without returning a specific error code. Once the connection is restored and the device checks in again, the queued commands are processed and the Hexnode portal updates the device status to Success.

If the installation eventually completes and the device shows as successfully enrolled, it usually indicates that the issue was a temporary sync delay rather than a failed policy, app, or enrollment configuration.

Best Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
2 days ago Jul 24, 2026
Marked SolutionPending Review

So there isn’t a log in the portal that shows something like “connection resynced” or the exact point where Apple push started working again?

Marked SolutionPending Review
Hexnode Expert
2 days ago Jul 24, 2026
Marked SolutionPending Review

Specific connection resync logs are not shown in the Hexnode portal for this type of temporary sync delay. Since it is not treated as an application installation failure or policy execution failure, the portal does not generate a separate resync event log.

The practical indicators are the device checking in again, the pending commands getting processed, and the device status moving to Success. If the same behavior repeats or a Mac remains stuck for an unusually long time, it is best to review the enrollment status at that time and investigate it while the device is still affected.

Best Regards,
Isabel Lora
Hexnode UEM

Save