Source System Ivanti EPMM and Neurons / MobileIron Core and Cloud

01. Introduction

There is a general documentation available for the EBF Onboarder, where you can find information about its prerequisites and the whole migration project. It describes how you can setup a migration project, how you can setup invitation emails and reminders which guide your users through the migration. It also tells you how to initiate the migration process and how to track the migration status.

This documentation complements the general EBF Onboarder documentation and provides more detailed information for the source system Ivanti EPMM and Neurons / MobileIron Core and Cloud.

ATTENTION: This documentation does not replace any Ivanti/MobileIron documentation. It is only describing prerequisites for the EBF Onboarder. Please consult the Ivanti/MobileIron documentation and support if necessary.

02. Prerequisites for the source system Ivanti EPMM / MobileIron Core

02.1. Service Account

You need to create an Admin Account in your source system which is dedicated to the EBF Onboarder. It must be assigned to Global Space and you must ensure that it has the API User role and all roles listed below in order to be able to migrate the devices.

Admin roles can be changed in your Ivanti/MobileIron Admin Portal by selecting the account in the tab ‘Admin’. Here click on ‘Actions’ >> ‘Edit Roles’.

Please also pay attention to chapter 02.2.2 regarding the /mifs access.

ATTENTION: Make sure that ‚Enforce single sessions’ is NOT selected for the EBF Onboarder account in ‘Other roles’ to allow the Ivanti/MobileIron environment to accept several attempts of communication with the same Admin Account coming from different migrations at the exact same time.

02.2. Network configurations

02.2.1. HTTPS port or redirected port

All API command connections from the Ivanti/MobileIron-Onboarder server are made on port 443. If you don’t use port 443, you have to make sure that the firewall rules on your site will allow the Onboarder server to access the port you have chosen to access your Ivanti/MobileIron server environment. Please also make sure, that the „Portal ACLs“ on the EPMM/Core will allow the API access.

NOTE: Please read the general documentation to learn more about the IP whitelisting.

02.2.2. Portal access

The Service Account for the EBF Onboarder needs to have access to the Admin Portal, User Portal and API commands and must be able to log into port https 443 by default. The Service Account with API user role also needs to be able to search users on the target MDM system.

ATTENTION: If you have disabled port 443 for security reasons and are using a different port, please make sure that your firewall rules allow the EBF Onboarder servers and gate systems to access your login portal (/mifs).

NOTE: Please read the general documentation to get the IP addresses which are associated to the MobileIron EBF Onboarder server and the gate.ebf.de.

02.2.3. Ivanti EPMM/MobileIron Core 11.7 Support: Force Retire

If the EPMM/Core version 11.6 or higher is running on your source system, a device can remain in the status “Retire Pending” if the retire command was not confirmed by the device. This will cause the migration to stop as the EBF Onboarder will only continue the migration if the retirement was confirmed at the source MDM system.

The status “Retire Pending” has been introduced to the Admin Portal with EPMM/Core version 11.6. With EPMM/Core version 11.7, the “Force Retire” command was added to allow to remove these devices without the confirmation of the device.

If you are running EPMM/Core version 11.6 or higher and want the EBF Onboarder to send out “Force Retire” commands to the devices right away, please take the following steps in the EBF Onboarder portal:

• Go to ‘Settings’ >> ‘Tenant Settings’.
• Set “Timeout (seconds) after unenrollment” to 46.
• Click on ‘Save Settings’. From now on the EBF Onboarder will send “Force Retire” commands to the devices.

02.2.4. Connected Cloud

If your Source MDM system is a Ivanti/MobileIron Connected Cloud (an EPMM/Core with domain mobileiron.net) and you experience that devices are only retired after opening the Mobile@Work app on the device, you should add two other permissions to the API-user:

Device Management > Force device check-in
Other Roles > Migration

02.3. User role

Make sure that the EBF Onboarder Service Account and all users that will be part of the migration project have access to the ‘User Portal’ by assigning the role ‘User Portal’.

03. Prerequisites for the source system Ivanti Neurons / MobileIron Cloud

03.1. Service Account

You need to create a Service Account in your source system which is dedicated to the EBF Onboarder. It must have the API User role and all roles listed below in order to be able to migrate the devices.

Admin roles can be changed in your Ivanti/Mobileiron Admin Portal by seleting the account in the tab ‘Users’. Here click on ‘Actions’ >>  ‘Append Roles’.

Please apply All Spaces to the user.

02.3. Device selection

You should create new manual or filter labels and add the users/devices chosen for migration to them. The labels should be created before setting up the project in the EBF Onboarder portal.

If you are migrating a lot of devices, it is recommended to create waves of 500 to 1000 devices.