BlackBerry has rolled out a BlackBerry UEM 12.10 Maintenance Release 1. OpenJDK 8-based builds that are compatible with Java SE 8 are now supported as an alternative to using Oracle JDK 8. These builds and support are available from vendors such as Azul Systems (Zulu) or AdoptOpenJDK.
You can now set up a Factory reset protection profile for your organisation’s Android Enterprise devices that have been activated using the Work space only activation type. This profile allows you to specify a user account that can be used to unlock a device after it has been reset to factory settings, or remove the need to sign in after the device has been reset to factory settings.
On devices that are activated with Android Enterprise, you can set an update period for apps that are running in the foreground because by default, when an Android app is running in the foreground, Google Play cannot update it. You can also control how Google Play applies the changes to the device such as the user can allow the change, or the change occurs only when the device is connected to a Wi-Fi network.
You can now open the BlackBerry UEM Client and configure fingerprint authentication after BlackBerry Dynamics app activation is complete. All SSL connections between BlackBerry UEM and BlackBerry UEM Cloud and other internal and external systems now use TLS 1.2.
Ff you have obtained B2B apps using your Apple VPP account and added your VPP account to BlackBerry UEM, you can now assign those apps to users and groups in BlackBerry UEM.
iOS users can now allow the user to remove or add a cellular plan to the eSIM on the device. Specify whether the user is able to remove or add a cellular plan to the eSIM on the device. In addition, you can now specify whether the user can change settings related to their cellular plan.
There are also a lot of bug fixes to User and device management and the Management console.
