Getting started
- Configuring BlackBerry UEM for the first time
- Configuration tasks for managing BlackBerry OS devices
- Administrator permissions you need to configure BlackBerry UEM
- Obtaining and activating licenses
- BlackBerry Enterprise Mobility Suite services
Changing BlackBerry UEM certificates
- Considerations for changing BlackBerry Dynamics certificates
- Change a BlackBerry UEM certificate
Configuring BlackBerry UEM to send data through a proxy server
- Sending data through a TCP proxy server to the BlackBerry Infrastructure
- Sending data through the BlackBerry Router to the BlackBerry Infrastructure
  - Configure BlackBerry UEM to use the BlackBerry Router
- Sending data through an HTTP proxy to the BlackBerry Dynamics NOC
  - Configure HTTP proxy settings
Configuring connections through internal proxy servers
- Configure server-side proxy settings
Connecting to your company directories
- Configuring Microsoft Active Directory authentication in an environment that includes a resource forest
- Connect to a Microsoft Active Directory instance
- Connect to an LDAP directory
- Enable directory-linked groups
- Enabling onboarding
  - Enable and configure onboarding and offboarding
- Synchronize a company directory connection
Connecting to an SMTP server to send email notifications
- Connect to an SMTP server to send email notifications
Configuring single sign-on for BlackBerry UEM
- Configure constrained delegation for the Microsoft Active Directory account to support single sign-on
- Configure single sign-on for BlackBerry UEM
  - Console URLs for single sign-on
  - Browser requirements: Single sign-on
Obtaining an APNs certificate to manage iOS and macOS devices
- Obtain a signed CSR from BlackBerry
- Request an APNs certificate from Apple
- Register the APNs certificate
- Renew the APNs certificate
- Troubleshooting APNs
Controlling which devices can access Exchange ActiveSync
- Steps to configure Exchange ActiveSync and the BlackBerry Gatekeeping Service
- Configure permissions for gatekeeping
- Allow only authorized devices to access Exchange ActiveSync
  - Configure Microsoft Exchange to allow only authorized devices to access Exchange ActiveSync
  - Configure the mobile device access policy in Microsoft Office 365
- Configure Microsoft IIS permissions for gatekeeping
- Create a gatekeeping configuration
Connecting BlackBerry UEM to Microsoft Azure
- Create a Microsoft Azure account
- Synchronize Microsoft Active Directory with Microsoft Azure
- Create an enterprise endpoint in Azure
- Configuring BlackBerry UEM to synchronize with Microsoft Intune
  - Configure BlackBerry UEM to synchronize with Microsoft Intune
- Configuring BlackBerry UEM to synchronize with the Windows Store for Business
Configuring BlackBerry UEM to support Android Enterprise devices
- Configure BlackBerry UEM to support Android Enterprise devices
- Remove the connection to your Google domain
- Remove the Google domain connection using your Google account
- Edit or test the Google domain connection
Add an E-FOTA license
Manage attestation for Samsung KNOX devices
Manage attestation for Android devices and BlackBerry Dynamics apps using SafetyNet
- Considerations for configuring SafetyNet attestation
- Considerations for configuring SafetyNet attestation - App versions
- Configure attestation for Android devices and BlackBerry Dynamics apps using SafetyNet
Manage attestation for Windows 10 devices
Configuring BlackBerry UEM for DEP
- Create a DEP account
- Download a public key
- Generate a server token
- Register the server token with BlackBerry UEM
- Add the first enrollment configuration
- Update the server token
- Remove a DEP connection
Setting up BlackBerry UEM Self-Service for users
- Set up BlackBerry UEM Self-Service
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
- Configure BlackBerry UEM to trust the Exchange ActiveSync server certificate
- Configure BlackBerry UEM to use the TLS versions and ciphers that Exchange ActiveSync supports
Simplifying Windows 10 activations
- Deploy a discovery service to simplify 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
  - Export the self-signed root certificate for the Good Control 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
  - Good Control features in BlackBerry UEM
- Considerations: Migrating users from a source server
- Migrate users from a source server
- Considerations: Migrating devices from a source server
  - Device migration quick reference
- Migrate devices from a source server
- Migrating DEP devices
  - Migrate DEP devices that have the BlackBerry UEM Client installed
  - Migrate DEP devices that do not have the BlackBerry UEM Client installed
Configuring BlackBerry UEM to support BlackBerry Dynamics apps
- Manage BlackBerry Proxy clusters
- Configure Direct Connect or a web proxy for BlackBerry Proxy connections
- Configure BlackBerry Dynamics properties
- Configure communication settings for BlackBerry Dynamics apps
- Configuring certificates for BlackBerry Dynamics apps
  - Configure a time to live for client certificates
  - Configuring PKI connections for BlackBerry Dynamics apps
    - PKI connector interactions
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
  - Redirecting devices that are not activated on BlackBerry UEM
Monitoring BlackBerry UEM using SNMP tools
- Supported SNMP operations
- System requirements: SNMP monitoring
- MIBs for BlackBerry UEM
- Compile the MIB and configure the SNMP management tool
- Using SNMP to monitor components
  - Configure SNMP to monitor components

Configure
BlackBerry UEM
to support
Android Enterprise
devices

You can connect only one

BlackBerry UEM

domain to your

Google

domain. Before you connect another

BlackBerry UEM

domain, you must remove the existing connection. See Remove the connection to your Google domain.

On the menu bar, click

Settings > External integration > Android enterprise

Perform one of the following tasks:

Task	Steps
Use Android Enterprise devices that have managed Google Play accounts	Select Allow BlackBerry UEM to manage Google Play Accounts . Click Next . In the Bring Android to Work window, sign in using a Google account. You can use any Google or Gmail account. The account that you use will become the administrator account for the Bring Android to Work service. Click Get Started . Type the name of your organization. Click Confirm . Click Complete registration . You will be returned to the BlackBerry UEM management console.
Use a Google domain	Select Connect BlackBerry UEM to your existing Google domain . Click Next . Complete the fields to create a service account and click Next . For step-by-step instructions, visit http://support.blackberry.com/kb to read article 000037748.

Task

Steps

Use

Android Enterprise

devices that have managed

Google Play

accounts

Select

Allow BlackBerry UEM to manage Google Play Accounts

Click

In the

Bring Android to Work

window, sign in using a

Google

account. You can use any

Google

Gmail

account. The account that you use will become the administrator account for the

Bring Android to Work

service.

Click

Get Started

Type the name of your organization. Click

Confirm

Click

Complete registration

. You will be returned to the

BlackBerry UEM

management console.

Use a

Google

domain

Select

Connect BlackBerry UEM to your existing Google domain

Click

Complete the fields to create a service account and click

. For step-by-step instructions, visit http://support.blackberry.com/kb to read article 000037748.

Specify how you want app configurations to be sent to a device. Any information that you added in the app configuration can be either provided using the

BlackBerry Infrastructure

or provided using the

Google

infrastructure. Do one of the following:

Select

Send app configuration using UEM Client

to send app configuration details using the

BlackBerry Infrastructure

Select

Send app configuration using Google Play

to send app configurations details using the

Google

infrastructure.

When you are prompted, click

to accept the permissions set for some or all of the following apps:

Google Chrome

BlackBerry Connectivity

BlackBerry Hub

+ Services

BlackBerry Hub

BlackBerry

Calendar

Contacts by

BlackBerry

Notes by

BlackBerry

Tasks by

BlackBerry

Click

Done

Complete the steps to activate

Android Enterprise

devices. For more information about device activation, see "Device activation" in the Administration content.

Section:

Configuring BlackBerry UEM to support Android Enterprise devices

Configure BlackBerry UEM to support Android Enterprise devices

Configure
BlackBerry UEM
to support
Android Enterprise
devices