- 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
- Integrating BlackBerry UEM with Cisco ISE
- Managing network access and device controls using Cisco ISE
- Redirecting devices that are not activated on BlackBerry UEM
Redirecting devices that are not activated on BlackBerry UEM
BlackBerry UEM
If
Cisco Identity Services
Engine
(ISE) identifies a device
that is trying to access the work network (Wi-Fi
or VPN), and
the device is not activated on BlackBerry UEM
, Cisco ISE
opens an enrollment page in
the device browser that redirects the user to the BlackBerry UEM Self-Service
console.The user requires a
BlackBerry UEM
user account
to log in to BlackBerry UEM Self-Service
and activate
the device. Instruct users to contact the BlackBerry UEM
administrator if Cisco ISE
directs
them to the enrollment page.For more information about adding and activating user accounts, see the Administration content.
If a user's device was previously activated with
BlackBerry UEM
then
deactivated, the user is not redirected to BlackBerry UEM Self-Service
when the user tries to access the work network from the device. To resolve
this issue, when you remove a device from BlackBerry UEM
, delete the
data for that device from Cisco ISE
.