Skip Navigation
  1. BlackBerry Docs
  2. Whats new in BEMS
  3. What's new in BEMS

What's new in
BEMS

This topic details the new features that have been introduced in all supported releases of
BEMS
.
  • BlackBerry
    Docs
     service in
    UEM Cloud
     environment: Tenants that have enabled the
    BEMS
    Docs
     service in the
    UEM Cloud
     environment before May 2025, the Docs service will function as expected until December 1, 2025. Feature enablement for the
    Docs
     service has been disabled for all existing and new tenants. For more information, see the UEM Cloud Dynamics Docs service in UEM Cloud End-of-Life Notice.
  • Application Impersonation permission:
    Microsoft
     is deprecating the Application Impersonation permission in the
    Microsoft Exchange Online
     environment. Users will stop receiving email notifications to their devices when all of the following conditions are met:
    • Your environment is configured for on-premises
      BEMS
       or
      BlackBerry UEM Cloud
       with
      BEMS
       Cloud environments.
    • Mailboxes are on
      Microsoft Exchange Online
      , are enabled for modern authentication, and configured to use credential or passive authentication methods.
    • You are using
      Microsoft Exchange Web Services
       to communicate with
      Microsoft Exchange Online
    To avoid notification interruptions, make sure that you review your
    BEMS
     configurations and use certificate-based authentication for modern authentication or use
    Microsoft Graph
     to allow
    BEMS
     to communicate to users' mailboxes. For more information, see BEMS: Customers using Office 365 and EWS with Credential or Passive Authentication will stop receiving notifications. This change does not affect environments where BEMS is configured to use an on-premises Microsoft Exchange.

New in
BEMS
 version 3.8

The table below details the new features in this release. For information about the fixed and known issues in this release, see the BEMS 3.8 and BEMS Cloud Release Notes.
Feature
On-prem version
Cloud release date
Description
JRE 17 required
3.8.10.38
N/A
You must install
JRE
 17 on the servers where you will install
BEMS
 and set an environment variable that points to the
Java
 home location.
KCD enhancements
3.8.10.38
N/A
You can now specify a separate service account that is used to authenticate to
Microsoft SharePoint
 on behalf of the
BlackBerry Work
 app in your
Kerberos
 constrained delegation (KCD) and resource-based KCD configured environments. This feature provides enhanced security by not sharing the KCD user account credentials with the
BEMS
 service account.
Upgraded
Microsoft SQL Server
 driver
3.8.10.38
N/A
The
BEMS
 installer includes the upgraded
Microsoft SQL Server
 driver version 12.8.0. To allow
BEMS
 to communicate with the
SQL Server
, the installer prepopulates the Additional properties with the appropriate settings during the installation and upgrade process, and in the dashboard. No additional action is required by administrators.

New in
BEMS
 version 3.7 and
BEMS
 Cloud

The table below details the new features in this release. For information about the fixed and known issues in this release, see the BEMS 3.7 and BEMS Cloud Release Notes.
Feature
On-prem version
Cloud release date
Description
Firebase Cloud Messaging
3.7.11.11
June 2024
  • On-premises
    BEMS
     now supports the HTTP v1 API to send notifications to
    Android
     devices that run the
    BlackBerry Work
     and
    BlackBerry Connect
     apps.This feature requires an updated version of the
    BlackBerry Connect
     app (version 3.15). An updated
    BlackBerry Connect
     app will be released in the near future.
    In the UI, "Google Application Credentials" has replaced the "FCM key". This requires you to generate a private key in your FCM project and upload it to the
    BEMS
     Dashboard."
    For more information see Firebase Push Notifications.
    You must update your
    BEMS
     environment settings to use the HTTP v1 API before the end of June 2024 or
    Android
     devices will stop receiving notifications. For information on the HTTP v1 API, visit Migrate from legacy DCM APIs to HTTP v1.
  • BEMS
     Cloud now uses the HTTP v1 API to send notifications to
    Android
     devices that run
    BlackBerry Work
     app. For information on the HTTP v1 API, visit Migrate from legacy DCM APIs to HTTP v1.
UI changes
3.7.11.11
N/A
  • Installation
    : During the
    BEMS
     installation, the "Upload Credentials" screen has been removed. This removes the options to provide the
    BlackBerry
     Online Portal credentials for uploading
    BEMS
     logs to
    BlackBerry
     Support for troubleshooting, assign a cluster name to identify
    BEMS
     cluster and confirm the domain name. It also removes the ability to allow
    BEMS
     to send statistics information to BlackBerry.
  • Dashboard
    : In the "
    BEMS
     System Settings" section, the Troubleshooting section and the associated tools including "Upload Logs" and "Upload BEMS statistics" have been removed. In addition, the ability to periodically send statistics information (for example, version of
    BEMS
    , last restart time, system health) to
    BlackBerry
     has been removed.
Bug fixes
3.7.9.9
February 2024
Bug fixes that are described in the fixed issues section.
Email notification enhancements
3.7.2.2
December 2023
  • On
    Android
     devices, administrators can enable
    BEMS
     to deliver email push notifications with high priority to
    BlackBerry Work
    . This ensures that
    BlackBerry Work
     displays notifications for all new incoming emails in a time-sensitive manner.
    BEMS
     does not send high-priority messages for emails that are redirected to a subfolder, by default. For users to receive visual notifications for email messages that are received in their subfolders, they must be running
    BlackBerry Work
     3.13 or later and have the required policy setting enabled. This feature requires
    BlackBerry Work for Android
     version 3.15 or later and have the required policy setting enabled. For information on how to enable email subfolder notifications and high priority notifications, see "BlackBerry Work app configuration settings" in the BlackBerry Work administration content.
  • On
    iOS
     and
    Apple Watch
     devices,
    BEMS
     now supports sending the preview body of an email as a part of the
    BlackBerry Work
     email notifications. This feature requires
    BlackBerry Work for iOS
     version 3.14 or later and that the required email notification policy setting be enabled. For more information, see "BlackBerry Work app configuration settings" in the
    BlackBerry Work
     Administration content    .
Retrieve S/MIME certificates
N/A
December 2023
BEMS
 Cloud now supports searching for and retrieving recipients’ S/MIME certificates from LDAP certificate servers. This feature enables email encryption and signature functionality in the
BlackBerry Work
 app. This feature is disabled by default. You must contact BlackBerry Technical Support if you want to enable this feature.
Software requirements
3.7.2.2
N/A
BEMS
 is now compatible with the following:
  • Microsoft SQL Server
     2022
  • Cisco
     Unified CM for IM and Presence (CUCM) 14
For more information about the supported software, see the BEMS Compatibility Matrix.

New in
BEMS
 version 3.6 and
BEMS
 Cloud

The table below details the new features in this release. For information about the fixed and known issues in this release, see the BEMS 3.6 Release Notes or the BEMS Cloud Release Notes.
Feature
On-prem version
Cloud release date
Description
BEMS
 SSL Tech Tool
May 2023
N/A
The
BEMS
 SSL Tech Tool is no longer available. You can now update the
BEMS
 Certificate Password using the Jetty Util. For more information, see "Update the certificate passwords in BEMS" in the Configuring BEMS-Core content.
Bug fixes
3.6.9.10
N/A
Bug fixes that are described in the fixed issues section.
Turn off notifications for multiple users
3.6.1.1
N/A
You can now immediately stop notification for all devices associated with multiple users by importing a .csv file in the
BEMS
 Dashboard. This allows administrators to stop notifications to multiple users’ devices at once in the event that a device might have been lost or the user account was deleted from the
BlackBerry UEM
 server instance. Users can resubscribe to notifications if they are entitled to an app that can subscribe to notifications.
Email notification enhancements
3.6.1.1
July 2023
BEMS
 and
BEMS
 cloud now supports visual notifications for email messages that are received to users’ subfolders. This feature requires
BlackBerry Work
 version 3.13 or later. For information on how to enable email subfolder notifications, see "BlackBerry Work app configuration settings" in the BlackBerry Work administration content.
Security enhancements
3.6.1.1
N/A
The HTTP Security Header to the
BEMS
 Dashboard login page (https://bems_server:8443/) has been added to the BEMS Dashboard root directory.
LDAP configuration enhancements
3.6.1.1
N/A
You can now specify, in seconds, the timeout before the
BEMS
 connection attempt to the LDAP server and search times out in the following scenarios:
  • BEMS
    -Docs attempts to connect with the LDAP server and look up users and their membership in user groups.
  • BEMS
    -Mail queries the LDAP server and look for users from your organization’s Global Address List, their password expiry details, and S/MIME digital certificates from the users’ Active Directory.
Windows Extended Protection
3.6.1.1
N/A
BEMS
 now supports
Windows
 Extended Protection for
Microsoft Exchange Web Services
 (EWS) endpoints.
Software requirements
3.6.1.1
N/A
BEMS
 no longer supports the following software:
  • Microsoft Lync Server
     2013
  • Microsoft Exchange Server
     2013 SP1
  • Microsoft SharePoint
     2013
Before you upgrade to a supported version of
Microsoft SharePoint
, make sure to change the "Storage Provider" from an unsupported
Microsoft SharePoint
 version (for example, SharePoint2013) to
SharePoint
 or the Docs service might not function as expected. For more information on how to change the store provider, see Add a storage service. For information about supported
Microsoft SharePoint
 versions, see the Compatibility Matrix.