- 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
- Removing the BEMS software
- In a BlackBerry UEM environment, remove the BEMS server references from the BlackBerry Dynamics connectivity profile
In a BlackBerry UEM environment, remove the BEMS server references from the BlackBerry
Dynamics connectivity profile
BlackBerry UEM
environment, remove the BEMS
server references from the BlackBerry
Dynamics
connectivity profile- In theBlackBerry UEMmanagement console, on the menu bar, clickPolicies and profiles.
- ClickNetworks and connections > BlackBerry Dynamics connectivity profile.
- Click theBlackBerry Dynamicsconnectivity profile that you want to remove theBEMSinstance from.
- Click
. - If specified, in theAdditional serverssection, remove theBEMSinstances.
- If specified, in theIP address rangessection, remove theBEMSinstances.
- In theApp serverssection, if listed locate theBlackBerry Workapp entitlement.
- Click
beside the instance that has been decommissioned. - Repeat steps 7 and 8 for the following entitlements that might be listed:
- GoodEnterprise Services (com.good.gdserviceentitlement.enterprise)
- BlackBerry Connect(com.good.goodconnect)
- Feature-Docs Service Entitlement (com.good.feature.share)
- BlackBerryCore andMailServices (com.blackberry.gdserviceentitlement.coreandmail)
- BlackBerry PresenceService (com.blackberry.gdservice.entitlement.presence)
- BlackBerry Tasks(com.blackberry.gd.tasks)
- BlackBerry Notes (com.blackberry.gd.notes)
- ClickRemovebeside any additional entitlements that do not have aBEMSinstance associated with them.Only complete this step if aBEMSinstance is no longer required in your environment for BlackBerry Dynamics apps.
- ClickSave.