- About this guide
- What is BEMS?
- Preinstallation checklists
- Installation and upgrade
- Supported installation and upgrade paths
- Best practices: Preparing to upgrade
- Steps to install BEMS
- BEMS setup application modes
- Steps to upgrade BEMS
- Steps to upgrade BEMS and change to an alternate JRE
- Steps to upgrade BEMS and change the instant messaging service
- Steps to install BEMS instances into a cluster
- Prerequisites: Installing and configuring BEMS
- Core requirements
- Configure the Java Runtime Environment
- Prerequisites: Connect for Microsoft Lync Server and Skype for Business
- Preparing the computer that hosts BEMS for use with Microsoft Lync Server 2013 or Skype for Business
- BlackBerry Connect service database requirements
- Preparing the Microsoft Lync Server and Skype for Business topology for BEMS
- SSL certificate requirements for Microsoft Lync Server and 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
- 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: Microsoft Lync Server and 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.5
- BEMS Installation Guide
- Prerequisites: Installing and configuring BEMS
- Prerequisites: BlackBerry Push Notifications service
- Grant application impersonation permission to the service account
- Grant application impersonation permission using Microsoft Exchange Management Shell
Grant application impersonation permission using Microsoft Exchange Management
Shell
Microsoft Exchange Management
Shell
- OpenMicrosoft Exchange Management Shell.
- TypeNew-ManagementRoleAssignment -Name:<. For example,ImpersonationAssignmentName> -Role:ApplicationImpersonation -User:<ServiceAccount>New-ManagementRoleAssignment -Name:BlackBerryAppImpersonation -Role:ApplicationImpersonation -User:BEMSAdmin.
For more information on how to restrict Application Impersonation rights to specific users, organizational units, or security groups, visit the MSDN Library to see How to: Configure impersonation.