Hello everyone,
I’m looking for the best way to move a managed account from one Mac to another. The user’s current Mac is broken, so we’re setting them up with a replacement.
Both Macs are already enrolled in Hexnode, and instead of manually copying files and settings, I’m planning to use Apple’s Migration Assistant to transfer the user account, apps, and data to the new machine.
Has anyone done this before? Is there anything special I should keep in mind when moving a managed account this way?
18 Views
Oh, that’s actually a good idea. I’ve been wondering about something similar as well. We might have to replace a few Macs soon, so I’m curious how this works.
Are you planning to move everything using Hexnode, or just use Apple’s Migration Assistant for the transfer?
No, not through Hexnode.
Both devices are already managed. I just want to use Apple’s Migration Assistant to move the user account and its data from the old Mac to the new one.
Hi @eduardo ,
Before we go further, could you share how the Macs were enrolled?
Best Regards,
Isabel Lora
Hexnode UEM
The Macs were enrolled through ABM using ADE.
In that case, using Migration Assistant should work fine for transferring the managed account and its data.
Since the new Mac is already managed with Hexnode UEM, it’s best to disenroll the device and remove the existing Hexnode profiles before starting the migration. This helps avoid conflicts after the migration. Once the migration is complete, run the following command in Terminal on the new Mac:
|
1 |
sudo profiles renew -type enrollment |
This command makes the Mac check in again with Apple’s enrollment servers. After that, a prompt will appear asking the user to allow device management. Once they approve it, the Mac reconnects to the Hexnode UEM portal and starts receiving policies normally.
If you have any further queries, feel free to contact us.
Best Regards,
Isabel Lora
Hexnode UEM
But why should we need to run that command after the migration? Doesn’t the new Mac automatically stay connected to Hexnode since it’s already enrolled?
Hi @desmond ,
When you run the migration, the user account and its data are transferred to the new Mac. The profiles, policies, and restrictions that were previously pushed through Hexnode UEM can also come over during the migration.
However, the new Mac has a different hardware identity (serial number). Because of this, it won’t automatically establish itself as the same managed device in the Hexnode UEM portal.
Running the command mentioned earlier simply helps the new Mac re-establish the management link after the migration is complete.
Best Regards,
Isabel Lora
Hexnode UEM
Don't have an account? Sign up
