Known issues in UEM 12.19 and UEM Cloud (November 2023)
UEM
12.19 and UEM Cloud
(November 2023)Management console known issues
If you assign an app group to a user or group, when you edit that user or group you cannot change the disposition of the app group. (EMM-154392) Workaround : Remove the app group from the user or group, then create and assign a new app group with the desired disposition. |
If you activate both Android Enterprise and Android Management devices, then remove the Android Management connection from UEM , the console will display an incorrect count of the devices that will be removed. The count includes both Android Enterprise and Android Management devices. Only Android Management devices will be removed. (EMM-154081) |
In a UEM Cloud environment, if you turn on "Send SMS/MMS logs to the BlackBerry Connectivity Node" or "Send phone logs to the BlackBerry Connectivity Node" in an IT policy and the BlackBerry Connectivity Node is not installed, the following error displays: "An error was encountered. The profile could not be created." The error message should indicate that the settings could not be enabled because the BlackBerry Connectivity Node is not installed. (EMM-154049) |
In the Device tab of an org unit, if you try to configure a scheduled reboot, you cannot save the configuration unless you update all three sub-fields. (EMM-153890) |
When you view the device details for a user with more than one SIM, the expand and collapse arrow does not display as expected for SIM 1. You can still expand and collapse the SIM details. (EMM-153727) |
Entra ID directory synchronization reports do not display changes to users' group membership after the report runs. (EMM-153691) |
If a user deactivates a device with an Android Management activation type from the device settings, the device still displays as activated in the management console. (EMM-153468) |
When you send the Delete only work data command to an iOS device that is activated with User privacy, the request times out and an error message is displayed. (EMM-153457)Workaround : Use the Remove device command. |
When you assign an IT policy to devices that are running Windows 10 21H2, a "Command Failed" error might be displayed when you view the device actions and the IT policy is not applied. (EMM-151905) |
After you set up Chrome OS device management and click on the Network tab for an org unit, an error message stating that the profile could not be retrieved might be displayed. (EMM-151438) |
The value of the variable %ComplianceDynamicsEnforcementActionWithDescription% does not display as expected in compliance notification emails that are sent to users. (EMM-151056) |
When you try to re-enroll a DEP-enrolled device that doesn't have the BlackBerry UEM Client installed, the following error message is displayed: "An error was encountered. The device could not be migrated." (EMM-150780) |
When compliance override policies are applied, UEM might not send the compliance violation status to Entra ID conditional access. (EMM-148486) |
After a BlackBerry
Dynamics app migration with one certificate, the user might display in the management console with two certificates assigned to them. (EMM-147006) |
When you are configuring Entra ID 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 Entra ID Conditional Access page, and complete the configuration steps again. |
User, device, and app management known issues
In UEM 12.18 and earlier environments, if you enabled the "Allow wearables" setting to allow an Apple Watch to synchronize with the BlackBerry Work app and then upgraded to UEM 12.19, the Apple Watch will no longer synchronize with BlackBerry Work . (EMM-154314) Workaround : In the BlackBerry
Dynamics profile settings, disable the "Allow wearables" setting and enable the “Allow WatchOS apps" setting to allow Apple Watch synchronization with BlackBerry Work . |
Samsung devices that are activated with Android Enterprise Work space only and are assigned an Enterprise connectivity profile cannot send or receive SMS or MMS messages. (EMM-154287)Workaround : In the Enterprise connectivity profile settings, on the Android tab, select Container-wide VPN and add the com.android.mms.service and com.google.android.apps.messaging apps to the list of apps restricted from using BlackBerry Secure Connect Plus. |
If a Knox Service Plugin (KSP) policy is set to disable factory reset on a device and you send an IT command to wipe the device from BlackBerry UEM , the device will be unmanaged and cannot be reactivated or complete a factory reset. (EMA-17549) |
In dark site environments, when activating a Samsung Galaxy S 20 device running Android 11 with the Work and personal - full control (Android Enterprise ) activation type with the premium option enabled, the device activates with the Android Enterprise workspace instead of the Knox workspace. (EMA-16736) |
On Android devices, when you open the Work apps menu from the BlackBerry Dynamics Launcher , the app list loads, but an error message is displayed at the bottom of the screen. (EMM-151977) |
Chrome OS devices will not synchronize with UEM if they are in an org unit that has no child org units. (EMM-150375) |
You cannot synchronize Chrome OS users that have a duplicate username. (EMM-150357) |
If you don't configure an app server for Entra ID 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. |
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. |
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. |
During the Entra ID 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. |