Zoom offers a BlackBerry Unified Endpoint Management (UEM) mobile client for Android and iOS devices that enforces security policies within the application. This document provides instructions for adding and configuring Zoom for BlackBerry policies within your UEM tenant.
Zoom for BlackBerry does not require any special configurations or components for deployment. Customers with an established BlackBerry UEM in place and are already configured to use Zoom within their network are able to deploy without additional requirements.
Zoom for BlackBerry network requirements are captured within our . No additional network configurations are required.
Log into the
Search for Zoom for BlackBerry
Click on the application
On the app page, select Start Trial\
Log into your BlackBerry UEM server
Select Apps in the side menu
In the dropdown, click Apps
In the apps list, select Zoom for BlackBerry
All configurable policies are available within the App Configuration screen. For an external list of all settings and their descriptions, refer to our .
The Zoom for BlackBerry app may require additional permissions before being used, which will be indicated by a yellow ⚠️ alert next to the app within the application list.
To confirm app permissions, perform the following steps:
Check the box on the left-hand side of the application name
Click the 🔄 button at the top of the page
Locate the Zoom for BlackBerry application within the list and select Approve app if required\
Read and confirm the requested app permissions
Refresh the applications page and confirm
For Bring Your Own Device (BYOD) policies, any Zoom links opened within BlackBerry Work (version 3.7.0 and higher) will open directly within Zoom for BlackBerry (version 5.8.0 and higher). Users can use both Zoom for BlackBerry and the standard Zoom Cloud Meetings mobile client on the same device without concern for data leakage if minimum versions are met.
Customers that are below BlackBerry Work version 3.7.0 or Zoom for BlackBerry version 5.8.0 can force links to open within Zoom for BlackBerry by completing the following steps:
Submit a request to Zoom support to enable the feature “Enforce Zoom for BlackBerry Client when using BlackBerry Access”
Log into your BlackBerry UEM server
Select Apps in the side menu
In the dropdown, click Apps
Once Zoom Support has enforced Zoom for BlackBerry and the above policy is in place, all Zoom links opened within BlackBerry Work will force BlackBerry Access to open the link within Zoom for BlackBerry regardless of application version.
Zoom for BlackBerry is compatible with additional data leakage prevention policies included with BlackBerry Dynamics management profiles. These policies are not configurable within the Zoom for BlackBerry application and must be configured through a BlackBerry Dynamics configuration profile, located within the Policies and profiles within your UEM Server. When configuring the profile, additional Data Leakage Prevention options are available as seen in the following images:
Click Settings
Click BlackBerry Dynamics
Under App Configuration, click the + icon to add a new deployment configuration\
Under the Name field, enter the name of the configuration
Set your desired settings for the app deployment across the various tabs\
Click Save to complete creating the configuration
Set up your app configuration hierarchy for the new custom policy in top-down order\
Select BlackBerry Access
Under App Configuration, click the + icon to name and add a new deployment configuration, or modify an existing configuration from the list\
Select Identify BlackBerry Access in User Agent under the General settings tab\
Further under the General settings tab, click to Enable 3rd Party Applications and enter zoomusbb,zoomus,zoommtg in the field below\
Save the policy
This section provides an overview of Auto Update functionality.
Auto update simplifies client version management for organizations, applies critical security updates as they become available, and will help ensure the Zoom client remains within the rolling 9-month release window once implemented.
Organizations and customers who use the automatic update feature have the ability to select either a fast or slow update schedule.
These releases will have the newest client features and updates available, but may experience occasional client instability.
Zoom will generally promote a new release from the Fast to the Slow audience within two weeks of release, unless the need for a critical fix is discovered during that period.
As an example, consider a client running version 5.10.0 when version 5.10.1 is released. There are two possible scenarios depending on the selected schedule:
Fast schedule, where there is no minimum version
The client will install version 5.10.1.
Slow schedule, where Zoom’s determined stable version is 5.10.0
The client will retain version 5.10.0
While version 5.10.1 is technically released and available, the slow schedule client will not install it because it has not yet been marked as the stable version by Zoom.
Zoom will deploy any critical security updates to both fast and slow channels. There is no ability to opt out of this behavior for either schedule.
Each update speed has its own minimum version threshold. Client updates trigger when the client’s version is lower than the minimum version for the configured update speed.
Once new updates are released, Zoom staggers the availability of the new client version across an increasing percentage of clients so all users will not receive the update at the same time.
This section details advanced configuration options regarding auto update functionality.
Zoom Recommendation For the best experience, Zoom recommends enabling auto update with no additional configurations.
Mass deployment meeting clients for IT Admins, like the MSI and PKG installers, won't automatically install updates unless configured to do so through MSI switches or Group Policy (GPO) for Windows devices, or a PLIST for Mac devices.
Standard meeting clients, like the EXE and DMG installers, do have automatic updates enabled by default, and users can opt into fast or slow updates at their discretion. Administrators can opt standard meeting clients out of automatic updates using Windows GPO or macOS PLIST parameters.
Warning
Zoom updated automatic update configuration parameters to support a new system with Zoom client version 5.10.3. All new automatic update keys begin with the prefix AU2_.
Enabling any AU2_ key will disable legacy parameters for: ZoomAutoUpdate, EnableSilentAutoUpdate,
Windows MSI deployments can include the AU2_EnableAutoUpdate parameter to enable automatic updates Administrators can configure MSI deployments to enable automatic updates using the parameter AU2_EnableAutoUpdate with a value of true in their install string. Automatic updates will be disabled if the MSI parameter is not included or set to false.\
Windows MSI and EXE deployments both respect the AU2_EnableAutoUpdate GPO setting to control automatic updates
MSI switches will not work on the Windows EXE installer, but both installations will respect the same AU2_EnableAutoUpdate GPO setting. Setting the GPO configuration to a positive string value (e.g., “true” or “1”) will enable automatic updates. Using a negative value (e.g., “false” or “0”) will disable the automatic update function.\
macOS PKG and DMG deployments both respect the AU2_EnableAutoUpdate PLIST parameter to control automatic updates
Enabling automatic updates will passively enable a parameter that quietly installs client updates without requiring user prompt. Updates will install on application restart unless otherwise prompted and will not interrupt ongoing meetings. After an update is applied, users will receive a notification their client was successfully updated.
Administrators can change the client behavior to prompt users to update Windows and MacOS administrators can change automatic background updates and prompt the user to approve the update installations. Using the AU2_EnableUpdateAvailableBanner parameter with a positive value (e.g., “true” or “1”) within the PLIST, install string, or GPO configuration will prompt the user to upgrade the client if an update is available. If this setting is not defined, it will default to false. Additionally, the client can prompt users to update when exiting a meeting or webinar if the AU2_EnablePromptUpdateForAU2 parameter is configured with a positive value (e.g., “true” or “1”) within the PLIST, install string, or GPO configuration. If this setting is not defined, it will default to false.
Post-update notifications can be turned off After an update is applied, users will receive a notification their client was successfully updated. Administrators can disable this feature with the AU2_EnableUpdateSuccessNotification parameter configured with a negative value (e.g., “false” or “0”) within the PLIST, install string, or GPO configuration.
Administrators can enforce specific update speeds with the AU2_SetUpdateChannel parameter in the install string, GPO, or PLIST settings. A value of “0” will use the slow schedule and a value of “1” will use the fast schedule. If this parameter is not defined, it will default to slow.
Zoom update settings located within General client settings can be hidden using the AU2_EnableShowZoomUpdates parameter set to a negative value (e.g., “false” or “0”). If this setting is not defined, it will default to true.\
AlwaysCheckLatestVersionCustomers using legacy parameters should update them to the AU2 values to avoid service disruption. Refer to our support documentation on mass deployment for Windows, Group Policy options, mass deployments for Mac devices, and enterprise auto update policies for more information.
Administrators can disable automatic updates and require manual updates, or disable updates completely Administrators can require users to manually update their client or disable client updates completely with the AU2_EnableManualUpdate parameter. If the AU2_EnableAutoUpdate parameter is disabled, configuring AU2_EnableManualUpdate with a positive value (e.g., “true” or “1”) will require users to manually check for and apply updates. Configuring this parameter with a negative value (e.g., “false” or “0”) will not allow the client to update under any circumstance. If this setting is not defined, it will default to true.\
Automatic updates can install on a schedule or when devices are idle Administrators can configure devices to look for device updates on a set schedule using the AU2_SetUpdateSchedule parameter with a string value. If this policy is configured with a valid string, the client will download the update package within the specified time period. The format of this string should be HHMM-HHMM, for example: "0900-1800" means 09:00 to 18:00, "1800-0400" means 18:00 to the next day 04:00. Alternatively, administrators can configure devices to update only when they are idle with the AU2_InstallAtIdleTime parameter. This setting is disabled by default and must be configured with a positive value (e.g., “true” or “1”) to enable. The AU2_InstallAtIdleTime parameter can be further defined when paired with the AU2_SafeUpgradePeriod parameter with a string value. If this policy is a valid string, the client will install auto updates within the specified time period when idle. The format of this string should be HHMM-HHMM, for example: "0900-1800" means 09:00 to 18:00, "1800-0400" means 18:00 to the next day 04:00.
Welcome to Device Management documentation.
This section provides technical implementation details, configuration workflows, and strategic practices designed specifically for administrators deploying Zoom solutions.
You'll find step-by-step procedures that streamline complex configurations, troubleshooting resources that accelerate resolution times, and practical examples that demonstrate real-world application scenarios.
Topics within this section connect technical specifications to measurable business outcomes, enabling you to architect solutions, support client implementations, and identify opportunities for feature expansion. Whether you're conducting initial deployments, optimizing existing environments, or evaluating advanced capabilities for your organization, this documentation serves as your definitive resource for successful Zoom product utilization.
