Known issues in BlackBerry UEM 12.16.x
BlackBerry UEM
12.16.xItems marked with an asterisk (*) are new for this release.
Install, upgrade and migration known issues
* The BlackBerry Affinity Manager service displays on the Settings > Infrastructure page after an upgrade for both manual and scripted deployments. (EMM-150313) |
When you migrate an app, some of the app configuration settings might be lost. (EMM-142673) |
User, device, and app management known issues
Note that some of these issues are for the
BlackBerry UEM Client
and will be fixed in a future release.* Chrome OS devices will not synchronize with BlackBerry UEM if they are in an org unit that has no child org units. (EMM-150375) |
Changes to iOS apps can be missed if an install app command is in progress while a configuration change is being made. (EMM-149702) |
* On some devices that are configured for ZSO authentication, when the user signs in to the ZSO service through the browser, a notification prompt appears unexpectedly to choose a certificate for authentication. (EMM-147606)
Workaround : Choose the "_Cirrus_SCEP_Profile_" option. |
During the Azure AD Conditional Access enrollment flow, the user might be prompted to register the device twice. (SIS-15411)
Workaround : If the user is enrolling only in conditional access, they shouldn't open the Microsoft Authenticator app from the app store after they install it, instead they should switch to the BlackBerry UEM Client and then open the Microsoft Authenticator app. |
In a dark site environment, you can't create a VPN profile using the KnoxPluginService if your users are using a Samsung S20 device running Android 10 with Knox 3.5 and the device has been activated with the Work and personal - full control (Android Enterprise ) or Work and personal - user privacy (Android Enterprise ) activation types. (EMA-16739)
Workaround : Use Android 11 on the device or activate the device using the Work space only - (Android Enterprise ) activation type. |
In a dark site environment, if you try to use the Work and personal - full control (Android Enterprise ) activation type to activate a Samsung Galaxy S20 device running Android 11, the activation fails with a 502 error. (EMA-16736) |
Users might not be prompted to set a workspace password during Work and personal - user privacy (Android Enterprise ) activation. (EMA-16279) |
If your organization uses PKI and Entrust smart credentials together, users might need to enroll the PKI certificate multiple times on the same device (maximum of once per app). (GD-35783) |
The 'Do not allow Android dictation' option in the BlackBerry
Dynamics profile is used to stop dictation from keyboards; however, there are certain keyboards that allow dictation through other channels. (GD-35440)
Workaround : To help mitigate the issue, you can apply an IT policy with the 'Allowed input methods' option set to 'System only' or enforce installation of particular keyboards in the Android work profile. |
After an iOS user imports a certificate, the user is taken through the import process again. (G3IOS-18108) |
Management console known issues
BlackBerry 10 is no longer supported. For more information, see the announcement from BlackBerry . Even though you will see instances of BlackBerry 10 in the console, you should no longer use those pages. All instances of BlackBerry 10 will be removed In a future release of BlackBerry UEM . (EMM-150314) |
* If a file or image is deleted from the Google admin console for the Custom Avatar field, when the administrator tries to open the corresponding org unit in BlackBerry UEM , a failure occurs. (EMM-150506)
Workaround : In the Google admin console, change the Custom Avatar field from 'Locally applied' to 'Inherit from Google domain', save changes and then open the org unit. |
* In the Parallels desktop section of an org unit, an error is displayed if you make a change and click save without enabling the "This field must be set to true to acknowledge the notice message associated with the field 'plugin_vm_allowed' set to value 'true" option. No error message is displayed to indicate what caused the failure. (EMM-150499) |
* In the device tab of an org unit, if you schedule a device reboot and click Save, the save fails and no error message is displayed to indicate what caused the failure. Also incorrect strings are displayed in some of the fields. (EMM-150472) |
* When you change the 'Allowed Chrome OS languages' options in an org unit and click Save, an error displays. (EMM-150467) |
* The BlackBerry Affinity Manager service displays on the Settings > Infrastructure page after an upgrade for both manual and scripted deployments. (EMM-150313) |
* In the 'Devices by Platform' view in the dashboard, the 'Last contact date' is incorrect. Instead of displaying when the device or container was last contacted, the value that is displayed is when the device was first activated. (EMM-150258) |
When you assign a user certificate to a user, the option to assign the certificate to BlackBerry
Dynamics enabled devices is not always available. (EMM-150069)
Workaround : When you apply the certificate, choose the "Other managed devices" option. |
On the Add apps page, some app icons might not display. (EMM-149812) |
In Settings > Infrastructure > Server certificates, if you replace one of the certificates and add a description, the description is not saved. (EMM-149599) |
When you are configuring Azure AD Conditional Access, an error message might display and the configuration might not complete successfully due to a timeout. (SIS-15834)
Workaround : Click Ok on the error message, click Save on the Azure Active Directory Conditional Access page, and complete the configuration steps again. |
When compliance override policies are applied, BlackBerry UEM might not send the compliance violation status to Microsoft
Azure AD conditional access. (EMM-148486) |
If you don't configure an app server for Azure AD Conditional Access in the BlackBerry
Dynamics connectivity profile, Microsoft online device registration does not occur. (EMM-148453)
Workaround : In the BlackBerry
Dynamics connectivity profile, add an app server for Feature-Azure Conditional Access, direct the app server to the URL of your UEM Cloud instance, and use port 443. |
If you have added a custom image that displays in the top-left corner of the management console, when you log in to the console the default BlackBerry logo displays instead of the custom image. (EMM-146978) |
If you set up a BlackBerry Connectivity Node , and create a directory connection that has an apostrophe in the name, you can't delete the directory connection. (EMM-145132)
Workaround : Do not create a directory connection that has an apostrophe in the name. |
A message does not display in the console when a BlackBerry
Dynamics connectivity verification compliance violation occurs. (EMM-137201) |
A per-app VPN connection cannot be established on a device that is activated with the 'User privacy – User enrollment' activation type. (EMM-136964) |
The BlackBerry Connectivity app might not be delivered to an Android device that has been activated using the 'Work and personal - user privacy (Samsung Knox )' activation type and 'Google
Play app management for Samsung Knox Workspace devices' is enabled. (EMM-136648)
Workaround : Assign the .apk file to the device as an internal app and select the "Publish app in Google domain" option. |
When you add an internal app and an icon for the app, if you click the Refresh button on the Apps page, the icon does not display in the list of apps. (EMM-134638) |
BlackBerry Proxy known issues
BlackBerry Proxy
known issues* When you upgrade a BlackBerry Connectivity Node , the BlackBerry Proxy Service JvmMS and JvmMx values (Java Heap Variables) are overwritten, which results in the previous settings being lost. (EMM-149666)
Workaround : Manually reset the values. |
Activated endpoints can wait 15 minutes before the BlackBerry Proxy returns that they are authenticated. (EMM-148672) |
If the BlackBerry Proxy service receives a 503 error from the internal proxy server, BlackBerry Proxy does not try to reconnect to the BlackBerry Infrastructure . (EMM-147451)
Workaround : Restart the BlackBerry Proxy on the BlackBerry Connectivity Node . |