Skip to content

Commit 2a45170

Browse files
Update backup-restore-ios.md
updating information for ADE re-enroll to the same device
1 parent 13f70c1 commit 2a45170

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

memdocs/intune/enrollment/backup-restore-ios.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,8 @@ While it links files and documents, it doesn't typically restore any user data a
6969
### Specific to backup/restore
7070

7171
- In most cases, your MDM enrollment state (at the time of backup) isn't of any special significance. However, in a migration scenario where you are moving from one MDM vendor to another, it is important to be aware of.
72-
- When restoring a backup, taken while enrolled in MDM vendor A and restoring it on the same device but attempting to enroll in Intune, this will result in failure. The restore will be successful (no errors) as explained above, however since the management profile from MDM vendor A has been restored, the device isn't under management by Intune. Attempting to manually enroll the device using the Company Portal app will result in an error when trying to install the new Intune management profile "The new MDM payload doesn't match the old payload". To remediate this error, you would need to remove the existing management profile belonging to MDM vendor A and then re-enroll into Intune using Company Portal. Migrating from one Intune tenant to another Intune tenant would exhibit the same behavior.
72+
- When restoring a backup, taken while enrolled in MDM vendor A and restoring it on the same device but attempting to enroll in Intune, this will result in failure. The restore will be successful (no errors) as explained above, however since the management profile from MDM vendor A has been restored, the device isn't under management by Intune. Attempting to manually enroll the device using the Company Portal app will result in an error when trying to install the new Intune management profile "The new MDM payload doesn't match the old payload". To remediate this error, you would need to remove the existing management profile belonging to MDM vendor A and then re-enroll into Intune using Company Portal. Migrating from one Intune tenant to another Intune tenant would exhibit the same behavior.
73+
- To correctly and fully re-enroll an ADE device, a factory reset is required, and the device cannot be restored from its own backup (otherwise the ADE configuration and profiles in the backup will be applied).
7374

7475
### Migrating without wiping the device
7576

@@ -88,4 +89,4 @@ There is an additional migration scenario to consider, which should not be impac
8889
8990
## Next steps
9091

91-
[Learn more about Automated Device Enrollment](device-enrollment-program-enroll-ios.md).
92+
[Learn more about Automated Device Enrollment](device-enrollment-program-enroll-ios.md).

0 commit comments

Comments
 (0)