- Configuring BlackBerry UEM
- Changing the certificates that BlackBerry UEM uses for authentication
- Installing the BlackBerry Connectivity Node to connect to resources behind your organization's firewall
- Configuring BlackBerry UEM to send data through a proxy server
- Configure connections through internal proxy servers
- Connect to an SMTP server to send email notifications
- Connecting to your company directories
- Connecting BlackBerry UEM to Microsoft Entra ID
- Obtaining an APNs certificate to manage iOS and macOS devices
- Configure BlackBerry UEM for DEP
- Configuring BlackBerry UEM to support Android Enterprise devices
- Configuring BlackBerry UEM to support Android Management devices
- Extending the management of Chrome OS devices to BlackBerry UEM
- 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 BlackBerry server
- UEM migration best practices and considerations
- Connect to a source server
- Migrate IT policies, profiles, and groups from a source server
- Migrate users from a source server
- Migrate devices from a source server
- Configuring network communication and properties for BlackBerry Dynamics apps
- Manage BlackBerry Proxy clusters
- Configure Direct Connect using port forwarding
- Configure BlackBerry Dynamics properties
- Configure communication settings for BlackBerry Dynamics apps
- Sending BlackBerry Dynamics app data through an HTTP proxy
- Methods for routing traffic for BlackBerry Dynamics apps
- Configuring Kerberos authentication for BlackBerry Dynamics apps
- Integrating BlackBerry UEM with Cisco ISE
- Set up VPN using Knox StrongSwan for UEM dark site environments
- BlackBerry Docs
- BlackBerry UEM 12.19
- UEM Configuration Guide
- Migrating users, devices, groups, and other data from a source server
- Migrate users from a source server
Migrate users from a source server
- In the management console, on the menu bar, clickSettings > Migration > Users.
- ClickRefresh cache.The refresh requires approximately 10 minutes for every 1000 users. Refreshing the cache is mandatory only for the first set of users that you want to migrate. If you make changes to the source server during migration, it is a best practice to refresh the cache again.
- ClickNext.
- Select the users that you want to migrate.By default, only the first 20,000 users are displayed. You can search for specific users as needed. Note that selecting all users selects only those displayed on the first page.
- ClickNext.
- Assign an IT policy, groups, and profiles to the selected users.
- ClickPreview.
- ClickMigrate.
Note that migrated user accounts are not removed from the source server.