EBF product documentation

Find help using and administering EBF applications

View Categories

13. Platforms

18 min read

13.1. Android Enterprise device migration

The EBF Onboarder can migrate Android Enterprise devices. In the process, it is possible to switch to another Android operating model at the same time (Device Admin, BYOD, COPE (WPCOD), COBO, COSU).

The following table shows what is possible, which target system must be selected in step 3 of the migration process (target system selection), what the migration steps look like and if a device wipe is required.

Android source Android target Migration target Migration steps Device wipe
Device Admin (Legacy) Device Admin (Legacy) Your target UEM system See variant 2 below No
Device Admin (Legacy) BYOD Your target UEM system See variant 2 below

NOTE: The process can be different on Samsung devices.

 No
Device Admin (Legacy) COPE/COBO Managed Enrollment See variant 1 below

NOTE: The process can be different on Samsung devices.

 Yes
BYOD BYOD Your target UEM system See variant 3 below No
BYOD COPE/COBO Managed Enrollment See variant 1 below Yes
COPE COPE/COBO Managed Enrollment See variant 1 below Yes
COPE BYOD Managed Enrollment See variant 3 below

NOTE: This is only possible if the source system supports the relinquish ownership feature and the device has Android 11 or newer.

Currently Ivanti EPMM/Neurons (MobileIron Core&Cloud) support the relinquish ownership feature. Ivanti will add the feature to the default retire command in Core version 11.10 (read this article for more information).

 Yes
COBO COBO/COPE Managed Enrollment See variant 1 below Yes
COSU COSU/COBO/COPE Managed Enrollment See variant 4 below

NOTE: Currently COSU is a special case for Microsoft Intune as no user name or email is provided. For MDM systems, COSU devices can be migrated like COBO devices.

 Yes

Device Admin (Legacy): Personal and corporate-owned devices with device administrator privileges
COSU: Corporate-Owned Single-Use, kiosk devices
COBO: Corporate Owned, Business Only, fully-managed devices
COPE: Corporate Owned, Personally Enabled, devices with work profile
BYOD: Bring Your Own Device, user-owned devices with work profile

13.1.1 Migration steps

Migration steps – Variant 1

  1. An invitation email with the migration link is sent to the users.
  2. Users need to press the start button in the invitation email.
  3. The device is wiped (factory reset).
  4. The device reboots and the welcome screen is shown.
  5. A setup type must be chosen (see Setup Methods below).

Migration steps – Variant 2

  1. An invitation email with the migration link is sent to the users. The link can be sent in different formats:
    • {urlGo} (requires access to the mailbox to receive the additional email with the PIN)
    • {qr} QR code (requires a second device or a printout to receive the QR code)
    • {urlIreg} (Only if Microsoft Intune is the source or target system. Please read the separate documentation to learn more about this. You can find it here.)
  2. Users need to open the invitation link in the personal profile.
  3. Users need to enter email address and PIN which is included in the email.

Migration steps – Variant 3

  1. An invitation email with the migration link is sent to the users. The link can be sent in different formats:
    • {urlGo} (requires access to the mailbox to receive the additional email with the PIN)
    • QR code (requires a second device or a printout to receive the QR code)
    • {urlIreg}

    Users need to open these migration links in the personal profile. If the /ireg link or /go link is used, they need to enter the email address and PIN (for urlGo) which is included in a second email.

  2. The work profile is removed. Users will be forwarded to the Play Store. In some cases they need to manually search the old Management App in the Play Store to be able to delete it, but this should no longer happen.
  3. Users need to install the MDM app from the new MDM and register.

 Migration steps – Variant 4

  1. A web app with the migration link is provided to the users to the device with the source MDM.
  2. Users need to activate the migration by marking the device as notified. Currently it is required to perform this for every single device.
  3. Users need to open the web app and press ‘Start’.
  4. The device is wiped (factory reset).
  5. The device reboots and the Welcome screen is shown.
  6. A setup type must be chosen (see Setup Methods below).

13.1.2 Setup methods

There are different setup methods an admin can choose which are described in the tables below.

Initiate setup via AFW#Token
Process
  1. Turn on a new device or a device reset to factory settings. Follow the instructions in the setup wizard.
  2. Enter the WiFi credentials to connect the device to the internet.
  3. When prompted to sign in, enter the token provided by the MDM provider.
  4. Follow the instructions to complete the setup.
Supported Android devices Devices with Android Marshmallow 6.0 or higher
Supported management groups
  • Complete device management
  • Individual device management
  • Work profiles (only company-owned devices with Android 8.0 or higher)
Transfer setup details via QR code
Process
  1. Turn on a new device or a device reset to factory settings.
  2. Tap the screen at the same place six times. This causes the device to prompt you to scan a QR code.
  3. Scan the QR code provided by the MDM provider. The QR code can include additional setup details such as WiFi credentials, language, time zone, and custom disclaimers.
Supported Android devices New device or a device reset to factory settings with Android 7.0 or higher with a QR code reader
Supported management groups
  • Complete device management
  • Individual device management
  • Work profiles (only company-owned devices with Android 8.0 or higher)
Transfer setup details via NFC
Process Hold a new device or a device reset to factory settings to an NFC tag that contains setup details provided by the MDM provider. The NFC tag can include details such as Wi-Fi Login details, language, time zone and custom disclaimers.
Supported Android devices Devices with Android 6.0 or higher with NFC capabilities, from Android 10 and up no longer available
Supported management groups
  • Complete device management
  • Individual device management
Pre-configured devices with contactless enrollment (Zero Touch)
Process Zero Touch enrollment allows you to pre-configure Android devices purchased from a Zero Touch reseller. Devices pre-registered for Zero Touch enrollment can be shipped to users directly. On first boot, registered Zero Touch devices check for an assigned company configuration and set themselves up automatically. Users can follow the on-screen instructions to complete the setup.

Only for Samsung devices running Android 9.0 or 10:

  1. Turn on the device.
  2. Follow the instructions until the screen prompts you to transfer your old data to the device (e.g. Bring your old data for quicker setup or similar).
  3. Select ‘Skip this‘ for now and click ‘Next’.
  4. Follow the instructions to complete the setup.
Supported Android devices Devices with Android 9.0 or higher (initially via selected resellers only), compatible devices with Android 8.0 or higher, Pixel phones with Android 7.0 purchased from a Zero Touch reseller (https://androidenterprisepartners.withgoogle.com/resellers/)
Supported management groups
  1. Complete device management
  2. Individual device management
  3. Work profiles
Pre-configured devices with contactless enrollment (Knox Mobile Enrollment)
Process The Knox Mobile Enrollment allows you to pre-configure Android devices purchased from a reseller with a KME enrollment. Devices pre-registered for KME enrollment can be shipped to users directly. On first boot, devices enrolled in Knox Mobile Enrollment check for an assigned company configuration and the devices are automatically provisioned. Users can follow the on-screen instructions to complete the setup.

  1. Turn on the device.
  2. Follow the instructions until the screen prompts you to transfer your old data to the device (e.g. Bring your old data for quicker setup or similar).
  3. Select ‘Skip this‘ for now and click ‘Next’.
  4. Follow the instructions to complete the setup.
Supported Android devices Samsung devices with Knox 2.4 or higher for Android enrollment and Knox 2.8 or higher for Android Enterprise enrollment
Supported management groups
  1. Complete device management
  2. Individual device management
  3. Work profiles

13.2 Windows Desktop migration

The EBF Onboarder can migrate Windows 10/11 Desktop systems, including those where users have only user access on the device.
There are two cases:

  1. The common case: The user has only user access to the computer (see chapter 13.2.1).
  2. The users are part of an administrator group (see chapter 13.2.2).

13.2.1. Typical Windows Desktop migration for normal users

If the devices to be migrated have only user access, you can follow this instruction.

The EBF Onboarder does not make it necessary:  

  • to provide manual administrator privileges to users to be able to register their devices in the target system
  • to remove autopilot devices which would result in resetting the machine
  • to deal with general devices without local administrators

You can also migrate Windows devices with user accounts from the following sources: 

  • Active Directory Managed Devices
  • MDM Managed Devices without Active Directory profiles
  • MDM Managed Devices with Active Directory profiles
  • Entra AD Devices with MDM to switch the MDM
  • Entra AD Devices (which is intended for switching the Entra AD tenant – when you want to use Intune on the same tenant for your machine, you can register them automatically)

You can set up different target systems for your migration – including: 

  • Entra AD via deep link
  • MDM systems via deep link without A(AD) profiles
  • Entra AD with automatic MDM registration (best option, but requires the P2 license in Azure)
  • Local Active Directory when the connection to the local AD servers is present (can be combined with an MDM registration (planned feature))

Follow these steps to do so: 

  1. The administrator uploads the EBF Onboarder installation package to the existing software distribution tool (this could be an MDM system like AirWatch or Ivanti EPMM) and installs it on the devices. Every MDM that can manage Windows devices and distribute software is supported!
  2. After installing our tool, the device remains in the initial situation until the user starts our app to migrate.The user will migrate only when he is ready!
  3. When the migration is started, the device checks for an existing migration on the EBF Onboarder server and only starts when an active migration for this device is found. Having the tool installed does not let you migrate the device. The admin can control what happens on the Windows device and who is able to migrate!
  4. After the migration is started, the device enters a restricted mode with an admin profile where the user is not able to do anything else than migrating his devices. The process is guided by our tool and the user simply needs to authenticate at the target system.
  5. Once the device is migrated to the new MDM system, the administrator privileges are removed again.
  6. You can integrate your own PowerShell scripts for executing before and after the migration. This can be used for backup scripts or removing old management software on the devices.
  7. Before, during and after the migration process the admin will be able to monitor the process and inform, invite or remind the user in the EBF Onboarder portal.

NOTE: No own server is needed for migrating Windows devices.

13.2.2 Windows Desktop migration for Admin users

If the devices to be migrated are part of the administrator group, you can either use the normal EBF Onboarder migration or a deep link.

Deep link configuration

When registering a desktop device, users typically need to install the client app of the target MDM system (for example the Intune Comp Portal or the Workspace ONE Intelligent Hub), type in a server name, account name and a password. Windows supports a much easier way to register devices in the target MDM system: deep links.

Deep links forward the user directly to Windows settings and the Work/School Management Registration. The userid and the MDM server can be prefilled so that users just need to enter their password to start the registration.

The EBF Onboarder can handle deep links for Windows desktop migrations. In the following chapters you will learn how to create and use them.

There are two ways to configure a deep link:

Variant 1:

You can do that during the target system selection: Windows Enrollment (optional).

Variant 2:

You can edit the deep link after creating the migration project in the migration project dashboard:

  1. Go to the EBF Onboarder dashboard and click on ‘Migration Details’ to access the migration project dashboard.
  2. Click on ‘Windows Enrollment’.
  3. Edit the value for “ms-device-enrollment:?”.
  4. The blue info button will bring you to the Microsoft Website with information about the deep link.
  5. Enter the correct
  6. Click on ‘Save’.

Deep link creation

The deep link has the following format: ms-device-enrollment:?mode={mode_name}

Example: A deep link for the EBF Onboarder and the target system Microsoft Intune is: mode=mdm&username={userid}&servername=https://enrollment.manage.microsoft.com/enrollmentserver/discovery.svc

  • In this link, the parameter ‘userid’ is a EBF Onboarder parameter and is not provided by Microsoft. It adds the userid of the device user to the deep link so that usersids are prefilled in the Work/School Registration screen.
  • The parameter ‘servername’ is the enrollment link of your target MDM system.
  • You can find more details about deep link parameters on the Microsoft website.

Deep link usage

Users basically need to perform the same steps as on other devices to use a deep link:

  1. They click on the ‘Start’ button in the invitation mail and follow the enrollment steps.
  2. They click on ‘Connect to new MDM’.
  3. The Windows Work/School Registration windows shows up and the user enter their password.
  4. The target MDM system will guide the users to the other required steps.

NOTE: The EBF Onboarder recognizes the operating system of the device. Thus, it is possible to setup migration projects with different operating systems. Each device will get the correct enrollment link. Nevertheless we recommend to create different migration projects for different operating systems to have a better overview of the migrations and to customize the information sent to users to each operating system. Additionally, users should not migrate their desktop and mobile device at the same time.

13.3 MacOS Migration

This documentation complements the general EBF Onboarder documentation and provides more detailed information for migrating devices using the EBF MacOS Onboarder.

ATTENTION:
This documentation does not replace any MDM/UEM or Apple documentation. It is only describing prerequisites, setup configuration and usage for the EBF Onboarder. Please consult the UEM/MDM and Apple documentation and support if necessary.

13.3.1 General Information

EBF has extended the configuration types for device migrations using the EBF Onboarder.
The EBF Onboarder is already able to migrate MacOS devices, if the user has administrator access on the device.
But typically, a user does not have administrator rights on their computers. For a user the registration of a device in a new target MDM/UEM is not possible, because the MacOS requests an administrator password to install the new MDM/UEM profile.

Using the EBF MacOS Onboarder software, you as an administrator can request the users to migrate from one MDM/UEM to another system, without you touching the device.

Please Note:
This software is designed to migrate users without administrator access on the computer. But Users with Admin access already can use the standard EBF Onboarder migration option.

13.3.1.1 Available Migration Types

The EBF MacOS Onboarder software supports the following migrations:
– Migrate MDM Managed Devices from one MDM/UEM to another.
We support all MDMs, that the EBF Onboarder is supporting as well.

13.3.2 Functionality

13.3.2.1 Components of the EBF Onboarder for MacOS

The Onboarder for MacOS includes these components as follows:

  • The Onboarder MacOS app
    The app must be distributed to designated clients. This can be any MDM/UEM or software management system that is able to manage MacOS devices and install applications.

    NOTE:
    The source MDM must not remove the EBF software from the device after it is retired/removed/unenrolled from the MDM, but the onboarder.mobileconfig profile.

  • The Onboarder Helper service
    This service will be installed by installing the app. This service is used to perform admin operations like allowing the user to install the new MDM/UEM profile.
  • onboarder.mobileconfig file
    A proper configuration is required and needs to be sent to the device as well.
    Details about the configuration you will find under: Configuration

13.3.2.2 How the Onboarder for MacOS works

Once the app and the mobileconfig file are installed on the device, the service is installed as well and starts.

At this point, and if the computer restarts, the service will start checking the Onboarder server for a project with the serial number of the device, authenticating to the server and tenant by the given app_token.

If the device is found, but the migration is not activated (Invite not sent), the app will show a red dot, and the “Start migration” is not displayed.

 

If the invite was sent and the service finds it, a green dot is showing and the “Start Migration” button will be available:

If the user starts the migration, the EBF Onboarder will retire/unenroll the device from the source system and forward you to the target MDM/UEM to download the MDM configuration profile.

If the profile was downloaded, the user will be able to install the MDM profile.

After the MDM profile was installed, the Onboarder service removes the access from the user again and removes itself from the computer.

The target MDM will continue to configure the desktop. The Onboarder software will itself remove from the computer.
The migration is complete.

13.3.3 Typical procedure of a device migration

  1. Identify the devices to migrate, add them to groups.
  2. Create a project in the EBF Onboarder, add the devices using a group and setup the Information, Invitation and Welcome messages.
  3. Create the onboarder.mobileconfig file:
    1. Create the Apptoken in the EBF Onboarder Tenant Settings
    2. Add the Onboarder Server url
    3. Setup/disable the helper page
  4. Send the app and the onboarder.mobileconfig file to the computers. Wait for the deployment.
  5. Sent the Invitations to the users.
  6. User click the Start Migration button or start the app manually.
  7. Users migrate to the new MDM/UEM
    For migrations to Microsoft Intune, the Onboarder app will download, install and open the Company Portal app automatically for the user to login to be able to load  and install the MDM profile.
  8. EBF Onboarder app removes itself from the computers.
  9. EBF Onboarder shows the status of the migration.

13.3.4 Configuration

13.3.4.1 Definition of the configuration

The configuration is stored in the onboarder.mobileconfig file.

The onboarder.mobileconfig file needs to pushed to the device and installed via MDM like the app, before the migration.

The following parameters needs to be modified. All other lines and parameters must not be edited.

Key Values
base_url Mandatory:
This is typically the onboarder base URLExample: https://onboarder-test.ebf.com/
app_token  Mandatory:
The Onboarder apptoken to authenticate the access to your tenant. Check below to see how to create the apptoken.
display_help_button true: shows the help button
false: do not show the help button
help_button_url URL that opens, when the help button is pressed. Default: EBF Onboarder documentation: https://docs.ebf.com/doc/introduction-onboarder/
intunes_company_portal_download_url URL to download the company portal app.
Default: https://officecdn.microsoft.com/pr/C1297A47-86C4-4C1F-97FA-950631F94777/MacAutoupdate/CompanyPortal-Installer.pkg

 

If the onboarder.mobileconfig file was successfully pushed to the computer, you can check the content easily by opening:
System Settings -> General -> Device Management EBF Onboarder:

Please note:
The onboarder.mobileconfig (EBF Onboarder) profile needs to be removed from the computer when the source MDM profile is removed.

Example of the onboarder.mobileconfig file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>PayloadContent</key>
  <array>
    <dict>
      <key>PayloadDisplayName</key>
      <string>EBF Onboarder Configuration</string>
      <key>PayloadIdentifier</key>
      <string>com.ebf.onboarder.EBF0EBF1-05D7-4B4B-8A76-EBF01B0A2DE2</string>
      <key>PayloadType</key>
      <string>com.ebf.onboarder</string>
      <key>PayloadUUID</key>
      <string>EBF0EBF1-05D7-4B4B-8A76-EBF01B0A2DE2</string>
      <key>PayloadVersion</key>
      <integer>1</integer>
      <key>app_token</key>
      <string><<<Apptoken created in your tenant>>></string>
      <key>base_url</key>
      <string>https://<<<Onboarder-server-url>>></string>
      <key>display_help_button</key>
      <true/>
      <key>help_button_url</key>
      <string>https://docs.ebf.com/doc/introduction-onboarder/</string>
      <key>intunes_company_portal_download_url</key>
      <string>https://officecdn.microsoft.com/pr/C1297A47-86C4-4C1F-97FA-950631F94777/MacAutoupdate/CompanyPortal-Installer.pkg</string>
    </dict>
  </array>
  <key>PayloadDisplayName</key>
  <string>EBF Onboarder</string>
  <key>PayloadIdentifier</key>
  <string>CM-EBF01B0A2DE2.EBF0EBF1-E074-4380-A8C7-EBF01B0A2DE2</string>
  <key>PayloadOrganization</key>
  <string>EBF</string>
  <key>PayloadScope</key>
  <string>System</string>
  <key>PayloadType</key>
  <string>Configuration</string>
  <key>PayloadUUID</key>
  <string>EBF0EBF1-E074-4380-A8C7-EBF01B0A2DE2</string>
  <key>PayloadVersion</key>
  <integer>1</integer>
  <key>TargetDeviceType</key>
  <integer>0</integer>
</dict>
</plist>

How to Generate the apptoken

  1. In the EBF Onboarder please go to Settings –> Tenant Settings:
  2. Select “Apps” and click “generate Token” for the AppToken
  3. After creating the Apptoken you can add it to the configuration file.

Enable Fast fetchin (mandatory)

The EBF Onboarder system needs to be updated in time about the status of the migration on the device. To enable this feature, please open the Tenant Settings

13.3.5 Software

Please contact our support team at support@ebf.com to receive the software package.

13.3.6 FAQ/Common Issues

13.3.6.1 Backup

The EBF Onboarder for MacOS is not able to handle or create backups.
If any data is stored in an app removed by the source MDM (like on a cloud system), manual steps are required by the user (or IT) to save the data before.

13.3.6.2 Microsoft Intune web enrollment

Microsoft Intune does not support Web Enrollment for MacOS computers.

13.3.6.3 Network

Device needs to stay connected to network all the time

13.3.6.4 Testing / Serial Number

If you are testing with the same device(what is typically the case), please make sure to have a device(serial number) only in one project. Means, you should delete an old project with your device. Otherwise, the Onboarder app might find the wrong project.

Was this article useful?