Migrate DEP devices from a source server

You can migrate

iOS

devices that are enrolled in the

Apple

Device Enrollment Program (DEP) from a source

UEM

server to a destination

UEM

server. Complete the additional tasks detailed below to support the migration of DEP devices. After completing the steps below, DEP devices with the

BlackBerry UEM Client

and the

MDM controls

activation type can be migrated using the

UEM

management console. DEP devices without the

UEM Client

or with other activation types instead require a factory reset and reactivation on the destination server.

Note that the DEP enrollment configuration is not migrated and the devices will lose the enrollment configuration settings in the destination environment.

In the management console, on the menu bar, click

Apps

. Search for and click the

UEM Client

. On the

iOS

tab, clear the

Remove the app from the device when the device is removed from BlackBerry UEM

check box. If you try to migrate devices without clearing this option, the

UEM Client

is removed and the device may be unenrolled from

UEM

In the DEP portal, create a new virtual MDM server.

Connect the destination

UEM

instance to the new virtual MDM server. For instructions, see Configure BlackBerry UEM for DEP.

Verify that the DEP profile of the destination

UEM

server matches the DEP profile of the source server.

Move the DEP devices from the source virtual MDM server to the new virtual MDM server.

Do any of the following:

For DEP devices with the

UEM Client

and the

MDM controls

activation type, use the UEM management console to migrate the devices to the destination server.

For DEP devices without the

UEM Client

or with other activation types, perform a factory reset of each device and reactivate the device on the destination server.

For DEP devices with the

UEM Client

and the

MDM controls

activation type, instruct users to open the app that is configured as the authentication delegate. This will trigger the migration on the device.