- 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
- Configuring database high availability using database mirroring
- System requirements: Database mirroring
System requirements: Database mirroring
Item | Requirement |
---|---|
Microsoft SQL
Server | BlackBerry UEM supports database
mirroring using one of the following:
|
SQL Server Native
Client | The SQL Server 2012
Native Client must be installed on each computer that hosts a BlackBerry UEM instance. The BlackBerry UEM setup application
installs the SQL Server
2012 Native Client. |
Version parity | The Microsoft SQL
Server that hosts the mirror database must be the same version and edition as
the Microsoft SQL
Server that hosts the principal database. |
Single data center | The principal and mirror database must be located in the same data
center. |
Database location | Create the mirror database on a different computer than the principal
database. |
Operating mode | Configure database mirroring using high-safety mode with automatic
failover. |
Witness | A witness server is required for automatic failover. The witness must be
a different server than the principal server and the mirror server. For more information, see Database Mirroring Witness – SQL Server 2012 or Database Mirroring Witness – SQL Server 2014. |