Considerations: Migrating IT policies, profiles, and groups from a source server
A migration from a
BlackBerry UEM
source copies the following items to the destination database:
- Selected IT policies
- Email profiles
- Wi-Fiprofiles
- VPN profiles
- Proxy profiles
- BlackBerry Dynamicsprofiles
- CA certificate profiles
- Shared certificate profiles
- SCEP profiles
- User credential profiles
- Certification authority settings
- Any policies and profiles that are associated with the policies and profiles you select
For groups from
BlackBerry UEM
, user, role, and software configuration assignments, and BlackBerry
OS attributes are not migrated.A migration from a
Good Control
(standalone) source copies the following items to the destination database:
- Policy sets
- Connectivity profiles
- App groups
- App usage (for certificates)
- Certificates
BlackBerry UEM
BlackBerry UEM
When you migrate
BlackBerry UEM
IT policies, profiles, and groups to another domain, consider the following guidelines:Item | Considerations |
|---|---|
IT policy passwords | If any of the source IT policies you selected for Android devices has a minimum password length of less than 4 or more than 16, no BES12 or BlackBerry UEM IT policies or profiles can be migrated. Deselect or update the source IT policy and restart the migration. |
Profile names | After migration, you must make sure that all SCEP, user credential, shared certificate, or CA certificate profiles have unique names. If two profiles of the same type have the same name, you must edit one of the profile names. |
Directory groups | To migrate directory groups, the source database and destination database must each have only one directory configured. This directory must be configured the same way on both the source and destination database. If the directories are not set up this way, directory groups are not migrated. |
Nested groups | If the source and destination databases are BES12 or BlackBerry UEM databases that have been integrated with BES5 , you cannot migrate nested user groups. If you try to migrate nested groups, other groups, profiles, and PKI configuration information might not be migrated. |
Good Control (standalone)
Good Control
(standalone)When you migrate
Good Control
(standalone) security policy sets, connectivity profiles, app groups, and certificates to BlackBerry UEM
, consider the following guidelines:Item | Considerations |
|---|---|
Policy sets | After migration, each Good Control policy set appears as the following items in BlackBerry UEM :
|
Connectivity profiles | When BlackBerry
Dynamics connectivity profiles are migrated from Good Control (standalone) to BlackBerry UEM , the values from the App servers tab are not migrated. The values are populated using the default values from the destination UEM server, the same as when manually creating a new BlackBerry
Dynamics connectivity profile in UEM.When BlackBerry
Dynamics connectivity profiles are migrated from Good Control (standalone) to BlackBerry UEM , some of the values from the Infrastructure tab are not migrated. The administrator must manually edit each migrated profile and set the values for the Primary BlackBerry Proxy cluster and the Secondary BlackBerry Proxy cluster. |
App groups | The Everyone group is migrated but has no users assigned to it and is not related to the All Users group on the destination BlackBerry UEM . The administrator must manually assign it to users if needed. |
Apps | If an app entitlement from the source server doesn't exist in the destination server, that app assignment is not migrated. The app group is migrated. |
App usage (for certificates) | App usage is migrated, except for:
|