Two types of Android Enterprise enrollment exists:
work profilethat creates a container in which apps can be managed
fully managedthat manages the whole device dedicated for corporate use only
fully managed with a work profilethat manages the whole device both for corporate and personal use
For more details on definitions visit the Android Enterprise Terminology page
For the work profile settings, the migration target EMM environment needs a configured Google account.
Please refer to your official target EMM guidelines to ensure proper compatibility.
Beyond the Exodus Companion app steps, the end-user must follow the EMM Agent instructions.
Fully managed & fully managed with a work profile
For the fully managed and fully managed with work profile settings, the migration target EMM environment needs a configured Google account.
Please refer to your official target EMM guideline to ensure proper compatibility.
In the Exodus console, when a migration is created, you must choose to fully manage the devices or not (see fig. 1.1).
Do not forget that the end-users' devices will be wiped. You must ensure that end-users personal data have been properly saved prior to proceed.
Because of the device wipe, the end-users will have to follow the enrollment procedure on their own with the DPC identifier corresponding to their EMM target.
|Welcome screen||WiFi screen||Sign-In with airwatch dpc identifier|
You can also refer to the specificities of each target EMM here: