- 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
- 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 upgrade BEMS and change the instant messaging service to Skype for Business Online
- 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 2010, 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
- Prerequisites: Connect for Skype for Business Online
- Presence prerequisites: Microsoft Lync Server, Skype for Business, and Skype for Business Online
- Prerequisites: BlackBerry Push Notifications service
- Supported Load Balancer affinity using Microsoft Exchange Server 2010
- Microsoft Exchange Web Services proxy support
- Microsoft Exchange Web Services Namespace Configuration
- Grant application impersonation permission to the service account
- Set Basic authentication for the Microsoft Exchange Web Services protocol
- Microsoft Exchange Autodiscover
- BlackBerry Push Notifications database requirements
- 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
- Appendices
- Appendix A: Migrating your Good Share database to BEMS-Docs
- 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
- Legal notice
- BlackBerry Docs
- BlackBerry Enterprise Mobility Server 3.1
- BEMS Installation Guide
- Prerequisites: Installing and configuring BEMS
- Prerequisites: BlackBerry Push Notifications service
- Microsoft Exchange Web Services Namespace Configuration
Microsoft Exchange Web
Services Namespace Configuration
Microsoft Exchange Web
Services
Namespace ConfigurationIf you have
Microsoft Exchange
Server
instances deployed in multiple Microsoft Active
Directory
sites, a unique internal Microsoft Exchange Web
Services
(EWS) URL must be configured for each site for the BlackBerry Push Notifications
service to work properly. Consider the following scenario: an environment with two Microsoft Active
Directory
sites and each site has two Client Access Servers (CAS).- Site 1: CAS 1, CAS 2
- Site 2: CAS 3, CAS 4
In this case, at least two unique internal
Microsoft Exchange Web
Services
URLs are required, one for Site 1 and one for Site 2. The URLs look something like the following:- Site1: https://site1cas.domain.com/EWS/Exchange.asmx
- Site2: https://site2cas.domain.com/EWS/Exchange.asmx
It is also valid to configure a unique internal
Microsoft Exchange Web
Services
URL for each client access server.Before modifying the internal
Microsoft Exchange Web
Services
URL for your client access servers, first check which Microsoft Active
Directory
site the client access servers are in and what the current internal Microsoft Exchange Web
Services
URL is set to by running the following command on the Microsoft Exchange
Server
:- Open a command prompt.
- Typenltest /dsgetdc:mydomain.com. PressEnter.
The “Dc Site Name” output parameter indicates the
Microsoft Active
Directory
site. For more information on how to use the NLTEST command, visit support.blackberry.com/community to read article 41948.For information on how to check the internal URL on a CAS server, visit support.blackberry.com/community to read article 41943.