Skip to content

What's new?

Exodus 1.13

Jamf Pro as Source & Target πŸ“±

We are thrilled to announce the full support of a new EMM both as Source AND Target: Jamf Pro!!! You can now migrate your iOS devices from and to Jamf Pro.

Fixes

  • Remove the Intune Group ID requirement in the Target configuration page
  • Extended MobileIron Connected Cloud support
  • Update EMM configuration requirements to use hostname instead of URL

Exodus 1.12

Adding Admin authentication by certificate for Workspace ONE πŸ”‘

When you create a Migration from and to Workspace ONE, you can now authenticate with a certificate. This is the preferred option going forward as certificates are more resilient compared to admin accounts with a password lifecycle of 30 days. No more "WARNING: EMM credentials error" in your mailbox, you can be sure your Migrations run forever!

Welcome to you Viewers πŸ”­

We are introducing a new Exodus Console role: Viewer. A Viewer only user will be able to navigate the Exodus Console, check the ongoing Migrations and generate Exports but will not be able to create any Migrations, modify or delete any existing ones or trigger any Device Actions. It's the perfect role for someone that is just here to monitor and report on the project progress and when you want to make sure there is no misclick or mistake done.

Fixes

  • PostegreSQL improvements and bug fixes.

Exodus 1.11

Expanded MobileIron support βš™οΈ

To all our MobileIron users!: You can now leverage device groups when you create a Migration from MobileIron Cloud and labels for MobileIron Core. This should give you more flexibility in shaping your Device List and help you move beyond the space device structure.

In-depth Exports πŸ“Š

Exports now record device transitory states. You can now see when a device has changed status and for how long it has stayed in that same state. This will give you a better visibility in your devices journey.

Fixes

  • On demand: we can now disable all user email notifications, this is instance wide (don't forget Android use cases requires these emails).
  • Improved device statuses and their tooltips.

Exodus 1.10

Device deletion ❌

You can now delete one or any filtered devices from an ongoing Migration. It will help you all trim your Device List and do a bit of house cleaning prior to trigger your device migrations. Note that a deleted device in transit will see his assigned Token released.

Fixes

  • Improved duplicate device management.

Exodus 1.9

Going forward, iOS email templates will include a Dynamic Link like the one available in the Android template. This is great for the iOS edge cases where the Companion App has been deployed but not configured with App Config or if the user has downloaded the Exodus Companion App himself from the App Store. The uniquely generated Dynamic Link will automatically configure when the user tap on the link. No more lost users, everyone is sure to migrate.

Full VPP Support πŸ“²

Going forward, you will be able to leverage any form of licence assignment in the VPP program. It means that you now can deploy the Companion App without triggering or requiring an authentication from your end-user.

Migrations export πŸ“Š

If you need to track your devices in transit and monitor the state of your Migrations from outside the Exodus Console, you can Export the Device List in each Migrations or directly from the Dashboard.

Fixes

  • Device Serial Numbers are now displayed in the Device List.
  • Enable resend email notification as a bulk action.
  • Modified enrollment token generation for better iOS device enrollment in Workspace ONE.
  • Extended user lookup in Intune to match email field if UPN does not match.
  • Changes in the API call structure to reduce global amount of requests.
  • For "Light" mode: allow device to transition from unenrolled to enrolled when re-enrollment happen outside of Exodus Companion.

Exodus 1.8

SOTI MobiControl as source βœ…

Introducing SOTI MobiControl in the Exodus EMM portfolio starting with MobiControl as a Source! You can now migrate your device fleet from MobiControl.

Companion App Notifications πŸ“±

Introducing a new way to reach out to your users and help them re-engage with their device migration: Notifications are now available as a Device Action in your device list. These notifications are also independently scheduled to ensure users engagement.

Fixes

  • Improve Companion App detection to speed up migration initiation.

Exodus 1.7

Device action: Resend start migration email πŸ“¬

Introducing a new device action allowing you to notify by email any of your users individually. It is relevant for users that might have missed the original notification and it is particularly important for Android devices which require the provided link to install and configure the Exodus Companion App.

Migration Credentials Renewal: Notification email ⚠️

Following last month’s new feature which helps update any expired credentials during a migration, we further improve it by sending a notification email to all the instance’s admins so they can act on it as soon as possible.

Fixes

  • Improve the way we retrieve the iOS enrollment profile on WorkspaceOne.
  • Update documentation with Device Actions section in Console Guide page.

Exodus 1.6

Introducing Exodus β€œLight” Mode πŸ’«

As we are adding EMMs in our portfolio as fast as possible, we sometimes face technical challenges that prevent us from providing a complete end-to-end experience.

Without the appropriate APIs and documentation, we can get stuck at the device re-enrollment, the user authentication or the device assignment step.

To support these scenarios we have developed an Exodus β€œLight” mode (compared to the standard β€œFull” Exodus re-enrollment process) which leverage the Target EMM Agent App to finalise the migration.

Despite having the end-user to authenticate with the Target EMM Agent App, the Exodus Console is still able to track and report the status of the device The Exodus Companion App stays as a guide for the end-user to walk him through the process and ensure he always has a place to come back to finish it.

Microsoft Intune As Target βœ…

Introducing the first EMM to leverage the Exodus β€œLight” mode: Intune as Target. You can now migrate your device fleet to Intune.

Migration Credentials Renewal πŸ”„

To ensure there is no interruption during a Migration, we have added the ability to renew the credentials used by both the Source and Target EMM. This action can be done proactively (before credentials expiration) or reactively (after credentials expiration).

If a Migration fails due to a credentials issue, the Migration is displayed with a red halo in the Exodus Dashboard and the Credentials button becomes Red in the Migration panel.

Fixes

  • Improve serial number management for Android devices on MobileIron Cloud.

Exodus 1.5

Microsoft Intune as Source πŸŽ‰

Introducing Intune in the Exodus EMM portfolio starting with Intune as a Source! You can now migrate your device fleet from Intune to WSOne.

New Tokens Allocation 🧐

Now that we provide more flexibility within a Migration, it makes sense to do the same for Tokens allocation. Tokens are now allocated at the Device level: a Token is reserved only when a device initiate its migration. No more limitation in the number of concomitant Migrations due to your Token Pool.

Extras

  • Improved Android Enterprise scenario: Work Profile to Work Profile migration process to mitigate AE containerisation.

Fixes

  • Admin console: Fix grayed out filters on Safari after the loading indicator appeared on device list.
  • Admin console: Refresh migration and device list after starting a device using "Start all ready devices" button or device actions.

Exodus 1.4

Device action: Start migration πŸ‘

Introducing device level migration for more granularity and flexibility! You can now initiate the migration of a single device or a set of filtered devices. The other devices will just sit there waiting for their turn.

Smarter Start Migration 🧐

The Start Migration button just got a little bit smarter: it now initiates the migration of all devices in the Ready status. Once new devices become Ready, just click the button again to initiate their migrations. All of this within a single button.

Fixes

  • Improved re-enrollment workflow when resuming.
  • Better Token duplicate management.

Exodus 1.3

Support for macOS

On top of iOS and Android, we are adding the support for a new system: macOS πŸš€ You can now migrate your Macs from Workspace ONE to Workspace ONE.

Device List filtering πŸ’ͺ

You can now apply various filters to your device list. This should give everyone more visibility and control over ongoing migrations. It is fair to say that this feature is the foundation of upcoming improvements...

Extras

  • Device Status naming scheme has been updated to facilitate impending changes.

Fixes

  • Logout automatically on invalid authentication.
  • Forgot password link does not reload the entire page.
  • Color of DEP sync and download buttons.

Exodus 1.2

Support of MobileIron Cloud as source

You can now migrate your devices from MobileIron Cloud with Exodus πŸ‘.

New Device Battery Threshold

We have changed the battery minimum threshold on both Android and iOS to better reflect actual use cases. See updated Support Matrix.

Extras

  • You can now reset your account password.
  • Exodus Terms of Service must be accepted at first login prior to accessing the service.

Fixes

  • Workaround to prevent enterprise wipe failure when using Workspace ONE < 9.5 as source. (Documented API Bug).
  • Add support for uninstalling Exodus Companion App on Android 8.0+.

Exodus 1.1

Support of MobileIron Core as source

Now you can migrate your devices from MobileIron Core with Exodus πŸŽ‰

iOS 12.2+ support (Companion App v1.0.5)

Apple has released iOS 12.2 which impact the certificate installation. We have improved our solution to guide the users during this operation.

Extras

  • Add Host URL verification before submitting EMM configuration form.
  • Show failed devices in the progress bars of the Dashboard and Migration details.