Mac froze during migrationSolved

Participant
Discussion
2 months ago Feb 17, 2026

Hi everyone,

We’re doing a pilot migration of macOS devices from old MDM to Hexnode by pushing the Hexnode Migrator tool via old MDM.

One user got stuck. After fixing an initial “Device isn’t assigned to the MDM Server” error by assigning the device to Hexnode in Apple Business Manager (ABM), the Mac froze during the Google Workspace enrollment phase. The user couldn’t click “Next” or exit the screen, effectively bricking the device until we temporarily pushed a non-authenticated profile.

Two questions before we continue the rollout:

  1. How can we prevent users from being completely locked out if the enrollment screen hangs like this?
  2. Is it strictly required to reassign all these Mac devices to the Hexnode UEM server in ABM before using the Migrator tool?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 months ago Feb 17, 2026
Marked SolutionPending Review

Hello,

Thank you for reaching out to Hexnode Connect. Glad to have you onboard! Let’s get these issues sorted out directly so the rest of your rollout goes smoothly.

1. Preventing Enrollment Lockouts

To ensure users can back out if an authentication step hangs, you need to adjust your setup payload.

  • When configuring the Hexnode Migrator, ensure that you enable the Allow user to exit full screen option within the migrator configuration settings.
  • Checking this box ensures that if the UI hangs or network drops, the user can safely exit the setup screen rather than being locked into a frozen state.

Note on ABM Syncing: When you assign a new device to a new management server in ABM, it doesn’t always sync instantly. Always navigate to Admin > Apple Business Manager > Automated Device Enrollment and click Sync with ADE to refresh the list before the user attempts to log in.

2. ABM Reassignment Requirements

While technically dependent on your management goals, reassigning the devices in ABM prior to migration is highly recommended for corporate-owned Macs.

Here is why: when the Migrator tool strips the legacy MDM profile, the device needs to immediately recognize its new authoritative server. If it’s already assigned to Hexnode in ABM, the handoff is seamless. Furthermore, enrolling via ABM is the only way to mark the Hexnode management profile as non-removable, which ensures the device will automatically re-enroll even if a user performs a factory reset.

I hope this helps. If you need any assistance, please let me know.

Best regards,
George,
Hexnode UEM

Save