Skip Navigation

Fixed issues in BlackBerry UEM 12.17 MR1

Install, upgrade and migration fixed issues

If you were performing an installation in any language except English, the installation did not complete successfully when the installer couldn't find the administrator account name. (EMM-150264)

User, device, and app management fixed issues

The Device activations pop-up window accessed from the management console dashboard did not display data for activated devices. (EMM-151035)
When you enrolled a DEP device, the device might not have received the passcode enforcement policy before the passcode setup screen displayed. (EMM-151217)
When an
iOS
device was activated using the User privacy - User enrollment activation type, a message was displayed asking the user to upgrade to the same version of the
BlackBerry UEM Client
that was already installed on the device. (EMM-150754)
NullPointerException errors were written to the
UEM Core
log file when a user signed in to an enterprise enrolled
Chrome
OS device using a personal account. (EMM-150305)
For devices that you activated using the
Android Enterprise
- Full Control activation type, in the device's assigned IT policy, if you set the password complexity to High, and you then set the password complexity to Medium in the Work profile (all
Android
devices) section of the IT policy, the global setting took precedence over the Work profile setting and users were be forced to set a password with high complexity. (EMM-150252)
The
BlackBerry UEM Client
did not process any IT policy password complexity requirements on
Android Enterprise
activated
Android
12 devices on
BlackBerry UEM
12.16. (EMM-150137)
A security issue has been discovered that requires a
BlackBerry UEM
server upgrade followed by a reactivation for impacted MDM-enrolled
iOS
devices. For more information, visit support.blackberry.com to read article KB99869. (EMM-150054, EMM-146729)
The
BlackBerry UEM Client
did not retrieve or apply IT policies when the workspace was unlocked. (EMA-16864)
Android Enterprise
- Full Control dualDAR activation failed when using a custom encryption app on
Samsung
devices running
Android
10. (EMA-17112)
Policies and profiles did not get deployed on
macOS
12 (Monterey) devices after they were activated. (EMM-150189)

Management console fixed issues

You could not upload an app and an app configuration using the "Upload a template" feature. (EMM-150560)
You could not remove an internal version of the
BlackBerry Connectivity
app in the management console. (EMM-150678)
In an org unit, if you set the "Don't Allow Users to use Parallels Desktop" option to True, when you clicked Save, an error message displayed. (EMM-150764)
In a compliance profile, the list of restricted OS versions was not listed in numerical order. (EMM-150721)
The app list did not display if the name of one of the apps in the list contained a single quote ('). (EMM-150310)
In the compliance policy, on the
iOS
tab, if you select the 'Show only allowed apps on device'  option, add an app to the list, select the 'Restricted app is installed' option and add the same app to the Restricted apps list, when you remove the app from the Restricted apps list, it is also removed from the 'Show only allowed apps on device' list. (EMM-147897)

BlackBerry UEM
Core fixed issues

The import users function might have failed when you attempted to import a large number of users. (EMM-150324)
If a user's parameters didn't match what the
Google
domain was expecting, the user might not have been automatically created in the
Google
domain. (EMM-150306)

BlackBerry Proxy
fixed issues

When
BlackBerry Proxy
opened a connection with
BlackBerry Secure Connect Plus
, it took certificates from the keystore that are meant only for use with a
BlackBerry Connectivity Node
installation. If you did not upgrade
BlackBerry UEM
before the certificates expired, the
UEM Client
logged
BlackBerry Secure Connect Plus
errors that indicated failed certificate validation  (EMM-150706)
Activated endpoints might have waited 15 minutes before the
BlackBerry Proxy
returned that they were authenticated. (EMM-148672)