Fixed issues in

UEM

12.19 and

UEM Cloud

If you associated a user credential profile with a VPN profile and assigned the VPN profile to users, the VPN profile was not applied to the users as expected. (EMM-156008)

UEM

now uses the cRLSign bit field to verify that a certificate is trusted before checking the CRL. (EMM-155996)

This release includes the following changes to IT policy rules for

Android

password complexity:

The
Android
Global Password complexity IT policy rule now applies only to devices with
Android
OS 12 or later with a user privacy activation type (
Android Enterprise
and
Android Management
).
The
Android
Global Password requirements IT policy rule now applies to full control and work space only activation types (
Android Enterprise
and
Android Management
), and to user privacy activation types (
Android Enterprise
and
Android Management
) on devices with
Android
11 only.
The Password complexity IT policy rule in the
Android
Work profile section is no longer applicable as of
UEM Client
version 12.44.x.
The Password requirements rule in the Work profile section now applies to all
Android
activation types.

Note that the tooltip text to clarify the changes for these rules will not be visible in the UI until the next IT policy pack is released (currently planned for June 2024). (EMM-155761)

The

BlackBerry Dynamics

profile includes a new setting, Start conditional access enrollment after authentication broker is installed, that allows you to delay

Entra ID

conditional access enrollment for a user until the

Microsoft Authenticator

app is installed on the user’s device. (EMM-154216)

After upgrading

UEM

, the

UEM

root certificate was renewed even though it had not expired. As a result, some

Samsung

devices did not activate with

UEM

because the server certificate could not be validated. (EMM-154119)

The following options have been added to the

BlackBerry Dynamics

profile:

Enable Dynamics Launcher in UEM Client: This setting specifies whether the
BlackBerry Dynamics Launcher
icon appears in the
UEM Client
.
Enable Dynamics Launcher first time setup: This setting specifies whether the tutorial appears when the
BlackBerry Dynamics Launcher
appears for the first time in the
UEM Client
.

(EMM-153611)

This release includes the following changes (the IT policy changes were also made available in the latest IT policy pack):

The "Allow marketplace apps" IT policy rule has been added to allow you to control whether users can install marketplace apps. This rule is supported for
iOS
17.4 and later.
The functionality of the following
iOS
IT policy rules now extend to marketplace apps: Allow installing apps (supervised only), Allow removing apps (supervised only).
The functionality of the following
iOS
compliance rules now extend to marketplace apps: Show only allowed apps on the device, Restricted app is installed.

(EMM-155942)

When you tried to save a change to an IT policy that was assigned to a device group, the change could not be saved. (EMM-155566)

In a

UEM Cloud

environment, the

BlackBerry Cloud Connector

could not synchronize more than 1500 users for an LDAP directory group. This issue is resolved in this QF with a new release of the

BlackBerry Cloud Connector

. Use the setup application for the

BlackBerry Connectivity Node

(Settings > External integration > BlackBerry Connectivity Node setup) to update the

BlackBerry Cloud Connector

. (EMM-155301)

You could not change the disposition of an app group that was assigned to a user or device group. (EMM-154392)

When you assigned an app or app group to a user group, then viewed the group from the user view (navigate to the user then click the group), the disposition of the app or app group was listed as "Undefined" instead of the actual disposition setting. The same issue occurred if you assigned the app or app group to a device group and then opened the device group. (EMM-154391)

After completing a scripted install of

UEM

, you could not log in to the management console. (EMM-155491)

If a user was assigned an IT policy with "Enable activation lock" enabled for

iOS

devices, and the device had a null MEID value,

UEM

was not able to apply profiles or commands to the device. (EMM-155671)

When a user activated a device with an

Android Enterprise

activation type, an issue with

Google

API calls might have caused a delay in pushing assigned apps to the device. (EMM-155385)

Previously, if a user tried to activate an

Apple

DEP device and their device did not have a required OS version, the activation failed. The DEP activation process has been improved to prompt the user to upgrade the OS, if required. (EMM-153864)

If you tried to upgrade

UEM

on-premises from version 12.18 to 12.19 using the command line, the upgrade did not complete successfully. (EMM-154989)

In a

UEM Cloud

environment, if you navigated to the Org Connect section of the management console, an error message displayed indicating that you should verify that your organization uses

BBM Enterprise

, and you could not access the Org Connect UI. (EMM-155126)

Devices with activation lock enabled might not have displayed as expected in the Users > Apple Activation Lock screen. (EMM-154070)

In a

UEM

on-premises environment, when you integrated UEM with a Google domain to manage Chrome OS devices,

UEM

sent an incorrect ID in REST calls to

Google

, resulting in 400 errors. (EMM-155274)

Due to a specific error that could occur during the activation of an

Android

device, the

Google Play

device policy might not have been set correctly. As a result, the device could encounter issues with app deployment or other features. (EMM-155259)

After an OS update was installed on an

iOS

device,

UEM

might have continued to send update OS commands. (EMM-155104)

Hardware attestation failed on

Android

devices if certificate data was not recognized by

UEM

. (EMM-154980)

When a REST API was used to update

iOS

devices, some available updates for

iOS

devices were missing. (EMM-154517)

Shared

iPad

devices did not support

BlackBerry Secure Connect Plus

. (EMM-154285)

The RSR version was not displayed in

UEM

after an

iOS

device was updated to the RSR version. (EMA-17723)

Administrators could not delete a certificate from the CA certificate profile page. (EMM-153265)

The IT policy tooltip for "Allow screenshots in the work profile to be stored in the personal profile" was updated to indicate that screenshots must be stored in the personal profile if the option is selected. (EMM-152026)

If a SIEM connector was configured with TLS settings that did not match the syslog server settings, scheduled tasks did not run. (EMM-151864)

After you removed

Apple

VPP apps from a device and unassigned them from the user, the license consumption counts were not updated in the management console. (EMM-151299)

The work profile was not removed or the device was not reset to factory default settings if the Remove device command was sent while the device was offline. (EMA-17733)

SCEP enrollment was not completed during activation of

Android

devices when the CMS Algorithm Identifier Protection attribute was used. (EMA-17636)

Wi-Fi

profiles with the Enterprise security type were not applied to devices because the root CA or domain name were not applied to users devices. (EMM-153133)

BlackBerry Work

did not activate automatically when it was set as the primary authentication delegate on an

iOS

DEP device. (EMM-152855)

The activation password expiry date was not displayed correctly in

UEM Self-Service

when the language was set to French. (EMM-152389)

App shortcuts were displayed in the personal apps list in

UEM

after they were configured to appear in the

BlackBerry Dynamics Launcher

. (EMM-152316)

After you upgraded from

BlackBerry UEM

12.17.1(a) to 12.18, device groups that include RSR versions were not updated automatically. (EMM-152033)

For

iOS

devices, RSR versions might have been included in device groups that were intended to filter for a specific version and earlier or later versions. (EMM-152028)

Users could not edit notification permissions for apps on

Samsung

devices running

Android

13. (EMM-151936)