- Getting started
- Changing BlackBerry UEM certificates
- Configuring BlackBerry UEM to send data through a proxy server
- Configuring connections through internal proxy servers
- Connecting to your company directories
- Connecting to an SMTP server to send email notifications
- Configuring single sign-on for BlackBerry UEM
- Obtaining an APNs certificate to manage iOS and macOS devices
- Controlling which devices can access Exchange ActiveSync
- Connecting BlackBerry UEM to Microsoft Azure
- Configuring BlackBerry UEM to support Android Enterprise devices
- Add an E-FOTA license
- Manage attestation for Samsung KNOX devices
- Manage attestation for Android devices and BlackBerry Dynamics apps using SafetyNet
- Manage attestation for Windows 10 devices
- Configuring BlackBerry UEM for DEP
- Setting up BlackBerry UEM Self-Service for users
- Configuring high availability for a BlackBerry UEM domain
- High availability for the components that manage BlackBerry OS devices
- Architecture: High availability for BlackBerry UEM
- Load-balancing data for BlackBerry 10 devices
- High availability and the BlackBerry Connectivity Node
- How BlackBerry UEM evaluates the health of components
- Install an additional BlackBerry UEM instance
- Configuring high availability for the management console
- Configuring database high availability using database mirroring
- Database high availability for components that manage BlackBerry OS devices
- Steps to configure database mirroring
- System requirements: Database mirroring
- Prerequisites: Configuring database mirroring
- Create and configure the mirror database
- Connect BlackBerry UEM to the mirror database
- Configuring a new mirror database
- Configuring TLS/SSL connections to Exchange ActiveSync when you enable the BlackBerry Secure Gateway
- Simplifying Windows 10 activations
- Migrating users, devices, groups, and other data from a source server
- Prerequisites: Migrating users, devices, groups, and other data from a source server
- Connect to a source server
- Considerations: Migrating IT policies, profiles, and groups from a source server
- Migrate IT policies, profiles, and groups from a source server
- Complete policy and profile migration from Good Control to BlackBerry UEM
- Considerations: Migrating users from a source server
- Migrate users from a source server
- Considerations: Migrating devices from a source server
- Migrate devices from a source server
- Migrating DEP devices
- Configuring BlackBerry UEM to support BlackBerry Dynamics apps
- Integrating BlackBerry UEM with Cisco ISE
- Requirements: Integrating BlackBerry UEM with Cisco ISE
- Create an administrator account that Cisco ISE can use
- Add the BlackBerry Web Services certificate to the Cisco ISE certificate store
- Connect BlackBerry UEM to Cisco ISE
- Example: Authorization policy rules for BlackBerry UEM
- Managing network access and device controls using Cisco ISE
- Monitoring BlackBerry UEM using SNMP tools
- BlackBerry Docs
- BlackBerry UEM 12.10
- Configuration
- Migrating users, devices, groups, and other data from a source server
- Migrate devices from a source server
Migrate devices from a source server
After you migrate users from the source
server to the destination
BlackBerry UEM
, you can migrate their devices. The devices move from the source server to the
destination BlackBerry UEM
and are no longer in the source after the migration.- Before you migrate devices, verify that the appropriate policies and entitlements are assigned to the users that you've migrated.
- For migrations fromBlackBerry UEMand, notifyBES10iOSdevice users that they must open theBlackBerry UEM Clientto start the migration toBlackBerry UEMand that they must keep theBlackBerry UEM Clientopen until the migration is complete.
- On the menu bar, clickSettings > Migration > Devices.
- On theMigrate devicesscreen, if the source is aGood Control(standalone) configuration, clickRefresh cache.The cache can take approximately 10 minutes for each 1000 devices to populate.BlackBerry UEMcaches the device data to speed searching capabilities, but the device data is migrated directly from the source. Refreshing the cache is mandatory only for the first set of device migration and optional afterward.
- ClickNext.
- Select the devices to migrate.ForGood Controlmigrations, only the first 20,000 devices are displayed. Search on the user name or email address to locate specific users that may not be in the first 20,000. Selecting all selects only those devices on the first page. Set the page size for the number of devices that you want to select.You may see fewer line items than number of devices because the cache is displayed by user and some users may have more than one device.ForGood Controlmigrations, if changes are made in the source after the cache is refreshed, those changes are not reflected in the cache data displayed. You should not make changes to the source server during migration, but if you do, refresh the cache periodically.
- ClickPreview.
- ClickMigrate.
- To view the status of the devices being migrated, clickMigration>Status.To determine whichBlackBerry Dynamicsapps have been migrated, run the container activity report onGood Control.Make sure that theGood Controlconfiguration remains running until all of the users' authentication delegate apps have completed migration, even if all devices are migrated.