Prerequisites for MobileIron Cloud as Source
Required environment’s information
You need to first setup all general prerequisites before proceeding to this guide.
Get the Exodus Companion App on your devices
This setup needs to be done in your Source Tenant and will differ depending on the OS of your targeted devices.
For iOS devices
Installing an app on your device fleet is broken down in 5 steps: Choose, Describe, Delegate, Distribute, and Configure.
Step 1: Choose app
You need to add the Exodus companion app from the AppStore to your source EMM’s app catalog via: Apps › + Add. Make sure the iOS Store option is selected, then add the app by entering its name, Exodus companion
in the search field (see Fig. 1.1 and 1.2).
Figure 1.1
Figure 1.2
Steps 2: Describe and Step 3: Delegate
You can optionally add an additional description that your users will see, and delegate installation of this app to other spaces.
Step 4: Distribute
Distribute allows you to target some custom groups, users, or your whole mobile fleet. Configuring this will depend on your organization's needs and migration process.
Step 5: Configure
Important
This is an important step, required for the Exodus workflow to handle your migration.
Three aspects must be configured: (see Fig 1.3)
- Install Application configuration settings
- iOS Application Management configuration settings
- iOS Managed App Configuration
Figure 1.3
1. Installation settings
Click on the Install Application configuration settings.
- Check Install on Device: this will prompt users of unsupervised devices with an alert to install the app. For supervised devices, the app will be pushed silently.
- Check Enable MDM App Auto-Updates in order to push the latest version on each update.
- Finally, check Convert to Managed App as well. If a user has installed the app directly from the App Store, this will allow the system to "convert" it into a managed app, which is a requirement for the Exodus companion app.
Figure 1.4
2. Application management
Click on iOS Application Management configuration settings.
Make sure the Remove apps on un-enrollment checkbox is unchecked, to ensure the companion can continue managing the reenrollment in your target EMM after retiring it from your MobileIron Cloud source server.
Figure 1.5
3. Remote App Configuration
Click on the + button on the right of the iOS Managed App Configuration section. Please make sure to select this section and not the App Connect one, which has a similar name.
Give a name to this configuration, and add two key/value pairs with the + Add button to create two values entries. Then fill them with the following:
- The server URL for the
server-url
key. This URL needs to behttps://#your-instance-name#-api.exodus.tools
(assuming you access your Exodus console throughhttps://#your-instance-name#.exodus.tools
). - A specific value for the
serial-number
key:${deviceSN}
.
Important
Don't forget to replace #your-instance-name#
by your real instance name which should be equal to the subdomain of your Exodus console URL.
If you access Exodus admin console with https://example.exodus.tools/
then the server url should be https://example-api.exodus.tools
.
Figure 1.6
For Android devices
For Android devices, nothing needs to be done. Each user will install the companion app themselves by following a dynamic link sent to them via an email by the Exodus server when the migration will start.
Work profile
For Work Profile, it's strongly recommended to approve the Exodus companion application from your Google Play Enterprise Account.
Note
The Exodus companion application must be installed outside the Work Profile container.
But if a user tries to start their migration inside the Work Profile container, with an approved application, we can help them follow the migration steps.
Otherwise, they will be redirected to an empty page on the Play Store.
For Mac computers
Migration of Mac computers from MobileIron Cloud is not supported in Exodus.