- Configuring BlackBerry UEM for the first time
- 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 database mirroring
- Connecting BlackBerry UEM to Microsoft Azure
- Enable access to the BlackBerry Web Services over the BlackBerry Infrastructure
- Obtaining an APNs certificate to manage iOS and macOS devices
- Configuring BlackBerry UEM for DEP
- Configuring BlackBerry UEM to support Android Enterprise devices
- 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 for BlackBerry Dynamics-activated users
- 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
- 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
- Configuring Kerberos for 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
PAC file considerations
You should be aware of the following support considerations if you are using PAC files with
BlackBerry Proxy
.BlackBerry UEM
supports the following PAC file directives:
- DIRECT
- PROXY (treated as HTTPS proxy - connection established using HTTP CONNECT)
- HTTPS (connection established using HTTP CONNECT)
BlackBerry UEM
doesn't support the following PAC file directives:
- BLOCK (treated as DIRECT)
- SOCKS (connection error will occur)
- SOCKS4 (connection error will occur)
- SOCKS5 (connection error will occur)
- HTTP (connection error will occur)
- Custom "NATIVE" directive defined byBlackBerry Access(connection error will occur)
BlackBerry UEM
has the following additional limitations for PAC files:
- The dnsDomainIs function can't include the "_" and "*" characters.
- The shExpMatch function can't include the expressions "[0-9]", "?", "/^d", or "d+"
- The option to strip the path and query from the URI is not supported.