iOS device stuck on “Scanning in progress” after Apple Configurator/ADE enrollmentSolved

Participant
Discussion
8 hours ago Jun 29, 2026

I have a couple of supervised iOS devices that suddenly stopped responding to MDM actions. One iPad stays on “Scanning in progress” for a long time and does not load profiles or policies. Another iPhone has an app uninstall command stuck in “Pending”.

The certificates are valid, the devices are on different networks, date/time is correct, and Location Services is enabled. Restarting the devices and switching networks did not change anything. One of the affected devices was added using Apple Configurator and assigned through Apple Business Manager.

Is this usually a server-side issue, or can this happen if the enrollment did not complete properly?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 hours ago Jun 29, 2026
Marked SolutionPending Review

This behavior usually means that the over-the-air MDM commands are not reaching the device or the device is not responding to them.

For iOS/iPadOS devices enrolled through Apple Business Manager or Apple Configurator, check whether the device completed the Apple Setup Assistant flow after being assigned to the MDM server. The important step is the Remote Management screen. If the device record appears in Hexnode but the device skipped or did not complete the Remote Management step, Hexnode may show the device as enrolled, but policies, profiles, scans, app installs, and app removals can remain stuck in states such as “Scanning in progress”, “In progress”, or “Pending”.

Recommended checks:

1. Restart the affected device.

2. Connect it to a different stable network.

3. Confirm that date and time are correct.

4. Ensure Location Services is enabled if automatic time zone detection is being used.

5. If the device was added using Apple Configurator, erase the device and enroll it again.

6. During setup, make sure the device reaches and completes the Remote Management screen.

If another iOS device enrolls and syncs successfully from the same portal, the issue is more likely with the affected device’s enrollment state rather than a general Hexnode service issue.

Regards,
Mary Romero

Save