
In certain circumstances, when you configured automatic failover, the BlackBerry Monitoring Service assigned user data items
to the standby BlackBerry Enterprise Server and did not generate alarms. (DT 323341)
If you typed an invalid email address into the Manage Addresses field, the BlackBerry Monitoring Service saved the email
address as (). (DT 313341)
The default domain did not display when users logged into the BlackBerry device dashboard. (DT 265554)
The data attribute table in the Help window of the BlackBerry Monitoring Service was not formatted correctly. (DT 255008)
When the BlackBerry Monitoring Service received a new message, the BlackBerry Monitoring Service closed the Messages
window and did not display the message details. (DT 237654)
In the BlackBerry Monitoring Service console, the help text contained a spelling error in the word "test." (DT 237561)
When you restarted a BlackBerry Enterprise Server, the BlackBerry Monitoring Service generated messages that indicated a
failover had occurred. (DT 221109)
The BlackBerry® Client Access License field did not clearly indicate that the value represented the amount of licenses that
are still available. (DT 212137)
In an environment that included more than one BlackBerry Enterprise Server in the BlackBerry Domain, if you set thresholds
for user accounts at a global level and at a user level and the user accounts were associated with different BlackBerry Enterprise
Server instances, the BlackBerry Monitoring Service did not override thresholds at the global level with the thresholds at the
user level. (DT 169436)
When the alarm severity of a threshold for a data attribute of a BlackBerry device user that is in an alarm state changed, the
Alarm panel in the BlackBerry Monitoring Service console might not have updated the alarm state for the threshold. (SDR
289828)
BlackBerry Policy Service issues fixed in this release
When you moved a user account to another BlackBerry® Enterprise Server, the BlackBerry Policy Service processed its tasks
in the incorrect order and could not complete the move. (DT 616719)
When the Allow Other Browser Services IT policy rule was set to No, you could not always provision the BlackBerry device with
needed data services. In this release, you can set the PolicySRPWhitelist trait that you can use if the BlackBerry device cannot
be provisioned. (DT 523012)
Release Notes
BlackBerry Policy Service issues fixed in this release
18
Comentários a estes Manuais