Fixed issues in UEM 12.19 and UEM Cloud
UEM
12.19 and UEM Cloud
UEM 12.19 Quick Fix 8 (August 2024)
UEM
12.19 Quick Fix 8 (August 2024)Management console fixed issues
If you tried to add certain Android APKs that were published to Google
Play to UEM as internal app, the APK file could not be verified. (EMM-156847) |
Additional logging has been added for calls to Google APIs for publishing hosted applications. (EMM-156841) |
In specific circumstances, opening an app group resulted in an error indicating that the app group details could not be retrieved, and the app group did not open as expected. (EMM-156584) |
User, device, and app management fixed issues
When BlackBerry Secure Connect Plus made an authorization check for a device, if the checked failed, it would not attempt another authorization check for at least one hour. (EMM-156726) |
UEM 12.19 Quick Fix 6 (July 2024)
UEM
12.19 Quick Fix 6 (July 2024)Upgrade fixed issues
If you tried to upgrade to UEM 12.19, the upgrade process failed if JRE 8 was installed on the computer after you installed JRE 17, which is required for UEM 12.19 and later. Installing JRE 8 for other purposes caused issues with the path variable. (EMM-154349) |
Management console fixed issues
You might not have been able to log in to the management console if you enabled OCSP certificate-based authentication. (EMM-156040, EMM-156067) |
User, device, and app management fixed issues
If you used the UEM REST API Delete user command and specified users with active devices, the users’ data might have been deleted from the BlackBerry Infrastructure and from partner systems such as Google and Apple , but the user was not removed from the UEM environment. (EMM-156426) |
UEM 12.19 Quick Fix 7 (July 2024)
UEM
12.19 Quick Fix 7 (July 2024)Management console fixed issues
The "Allow Factory Reset" option in the Knox Service Plugin profile was labelled incorrectly. It has been fixed to read "Block Factory Reset". (EMM-155439) |
User, device, and app management fixed issues
If you configured the UCM Plugin configurations (premium) and VPN profiles (premium) settings in a Knox Service Plugin profile and assigned the profile to users, the Delete all device data command did not complete successfully when it was sent to users that were assigned the profile. (EMM-156118) |
Under certain circumstances, you might not have been able to create a UEM recovery account due to the UEM Configuration Tool expecting a tenant id value of 1. (SDS-1333) |
UEM 12.19 Quick Fix 6 (July 2024)
UEM
12.19 Quick Fix 6 (July 2024)Upgrade fixed issues
If you tried to upgrade to UEM 12.19, the upgrade process failed if JRE 8 was installed on the computer after you installed JRE 17, which is required for UEM 12.19 and later. Installing JRE 8 for other purposes caused issues with the path variable. (EMM-154349) |
Management console fixed issues
You might not have been able to log in to the management console if you enabled OCSP certificate-based authentication. (EMM-156040, EMM-156067) |
User, device, and app management fixed issues
If you used the UEM REST API Delete user command and specified users with active devices, the users’ data might have been deleted from the BlackBerry Infrastructure and from partner systems such as Google and Apple , but the user was not removed from the UEM environment. (EMM-156426) |
UEM 12.19 Quick Fix 5 (June 2024)
UEM
12.19 Quick Fix 5 (June 2024)User, device, and app management fixed issues
If you used the BlackBerry Web Services REST API to send a command to a device to wipe data but preserve the device's eSIM data, the eSIM data was not preserved as expected. (EMM-156093) |
UEM 12.19 Quick Fix 4 (May 2024)
UEM
12.19 Quick Fix 4 (May 2024)This Quick Fix release includes the fixes from any previous QF release.
User, device, and app management fixed issues
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:
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:
(EMM-153611) |
UEM 12.19 Quick Fix 3 and UEM Cloud (April 2024)
UEM
12.19 Quick Fix 3 and UEM Cloud
(April 2024)This Quick Fix release includes the fixes from any previous QF release.
User, device, and app management fixed issues
This release includes the following changes (the IT policy changes were also made available in the latest IT policy pack):
(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) |
UEM 12.19 Quick Fix 2 (March 2024)
UEM
12.19 Quick Fix 2 (March 2024)This Quick Fix release includes the fixes from any previous QF release.
Installation or upgrade fixed issues
After completing a scripted install of UEM , you could not log in to the management console. (EMM-155491) |
User, device, and app management fixed issues
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) |
UEM 12.19 Quick Fix 1 and UEM Cloud (January 2024)
UEM
12.19 Quick Fix 1 and UEM Cloud
(January 2024)Installation or upgrade fixed issues
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) |
Management console fixed issues
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) |
User, device, and app management fixed issues
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) |
UEM on-premises 12.19 and UEM Cloud (October 2023)
UEM
on-premises 12.19 and UEM Cloud
(October 2023)Management console fixed issues
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) |
User, device, and app management fixed issues
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) |