Skip to content

Prerequisites for Workspace ONE 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

If your current EMM is a Workspace ONE environment, you need to also follow the instructions below. It will differ depending on the OS of your targeted devices, so please refer to the corresponding section.

For iOS devices

You need to add the Exodus companion app from the AppStore to your source EMM’s app catalog via: Apps & Books › Applications › Native › Public › Add Application.

  • Set the Platform to Apple iOS, select Search App Store and set Exodus Companion in the Name field (see fig. 4.1)

figure 4.1

Create iOS App

  • Click Next and select the correct app in the list (see fig. 4.2)

figure 4.2

Select App in App Store

  • In the next screen, click Save & Assign
  • Then click Add assignment and fill the form to match the screenshot below, replacing the Configuration Value value of the server-url Configuration Key with the name of your Exodus instance followed by -api.exodus.tools URL (e.g. for an instance named 'example', you should set 'https://example-api.exodus.tools/') (see fig. 4.3)

figure 4.3

iOS App Assignment Screenshot

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

For Mac computers, you need to distribute the macOS Exodus Companion App through your EMM. Download the app from our distribution platform, load it in your catalog, and push it to your fleet, as you usually do for your Mac apps.

Important

Please make sure that the macOS companion's version is compatible with your instance version by checking our Support Matrix.

Before your users can start the migration from their computers, you need to perform one last step, which is adding a profile to your Workspace ONE instance that should be deployed to all migrating Mac computers.

  • In your Workspace ONE dashboard, on the left menu, click on Devices › Profiles & Resources › Profiles, then click on the Add button above the list of profiles (see fig. 4.4).

figure 4.4

Custom Profile Upload

  • Select Add Profile, then click on the macOS section, then Device Profile.
  • Scroll all the way down the list on the left, to select the Custom Settings option.
  • Click on the Configure button.
  • In the text field that appeared, enter the following configuration payload, and replace $INSTANCE by your instance name (see fig. 4.5):
<dict>
    <key>PayloadDescription</key>
    <string>Configures Exodus Companion app</string>
    <key>PayloadDisplayName</key>
    <string>Exodus Companion</string>
    <key>PayloadIdentifier</key>
    <string>io.h2g.exodus-macos.428F1E79-CD88-4CD4-AE26-1F674DD1268B</string>
    <key>PayloadType</key>
    <string>io.h2g.exodus-macos</string>
    <key>PayloadUUID</key>
    <string>428F1E79-CD88-4CD4-AE26-1F674DD1268B</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
    <key>server-url</key>
    <string>https://$INSTANCE-api.exodus.tools</string>
</dict>

Important

Please note that the only information you need to customize in this payload is the server URL contained in between the <string></string> tags associated to the key server-url. You just have to replace $INSTANCE with the name of your Exodus instance. (e.g. for an instance named 'example', the whole string contained between the tags would be 'https://example-api.exodus.tools')

figure 4.5

Custom Profile Settings

  • Then click Save › Continue.
  • You can now narrow to which devices the profile will be deployed, for instance by choosing a Smart Group. Once done, click on Save and Publish › Publish, your profile will be pushed to the devices.