- 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
- BlackBerry Docs
- BlackBerry UEM 12.18
- Planning and Architecture
- BlackBerry UEM and BEMS Planning Guide
- Planning tools
- BlackBerry UEM Readiness Tool
BlackBerry UEM Readiness Tool
BlackBerry UEM
Readiness ToolYou can use the .
BlackBerry UEM
Readiness Tool to check system requirements before you run the BlackBerry UEM
setup application. The BlackBerry UEM
Readiness Tool is included with the BlackBerry UEM
software. You can also download the tool from my
AccountThe
BlackBerry UEM
Readiness Tool checks the following requirements:- Proxy server setting validation
- Minimum operating system requirements
- Minimum hard disk space
- Secure connection
- SRP connection
- Connection to theBlackBerry Dynamics NOC
- Required ports
- Account permissions
- Database validation
- TheBlackBerry UEMReadiness Tool does not check forMicrosoft .NET Framework4.5.
- TheBlackBerry UEMReadiness Tool performs a simple CONNECT to determine that ports are open. It does not validate that traffic will flow properly. For example, the Readiness Tool cannot detect issues related to traffic monitoring, SSL termination, or other systems that might reactively close sessions.