Re-enrolling wiped Abm iPads in hexnode after they show as disenrolledSolved

Hi @penelope,

When an iPad is wiped, the existing MDM management profile is removed from the device. This breaks the active management connection, so the device will naturally appear as disenrolled in Hexnode until it goes through the enrollment process again.

Since the devices are registered in Apple Business and assigned to Hexnode, they can simply be re-enrolled through Automated Device Enrollment (ADE) during the Setup Assistant.

Here is the recommended flow for the users receiving them:

1. Power on the iPad and proceed from the language selection screen.
2. Connect the device to Wi-Fi or another available internet connection.
3. Continue through the Setup Assistant until the Remote Management screen appears.
4. Select Enroll.
5. The assigned user can then sign in with their Microsoft credentials.
6. After successful authentication, the device will enroll back into Hexnode and appear under your Manage tab.

Once the device checks in, any policies and apps associated with the enrollment profile or assigned to the user/device will deploy automatically.

Please let me know if you run into any issues once the users start setting them up!

Best regards,
Eden Pierce
Hexnode UEM

So it is completely okay to just leave the iPads at the setup screen and let the new users finish the Remote management step with their own microsoft login?

Hi @penelope, 

Yes, absolutely! If user authentication is part of your ADE enrollment flow, it is actually best practice for the end user to complete that step using their own Microsoft credentials. This ensures the device is correctly associated with them. 

Before shipping, just verify that the devices are still assigned to Hexnode in Apple Business and that the ADE enrollment profile is successfully assigned to them in the Hexnode UEM portal. The users will just need internet access during setup to complete the process. 

Please let me know if you run into any issues during their deployments! 

Best regards, 
Eden Pierce 
Hexnode UEM 

That clears it up. I was worried that the disenrolled status meant something was wrong with the ABM assignment, but it sounds like it is expected after a wipe. Thanks for the help!