- Start here
- Planning tools
- BlackBerry UEM installation options
- Device management modes
- Designing a deployment plan for BlackBerry UEM
- Planning high availability for a BlackBerry UEM domain
- Architecture: High availability for BlackBerry UEM
- High availability and the BlackBerry UEM Core
- Configuring high availability for the management console
- High availability and the BlackBerry Connectivity Node
- Configuring database high availability using Microsoft SQL Server AlwaysOn
- Configuring database high availability using database mirroring
- Preinstallation and preupgrade requirements
- Hardware requirements
- Port requirements
- Server configuration
- Global IP ranges
- Mobile device configuration (Wi-Fi requirements)
- Reserved IP address ranges
- Outbound connections: BlackBerry UEM to the BlackBerry Infrastructure
- Outbound connections: BlackBerry UEM to the BlackBerry Dynamics NOC
- Outbound connections: Devices on a work Wi-Fi network
- Intranet connections
- How BlackBerry UEM selects listening ports during installation
- Supporting the deployment
Log files
The size of log files for
BlackBerry UEM
varies based on the number of devices in your organization's environment, the level of user activity on devices, and the logging levels that BlackBerry UEM
uses. It is a best practice to monitor and control the amount of disk space that the BlackBerry UEM
log files take up. For more information about configuring logging,