- About this guide
- What is BEMS?
- Preinstallation checklists
- Installation and upgrade
- Prerequisites: Installing and configuring BEMS
- Core requirements
- Configure the Java Runtime Environment
- Prerequisites: Connect for Skype for Business
- Preparing the computer that hosts BEMS for use with Skype for Business
- BlackBerry Connect service database requirements
- Preparing the Skype for Business topology for BEMS
- Prepare the initial computer hosting BEMS
- Prepare additional computers hosting BEMS
- Creating an additional trusted application pool
- Removing provisioning of the BEMS as a trusted application and trusted application pool
- Remove provisioning of the BEMS as a trusted application and trusted application pool
- SSL certificate requirements for Skype for Business
- Mutual TLS (MTLS) certificates
- Steps to create a CA-signed certificate for the local computer account using a CSR for BEMS
- Steps to create a CA-signed for the local computer account using automatic enrollment for BEMS
- Create a CSR for the local computer account for BEMS
- Obtain a CA-signed certificate from the CA server
- Import the CA-signed certificate on the CSR requesting BEMS
- Create a Personal Certificate for the local computer account for BEMS
- Export the CA-signed certificate and private key from the Microsoft Management Console
- Import the CA-signed certificate and private key to additional BEMS instances
- Presence prerequisites: Skype for Business
- Prerequisites: BlackBerry Push Notifications service
- Prerequisites: Cisco Unified Communications Manager IM and Presence Service requirements for Presence
- Prerequisites: Docs service
- Prerequisites: BlackBerry Directory Lookup, BlackBerry Follow-Me, and BlackBerry Certificate Lookup services
- Installing or upgrading the BEMS software
- Removing the BEMS software
- Troubleshooting BEMS installation or upgrade
- Appendices
- Appendix: AlwaysOn Availability support for SQL Server
- Steps to setup SQL Server for AlwaysOn availability
- Configure the BEMS services databases for AlwaysOn availability
- Enabling AlwaysOn availability group failover to subnets for the BEMS-Core and Mail services
- Enabling AlwaysOn availability group failover to subnets for the Connect service
- Enabling AlwaysOn availability group failover to subnets for the Docs service
- Architecture: BEMS notification flow using the Microsoft Graph API
- Architecture: BEMS
- Appendix: AlwaysOn Availability support for SQL Server
- BlackBerry Docs
- BlackBerry Enterprise Mobility Server 3.7
- BEMS Installation Guide
- Installation and upgrade
- Best practices: Preparing to upgrade
Best practices: Preparing to upgrade
When you upgrade from an earlier version of
BEMS
, consider the following guidelines: - Administrators must provide theirMicrosoft Active Directoryuser credentials to log in to theBEMSDashboard during the upgrade.
- If you are upgrading multiple instances in a cluster, you must upgrade each computer that hosts an instance ofBEMS.
- If multipleBEMSinstances point to a shared (common) database, new features are not available until all instances are upgraded. Running in a mixed-version environment for an extended period is not recommended.
- Special characters, for example semicolon (;), at sign (@), and slash mark (/), are not supported for theBEMSservice account.