Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Software-update: BlackBerry UEM 12.9

BlackBerry Unified Endpoint Management, UEM in het kort, kan gezien worden als de verdere ontwikkeling en samenvoeging van zowel BlackBerry Enterprise Server als Good Control MDM/MAM. Het product richt zich op mdm, het beheren van devices, en mam, het beheren van applicaties op deze devices. Daarnaast kan het worden geïntegreerd met andere producten om de functionaliteit uit te breiden, zoals BlackBerry Share, BlackBerry Workspaces en BlackBerry 2FA. BlackBerry UEM 12.9 is verschenen en de bijbehorende lijst met vernieuwingen ziet er als volgt uit:

What's new in BlackBerry UEM 12.9

Support Entrust IdentityGuard derived credentials
  • Derived credentials: Use Entrust IdentityGuard derived smart credentials for signing, encryption, and authentication for BlackBerry Dynamics apps and apps in the work space on Android work profile and Samsung KNOX Workspace devices. (JI 2221272)
  • Security patch settings can be assigned to devices from all vendors and all models in compliance profiles for Android devices: When you configure a compliance profile for Android devices, and you select the “Required security patch level is not installed” option, you can now select the “All vendors > All models” option in the list of allowed device models, which allows you to apply a security patch to every device that is using the Android OS. (JI 2241159)
  • Security patch version can be set to a day in a month in compliance profiles for Android devices: When you configure a compliance profile for Android devices, and you select the ‘Required security patch level is not installed’ option, you can now set the patch level based on the day in addition to the month and the year. (JI 2241159)
  • Android device password reset: The administrator can use the Specify device password and lock command for devices activated using the Work and personal - user privacy and Work and personal - user privacy (Premium) activation types. This command lets you create a device password and then lock the device. You must create a password that complies with existing password rules. To unlock the device, the user must type the new password. Only BlackBerry devices powered by Android 8.x and later devices support this command. (JI 2249999)
  • Enrollment: BlackBerry UEM now supports adding server and username information to Android zero-touch enrollment, simplifying end user activation. (JI 1674464)
  • Delete data from SD cards when wiping work space only devices: You have the option to delete all data on the SD card in a device when you delete all work data from an Android device with a work space only activation. (JI 1352406)
  • Control Android OS updates on Android work profile devices with a work space only activation: You can specify when to apply Android system updates to Android work profile devices with a work space only. Use the Device SR profile to specify rules by Android device model and OS version. (JI 1352406)
  • Ability to limit management on iOS devices: Administrators can now limit the amount of MDM-based control they have on iOS devices and improve user privacy for MDM enrollments with selective MDM controls within User Privacy activations. The new controls allow administrators to only control the parts of the device that are important to the organization, while preserving privacy for the user and their use of personal apps. (JI 1538477)
  • Ability to easily dismiss new apps for iOS devices: For iOS device users, users can now acknowledge and dismiss new apps listed in the New tab of the Work Apps app catalog by navigating to and away from the tab. Any installed apps that have an update will remain in the list. The loading time of the app catalog is now also improved. (JI 2354245)
  • iOS 11.3 Web Clip icons: You can now add Web Clip icons to a Home screen layout profile. (JI 2502748)
  • iOS 11.3 policy updates: The following new policies are available for iOS 11.3 devices (JI 2502748):
    • Show delayed software updates (supervised only)
    • Allow USB connections when device is locked (supervised only)
    • Require authentication before autofill of sensitive data (supervised only)
    • Allow automatic setup of new devices (supervised only)
    • Delay software updates (supervised only)
Management console
  • Rank app installation: For iOS and Android apps, you can rank the apps to control the order that they are installed when you assign them to devices. (JI 2483990)
  • Event notifications: Administrators can set event notifications to receive an email when the following events occur (JI 2191964):
    • Licenses are about to expire
    • The connection to the Apple DEP server is made
    • The connection to the Apple DEP server is lost
    • The connection with Microsoft Active Directory or LDAP server is lost
  • New Microsoft Intune app protection profile settings: The Microsoft Intune app protection profile includes new settings added in Intune by Microsoft to disable app PINs when the device is required to have password protection and to require minimum Android patch versions. (JI 2373165)
  • Enable user notification when a device has been activated: You can enable BlackBerry UEM to notify a user each time a device is activated on their account. The email notification is sent to the email address of the user account that was used to activate the device. By default, the email includes the device model, serial number, and IMEI. If the user receives a notification that they were not expecting, they should contact an administrator. (JI 2212924)
  • Last contact time: For devices that use BlackBerry Dynamics apps, on the device details page, a Last contact time column was added to the BlackBerry Dynamics apps list. The entries in the column display the latest time that the apps have contacted BlackBerry UEM. (JI 1684311)
BlackBerry Dynamics
  • Badge notifications: BlackBerry Dynamics users will now see a badge notification on the Apps icon in the launcher when new apps are assigned or existing custom apps are updated. (JI 2192742)
Installation and migration
  • Database consolidation: During an upgrade to BlackBerry UEM version 12.9 from BlackBerry UEM version 12.7 or later, the BlackBerry UEM 12.9 installer will consolidate the existing BlackBerry Control and BlackBerry UEM databases into a single BlackBerry UEM database. (JI 2369045)
  • Service consolidation: During an upgrade to BlackBerry UEM version 12.9 from BlackBerry UEM version 12.7 or later, the BlackBerry Control service is removed and consolidated with the BlackBerry UEM Core component. (JI 2369045).
Improved user experience during upgrades
  • BlackBerry Dynamics: Connectivity will remain enabled for BlackBerry Dynamics users while BlackBerry UEM and BlackBerry Connectivity Node servers are being upgraded. This feature is supported only when you are already using BlackBerry UEM 12.8.1 or later prior to upgrading to BlackBerry UEM 12.9. (JI 2219869)
  • BlackBerry Secure Connect Plus: Connectivity will remain enabled for BlackBerry Secure Connect Plus device users while BlackBerry UEM and the BlackBerry Connectivity Node servers are being upgraded. This feature is supported only when you are already using BlackBerry UEM 12.8.1 or later prior to upgrading to BlackBerry UEM 12.9. (JI 1685860)
UEM Notifications
  • Restrict UEM Notifications to a specific permission in BlackBerry UEM: Administrators must have the “Send email to users” permission in BlackBerry UEM to access UEM Notifications.
Fixed issues in BlackBerry UEM 12.9

Installation, upgrade, and migration fixed issues
  • In rare cases, if BlackBerry UEM had been upgraded from BES12 and then synchronized with Good Control, you might not have been able to update the BlackBerry Dynamics properties in BlackBerry UEM. (JI 2562790)
  • After a Good Control to BlackBerry UEM migration, a device that was not associated with any users might have displayed in the BlackBerry UEM Self-Service console. (JI 2506910)
  • When you upgraded from any version of BlackBerry UEM to BlackBerry UEM version 12.8, or when you added a new instance of BlackBerry UEM version 12.8 to your organization's domain, if you had activated Samsung KNOX using Samsung KNOX Mobile Enrollment, after the upgrade or install was complete, new device enrollment might have failed. When this issue occurred, "Error 4025" displayed on the device. For more information, visit to read KB48184. (JI 2531353)
  • When you were using the setup application to install BlackBerry UEM 12.8, the location of the log file folder did not display on the Folder locations screen. (JI 2497330)
  • When you installed the BlackBerry Router, the deployment log file was not written to the deployment folder. (JI 2522328)
  • After you performed the synchronization between Good Control and BlackBerry UEM, any app groups that users belonged to in Good Control still existed. In BlackBerry UEM, if you removed an app entitlement from a migrated app group that was assigned to the user, the user could continue to use the app because it was still a part of the app group that was assigned to the user in Good Control. (JI 2237889)
User and device management fixed issues
  • If your organization was using Entrust smart credentials on devices, after the user activated an Android device, the import certificate screen displayed three times. (JI 2568436)
  • If your organization was using Entrust smart credentials on devices, when the user was provisioning an app and clicked Next on the 'Certificate required' screen, the app might not have downloaded all required certificates (JI 2566492)
  • On Android devices, the total remaining memory value might have displayed incorrectly. (JI 2565570)
  • If your organization was using Entrust smart credentials on devices, after the user activated an iOS device, the import certificate screen displayed twice. (JI 2565424)
  • In rare cases, when a device communicated with the BlackBerry UEM Core, the BlackBerry UEM Core might not have been able to find the device so it sent a 410 response. This resulted in the device repeatedly trying to communicate with the BlackBerry UEM Core. (JI 2560445)
  • When you created an activation profile for iOS devices, if you selected the User privacy activation type and the Allow IT policy management, Allow email management, Allow Wi-Fi management, and Allow VPN management options, after you activated the device, the Work apps tab was not present in the BlackBerry UEM Client. (JI 2552423)
  • After you assigned an app to an iOS device, the device user did not receive a notification message. (JI 2549011)
  • After you enrolled an iOS DEP device using an email address and an activation password, the activation password did not expire even if you had enabled the “Activation period expires after the first device is activated" option in Settings > General settings > Activation defaults. (JI 2548802)
  • If you assigned a compliance profile to many users, the management console might have stopped responding when you tried to add a new device type to the “Allow selected device models” list. (JI 2547337)
  • Runtime app permissions were not updated for BlackBerry Dynamics apps on Android devices when permissions were configured from the app. (JI 2538415, JI 2529852)
  • If your organization was using a managed Google domain, you could not enroll a Samsung Tab E device that had a work profile. (JI 2537515)
  • An HTTP Status 400 error might have displayed on a device if the user left it idle on the BlackBerry Access SSAM page. (JI 2524859)
  • If a user's iOS device was enabled to use Touch ID , when the user installed and activated a BlackBerry Dynamics app, they might have been prompted for password authentication. (JI 2523767)
Management console fixed issues
  • After you used the Delete only work data command on an Android device that was activated using the MDM activation type, the device still displayed in the console. (JI 2573349, JI 2569105)
  • When you assigned a Device SR requirements profile to a user through a device group, on the device details screen the status of the profile might have displayed as "??????". (JI 2564213)
  • After you used the MDM controls activation type to activate a Samsung Galaxy 6 device, if you navigated to Apps > Personal apps, the model number of the device displayed instead of the name of the device. (JI 2553153)
  • When you sent an activation password to many users simultaneously, SQL deadlocks might have occurred. (JI 2550944)
  • You could not link a VPP license to an app entitlement if the URL for the app in the app store contained "/id". (JI 2547314)
  • When you synchronized a company directory, the "member of" attribute might have caused the synchronization to fail. (JI 2546278)
  • You could not select a proxy profile when you were creating or updating an enterprise connectivity profile. (JI 2543812)
  • An error message might have displayed when you viewed the user details for a BlackBerry OS device. (JI 2540204)
  • The management console might have stopped responding when you clicked Apps on the menu bar. (JI 2539299)
  • A file parser exception might have occurred when you added an internal BlackBerry Dynamics app in the management console. (JI 2533475)
  • When you created an activation profile for Android devices, if you selected the MDM Controls activation type, the following message displayed: "This activation type will be deprecated by Google in an upcoming Android release. You should prepare to switch to a different activation type for your organization's Android devices. (JI 2531732) For more information, visit to read article KB48386.
  • After you installed a new IT policy pack, incorrect characters might have displayed on the IT policy page. (JI 2525092)
  • When you created a SCEP profile for BlackBerry devices, the Subject and SAN fields did not display. (JI 2523941)
  • After you assigned an MDM profile to a user, if you set an activation password for the user and in the 'Activation option' list you selected the 'Device activation with specific activation profile' option and in the 'Activation profile' list you selected a Samsung KNOX with Google Play for Work activation profile, a Google User ID was not generated for the user. (JI 2521988)
  • When you created an Activation profile for an iOS device, if you selected the "Allow access to SIM card and device hardware information to enable SIM-based licensing" option, after you assigned the profile to a user, you couldn't activate the device if it was configured to use DEP. (JI 2512745)
  • Proxy profiles with PAC configurations and proxy profiles with manual configurations did not sync to Android devices. (JI 2512337)
  • You could not view VPP licenses usage for apps that were assigned to more than 600 devices. (JI 2413067)
  • If you used an unsupported SSL certificate, the management console would not open. (JI 2225075)
UEM Self-Service fixed issues
  • A single iOS device might have displayed as more than one device in UEM Self-Service. (JI 2530000, JI 2523750)
BlackBerry UEM API fixed issues
  • When you were using the BlackBerry UEM SOAP APIs, if an authentication failure against a CAP API occurred, the faultCode in the response from BlackBerry UEM was "PROXY_AUTHENTICATION_REQUIRED", which did not accurately describe the reason for the failure. This response was different from the one that Good Control used to provide when an authentication failure occurred. (JI 1620440)
Versienummer 12.9
Releasestatus Final
Besturingssystemen Windows Server 2012, Windows Server 2016
Website BlackBerry
Licentietype Betaald

Door Japke Rosink


17-07-2018 • 16:20

0 Linkedin

Bron: BlackBerry


Er zijn nog geen reacties geplaatst

Op dit item kan niet meer gereageerd worden.

Apple iPhone 12 Microsoft Xbox Series X LG CX Google Pixel 5 Black Friday 2020 Samsung Galaxy S20 4G Sony PlayStation 5 Nintendo Switch Lite

Tweakers vormt samen met Hardware Info, AutoTrack,, Nationale Vacaturebank, Intermediair en Independer DPG Online Services B.V.
Alle rechten voorbehouden © 1998 - 2020 Hosting door True