IBM Support

Legacy Device Admin to AE Profile Owner Checklist

White Papers


Abstract

Checklist for DA to PO migration measures

Content

Legacy Device Admin to AE Profile Owner Checklist

  • Review documentation
  • Enable the Android Enterprise Solution Set in Setup>Services.
  • Take an inventory of devices by creating a Device group with your Device Admin devices.
  • Confirm that Android Enterprise is supported on the  devices you plan to migrate.
  • Make sure the MaaS360 for Android Agent version is 6.70 or later and the Android OS version is 5.1 or later.
    • (The device group displays this information)
  • Create a group of devices that you want to migrate, typically this will be the devices that you assigned a specific Android MDM policy to.
    • (For example, if you have 100 Device Admin devices maybe 20 of them are Kiosk devices that you don’t want to migrate to Profile Owner and the other 80 are set to migrate to Profile Owner). You can create a device group based on the Policy attribute in the Security & Compliance category.
  • Prepare the Android policy by copying your policy configurations from Device Settings and Advanced Settings to the Android Enterprise Settings.
    • (The same Android policy is used for the device. For example, if Android A with Device Admin has Android MDM Policy called  Sample assigned to it, you must copy the Device Settings and Advanced Settings to the Android Enterprise Settings within the Sample policy.)
  • Make a list of the existing Apps that must be pushed to devices that are migrating. You must approve these apps in the App Catalog and also designate whether to install automatically.
  • Enable the Android Enterprise Work Profile Migration in Setup>Settings
  • Make sure the Administrator who is initiating the Migrate to Work Profile has Wipe Device : Grant and Device View -Read-Only: Deny
  • Go to the Devices > Groups and initiate action Migrate to Work Profile for the group with devices you want to migrate. You can also initiate an action on an individual device by going to Device Inventory view and initiating the Migrate to Work Profile action.
    • (Note that it’s a good practice to test the process on an individual device before initiating on a group of devices)
  • The device must be in the following state to initiate the migration to the work profile:
    • Battery must be charged above 30%
    • Device must be connected to the internet
    • Androids running OS earlier than 7 must be encrypted
    • Time on the device and server must be encrypted
    • The Play Store services app must be up to date
    • The shared device must not be in a signed out state
    • The device must be in compliance
  • On the device, the user can tap the migration request notification or open the MaaS360 App and tap Migrate to Android Enterprise.
fating ffffwor Device Admin (DA) to the Work ProfileoAndroid Enterprise Deployment GuideEnable the Android Enterprise Solution Set in Setup>Services.Take an inventory of devices by creating a Device group with your Device Admin devices.Confirmthat Android Enterprise is supported on the devicesyou plan to migrate.Make sure the MaaS360 for Android Agent version is 6.70 or later and the Android OS version is 5.1 or later. o(The device group displays this information)Create a group of devices that you want to migrate, typically this will be the devices that you assigned a specificAndroid MDM policy to. o(For example, if you have 100 Device Admin devices maybe 20 of them are Kiosk devices that you don’t want to migrateto Profile Owner and the other 80 are set to migrate to Profile Owner). You can create a device group based on the Policy attribute in the Security & Compliance category. Prepare the Android policy by copyingyour policy configurations from Device Settings and Advanced Settings to the Android Enterprise Settings.o(The same Android policy is used for the device. For example, if Android A with Device Admin has Android MDM Policycalled Sample assigned to it, you must copy the Device Settings and Advanced Settings to the Android Enterprise Settings within theSamplepolicy.)Make a list of the existing Apps that must be pushed to devices that are migrating. You must approve these apps in the App Catalog and also designate whether to install automatically. Enable the Android Enterprise Work Profile Migrationin Setup>SettingsMake sure the Administrator who is initiating the Migrate to Work Profile has Wipe Device : Grant and Device View -Read-Only: DenyGo to the Devices > Groups and initiate action Migrate to Work Profile for the group with devices you want to migrate. You can also initiate an action on an individual device by going to Device Inventory view and initiating the Migrate to Work Profile action. o(Note that it’s a good practice to test the process on an individual device before initiating on a group of

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"ARM Category":[{"code":"a8m0z000000070eAAA","label":"SETUP"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
28 April 2020

UID

ibm16202535