Skip Navigation

Known issues in
UEM
12.22 and
UEM Cloud

Installation and upgrade known issues
In certain circumstances, after you install
UEM
version 12.22 and you try to log in to the management console for the first time, the authentication process may take longer than expected and may stop with a "Login failed" error message. (EMM-157944)
Workaround
: Close the error message and try to log in again. The second login attempt will succeed.
In certain circumstances, in a
UEM Cloud
environment, when you open the
BlackBerry Connectivity Node
console for the first time after an upgrade, an HTTP Status 500 error displays and the console does not load as expected. (EMM-157113)
Workaround
: Refresh the page after the error displays.
Management console known issues
If you add a user to
UEM
and you do not enable the user for device management, you do not have to associate an email address with the user. If you later enable that user for device management and you try to migrate the user to a different
UEM
domain (Settings > Migration), the following error occurs because the user does not have an email address: “An error was encountered. The user cache could not be refreshed.” (EMM-157491)
Workaround
: Associate an email address with the user account and try to migrate the user again.
When you enable a
Chrome OS
user in the management console, the user is successfully enabled, but an error message displays indicating that the action cannot be performed. (EMM-157206)
When you view managed devices in the console, for
Chrome OS
devices, the
Chrome OS
icon does not display as expected in the OS column. (EMM-157196)
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 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
If a user’s
iOS
device is already activated with
UEM
and you enable that user for
Entra ID
conditional access, after the
Microsoft Authenticator
app is installed and the user brings the
UEM Client
to the foreground, the
Microsoft
authentication screen is not displayed to the user as expected. This is due to a
Microsoft
known issue. (EMA-18313)
Workaround
: Instruct users to force close the
UEM Client
and open it again.
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
UEM
, the device will be unmanaged and cannot be reactivated or complete a factory reset. (EMA-17549)
If you configured directory synchronization and enabled offboarding, when a user with more than one device activated with a user privacy activation type is supposed to be offboarded from
UEM
, the offboarding process does not complete successfully. As a result, the user and their devices are not removed from
UEM
. (EMM-158001)
If you use a .csv file to import directory user accounts into
UEM
, and you use the Group membership column to specify the group that you want to add each user to, during the import process you will receive a prompt asking you to select the groups that you want to add the users to, even though this information is already specified in the .csv file. If you make a selection in the prompt and click Import, the selection from the prompt will override whatever group memberships are specified in the .csv file. (EMM-157964)
Workaround
: Don't select any groups in the prompt and click Import. The imported users will be added to the groups that you specified in the .csv file.
If you use a .csv file to import directory user accounts into
UEM
, and you use the Directory UID column to specify a unique ID that
UEM
can use to validate each directory user (instead of each user's email address), if any of the Directory UID values are not valid, the import process does not complete and no users are imported. (EMM-157829)
If you configure IT policy rules to schedule an OS update for
iOS
devices at a specific date and time, when the device downloads the OS update, it may start installing the update ahead of the specified date and time. (EMM-157816)
If you configure compliance prompts for
BlackBerry Dynamics
apps for the "OS update not applied" (
iOS
and
Android
) or "Managed device attestation failure" (
iOS
) rules and you set the action for
BlackBerry Dynamics
apps to block or to delete
BlackBerry Dynamics
app data, then you remove and reassign the compliance profile, the
UEM Client
and other
BlackBerry Dynamics
apps may be blocked or deactivated and removed (depending on the selected action) without prompting the user first. (EMM-156895)
When you assign VPP apps with a user license to
Apple
DEP devices, if you assign the apps right after associating the VPP license to users, the apps might not install as expected because the app license cannot be retrieved. (EMM-156886)
If you assign a compliance profile with the
iOS
"OS update not applied" rule set to provide compliance prompts for
BlackBerry Dynamics
apps, then you change the compliance action for
BlackBerry Dynamics
apps from block to delete app data, or from delete data to block, prompts are not provided to the user before the enforcement action is applied. (EMM-156884)
When you configure a device profile with different wallpapers for the home screen and the lock screen and you assign the profile to an
iOS
device, the wallpaper configuration may not be applied to the device as expected. This issue occurs intermittently. (EMM-155689)
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
.
When you schedule an OS update for one or more supervised iOS devices, the update is delivered to devices but is not installed. This occurs intermittently and is due to an
iOS
known issue. (EMM-152977)
Chrome OS
devices will not synchronize with
UEM
if they are in an org unit that has no child org units. (EMM-150375)
If an authentication delegate app is configured in an assigned
BlackBerry Dynamics
profile, when a device user removes the authentication delegate app from their device and then restarts a different
BlackBerry Dynamics
app and uses the forgot password option, the forgot password option does not work and the user does not receive an error message. (GD-66829)
Workaround
: Instruct the user to install the authentication delegate app again.
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
UEM Client
and then open the
Microsoft Authenticator
app.
Performance
If you enable an encrypted connection and communication between UEM and Microsoft SQL Server, the encrypted connection can result in an increase in the UOS CPU on the computer that hosts the
BlackBerry UEM Core
. (EMM-155875)