Policy not automatically applying to refurbished iPads enrolled via Apple Configurator and ABMSolved

Participant
Discussion
3 months ago Mar 04, 2026

Hey everyone. My team recently acquired a large batch of second-hand iPads for our warehouse staff. To get them managed, we are using Apple Configurator to add them to our Apple Business Manager (ABM) portal, and from there, assigning them to our Hexnode MDM Server.

Over in the Hexnode console, we have an ADE enrollment profile set up with our strict warehouse lockdown policy attached to it. Our expectation was that the moment the iPad enrolls, this policy gets automatically slapped onto the device. However, that isn’t happening consistently. Sometimes the profile just sits there and the policy doesn’t take effect unless we force a sync and completely factory reset the iPad again, which is a massive time sink for my deployment team.

Two questions: First, is there a way inside ABM to pre-select our specific Hexnode Enrollment Profile instead of it just hitting the default? Second, is there a way to avoid these secondary factory resets just to get the policy to apply properly? Any advice on smoothing out this workflow would be hugely appreciated!

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 months ago Mar 04, 2026
Marked SolutionPending Review

Hello,

Thanks for reaching out to Hexnode Connect.

Apple Business Manager does not have the option to pre-select a specific MDM enrollment profile. ABM simply points the device to your Hexnode MDM server. Hexnode then takes over during activation to assign the configured settings.

Regarding the policy application, the need for secondary factory resets occurs if the enrollment profile is modified after the payload has already been deployed, or if the devices are activated before a proper sync. When a profile status is Assigned, it is in a pending state. It changes to Pushed only after the device completes the Setup Assistant. Any subsequent changes to that enrollment profile will require a full factory reset to take effect.

The Solution:

To avoid these secondary resets and ensure policies apply seamlessly, we recommend utilizing Dynamic Device Groups instead of tying the policy directly to the ADE enrollment profile.

  1. Navigate to Manage > Device Groups in your Hexnode console.
  2. You can either use the pre-existing iOS Default Group (which automatically captures all enrolled iOS devices) or select Create Dynamic Group to build a custom group based on specific device criteria.
  3. Associate your warehouse lockdown policy directly to this Dynamic Group.

By using this method, the moment your iPads enroll into Hexnode, they will dynamically populate into the group and immediately receive the associated policies over the air, bypassing the need for additional factory resets.

I hope this helps. If you find any more issues or need further assistance feel free to reach out.

Best regards,
George,
Hexnode UEM

Save