Fixed issues in BlackBerry UEM 12.18
BlackBerry UEM
12.18Installation and migration fixed issues
During installation, the end user license agreement did not display in Norwegian. (EMM-150771) |
User, device, and app management fixed issues
On iOS devices that were enrolled in DEP, users could not remove the UEM Client from the device if it was set as the authentication delegate for BlackBerry
Dynamics apps. (EMM-152603) |
After you upgraded to or installed BlackBerry UEM 12.17 MR1, the log files for iOS devices were not automatically stored in the default location, C:\Program Files\BlackBerry\UEM\Logs\device_logs. (EMM-151509) |
An error message was displayed when you tried to save a device wallpaper image in the Device settings for a Chrome OS org unit. (EMM-151488) |
When you activated a new Android Enterprise device or deactivated and reactivated an existing Android Enterprise device after upgrading to BlackBerry UEM 12.17 MR1, the device activation did not complete successfully because the CA certificate had been updated in UEM 12.17 MR1. (EMM-151249) |
Management console fixed issues
On the Users page, any Linked directory groups that the user is a part of did not display. (EMM-150812) |
In the Device tab of an org unit, if you scheduled a device reboot and clicked Save, the save failed and no error message was displayed to indicate what caused the failure. Incorrect strings were also displayed in some of the fields. (EMM-150472) |
Component fixed issues
Some BlackBerry UEM components had an expired certificate bound to them. (EMM-150729) |