Skip Navigation

Fixed issues in
UEM
12.21 and
UEM Cloud

Management console fixed issues
If you configured
UEM
to connect to more than one
Microsoft Active Directory
instance, when you searched for a user account to add from
Active Directory
,
UEM
might not have found the user account as expected because it searched the wrong
Active Directory
instance. (EMM-157231)
You could not assign apps to shared
iPad
groups when the browser was set to display the management console in German. (EMM-157187)
If you set your browser to display the management console in German, Spanish, or French, when you navigated to Users > Compliance violations, an error message displayed and no devices were listed. (EMM-157122)
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)
Under specific conditions, when you tried to update a hosted internal app, the update might have failed. (EMM-156828)
The DNS Domain Name field in a Managed domains profile did not accept a domain name longer than 6 characters. (EMM-156638)
When you opened an app group, an error displayed indicating that an unexpected error was encountered. (EMM-156584)
If you navigated to the Org Connect section in the management console, a notification message displayed indicating that the Org Connect plug-in requires
BBM Enterprise
, but the Next button was greyed out. This prevented you from registering Org Connect. If Org Connect was registered previously, you could not manage your connection. (EMM-156520)
In a
UEM Cloud
environment, if a user's
Active Directory
password contained certain German special characters (for example, ß or umlauts such as ä, ö, ü), the user could not log in to the management console. (EMM-156454)
In compliance profiles, if you selected "Restricted app is installed", the
iOS
Journal App was missing from the list of built-in apps. (EMM-156432)
In a
UEM Cloud
environment, if you made changes to an LDAP directory connection and saved, an error message displayed and you could not save your changes until you uploaded the LDAP server SSL certificate again. (EMM-156343)
In the compliance events view (Users > Compliance violations), if you selected a resolved event and clicked the Ignore button, the event was not removed from the view or added to the list of Ignored events. (EMM-156329)
When you added an app group to a device group with a required disposition and saved, the disposition changed to optional. (EMM-156069)
After you set up
Chrome OS
device management and clicked on the Network tab for an org unit, an error message might have displayed indicating that the profile could not be retrieved. (EMM-151438)
User, device, and app management fixed issues
If you set the expiration for delete commands to never expire, when you sent commands to delete work or device data to devices, the command expired after 24 hours. (EMM-157180)
In a
UEM Cloud
environment,
BlackBerry Dynamics
apps could not retrieve a user certificate using a SCEP profile configured with a dynamic SCEP challenge password. (EMM-157026)
Extra logging information has been removed from Debug logging. (EMM-156885)
When
BlackBerry Secure Connect Plus
or
BlackBerry Proxy
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)
If you assigned a VPN profile to
iOS
devices with the "Connection type" set to IKEv2, the "Authentication type" set to User credential, and “Enable per-app VPN” and “Allow apps to connect automatically” enabled, “Connect on Demand” was not enabled automatically in the VPN settings on iOS devices. Users had to manually enable this setting on their devices.
This is resolved in
UEM
version 12.21. Create a VPN profile for
iOS
devices with the configuration above, select “Enable VPN On demand”, and for “Enable per-app VPN”, specify a
Safari
domain. (EMM-156523)
If a device was out of compliance and the compliance action you configured was untrust, in certain circumstances,
UEM
removed the IT policy from the device. (EMM-156359)
When you sent the Delete all device data command to a device that was activated with an
Android Management
activation type, a SQL exception error might have displayed in the management console, but the command executed as expected on the device. (EMM-156357)