- Configuring BlackBerry UEM
- Changing the certificates that BlackBerry UEM uses for authentication
- Installing the BlackBerry Connectivity Node to connect to resources behind your organization's firewall
- Configuring BlackBerry UEM to send data through a proxy server
- Configure connections through internal proxy servers
- Connect to an SMTP server to send email notifications
- Connecting to your company directories
- Connecting BlackBerry UEM to Microsoft Entra ID
- Obtaining an APNs certificate to manage iOS and macOS devices
- Configure BlackBerry UEM for DEP
- Configuring BlackBerry UEM to support Android Enterprise devices
- Configuring BlackBerry UEM to support Android Management devices
- Extending the management of Chrome OS devices to BlackBerry UEM
- 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 BlackBerry server
- UEM migration best practices and considerations
- Connect to a source server
- Migrate IT policies, profiles, and groups from a source server
- Migrate users from a source server
- Migrate devices from a source server
- Configuring network communication and properties for 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
- Methods for routing traffic for BlackBerry Dynamics apps
- Configuring Kerberos authentication for BlackBerry Dynamics apps
- Integrating BlackBerry UEM with Cisco ISE
- Set up VPN using Knox StrongSwan for UEM dark site environments
- BlackBerry Docs
- BlackBerry UEM 12.19
- UEM Configuration Guide
- Configuring network communication and properties for BlackBerry Dynamics apps
- Configure Direct Connect using port forwarding
Configure Direct Connect using port forwarding
Direct Connect
using port forwarding- Configure a public DNS entry for eachBlackBerry Connectivity Nodeserver (for example, bp01.mydomain.com, bp02.mydomain.com, and so on).
- Configure the external firewall to allow inbound connections on port 17533 and to forward that port to eachBlackBerry Connectivity Nodeserver.
- If theBlackBerry Connectivity Nodeinstances are installed in a DMZ, ensure that the appropriate ports are open between eachBlackBerry Connectivity Nodeand any application servers that theBlackBerry Dynamicsapps need to access (for example,Microsoft Exchange, internal web servers, and theBlackBerry UEM Core).
- In the management console, on the menu bar, clickSettings > BlackBerry Dynamics > Direct Connect.
- Click aBlackBerry Proxyinstance.
- To turn onDirect Connect, select theTurn on Direct Connectcheck box. In theBlackBerry Proxy host namefield, verify that the host name is correct. If the public DNS entry you created is different from the FQDN of the server, specify the external FQDN instead.
- Repeat for allBlackBerry Proxyinstances in the cluster.To enable only someBlackBerry Proxyinstances forDirect Connect, create a newBlackBerry Proxycluster. All servers in a cluster must have the same configuration. For more information, see Manage BlackBerry Proxy clusters.
- ClickSave.