iOS MDM profile downloads but installation failsSolved

Participant
Discussion
1 month ago Sep 24, 2026

One of our iPhones is failing during Hexnode MDM enrollment. The MDM profile downloads successfully in Safari, but when the user tries to install it, iOS shows “Profile Installation Failed – An unknown error occurred.”

Other iPhones are enrolling fine, including an identical model enrolled the same day. For this affected iPhone, we already checked:

  1. iPhone enrollment is enabled in Hexnode enrollment restrictions
  2. No old MDM or configuration profiles are present under VPN & Device Management
  3. Safari was used to download the profile
  4. Date and time are correct
  5. Tested on two different networks
  6. Stolen Device Protection was disabled
  7. Tried installing through the Hexnode UEM app as well, but the same error appeared

Has anyone seen this where only one iPhone fails even though the profile downloads correctly?

Replies (2)

Marked SolutionPending Review
Hexnode Expert
1 month ago Sep 24, 2026
Marked SolutionPending Review

Hello @margaret ,

Since you have already verified the network, date/time, and ensured there are no conflicting profiles, the issue is likely isolated to a hidden iOS enrollment state on that specific device failing the Device Enrollment Challenge. Disabling Stolen Device Protection helps rule out security prompt delays, but it generally will not fix a core payload rejection like this.

To isolate and resolve this device-specific error, try these next steps:

  • Temporarily set your enrollment settings to require no authentication. This rules out any underlying credential or user-assignment conflicts causing the failure..
  • If the device is expected to use Automated Device Enrollment, confirm that it is present in Apple Business and assigned to the Hexnode MDM server.
  • If possible, erase the iPhone and attempt a fresh enrollment. A factory reset can clear local iOS enrollment state that is not visible under VPN & Device Management.

If wiping the device is not practical, swapping to another device is a valid workaround. To fix that specific iPhone without wiping it, a deeper investigation would require capturing device-side diagnostic logs via Apple Configurator while reproducing the failure.

Regards,
Simon Scott
Hexnode UEM

Marked SolutionPending Review
Participant
1 month ago Sep 24, 2026
Marked SolutionPending Review

We ended up using another iPhone for the user because wiping the active device was not an option. The replacement enrolled normally, so this does look isolated to that particular device.

Save