- 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 high availability for a BlackBerry UEM domain
- Install an additional BlackBerry UEM instance
Install an additional BlackBerry UEM instance
BlackBerry UEM
instanceTo install
additional
BlackBerry UEM
instances to create a high availability domain, see the Installation and upgrade content.
Verify that the computer satisfies the system requirements for installing a BlackBerry UEM
instance, and complete the necessary preinstallation and postinstallation tasks. For
compatibility details, see the Compatibility matrix.- When you install additionalBlackBerry UEMinstances:
- Install each instance on a separate computer.
- In the setup application, on theSetup typescreen, selectUse an existing domain.
- On theDatabase informationscreen, specify the information for theBlackBerry UEMdatabase that you created when you installed the originalBlackBerry UEMinstance.
After you install an additional
BlackBerry UEM
instance and
complete the necessary postinstallation tasks, active-active high availability is
available in the domain. User and device data is load-balanced across the BlackBerry UEM
instances, the
active BlackBerry Affinity Manager
monitors the enterprise
connectivity of each instance, and the standby BlackBerry Affinity Manager
instances monitor the active
instance to determine whether a failover is required.