Professional Documents
Culture Documents
Version 5.0
Release Notes
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
Note
This document is provided for informational purposes only, and does not constitute a binding legal document unless specifically incorporated by
reference into a binding legal agreement between you and Research In Motion (RIM). In the event that you enter into a binding legal agreement
with RIM, all provisions contained in such binding legal agreement shall apply, regardless of whether such provisions conflict with information
contained herein.
©2009 Research In Motion Limited. All rights reserved. BlackBerry®, RIM®, Research In Motion®, SureType® and related trademarks, names, and
logos are the property of Research In Motion Limited and are registered and/or used in the U.S. and countries around the world.
Adobe and Flash are trademarks of Adobe Systems Incorporated. AOL is a trademark of AOL LLC. BIG-IP is a trademark of F5 Networks, Inc.
Bluetooth is a trademark of Bluetooth SIG. IBM, Domino, Lotus, Lotus Notes, iNotes and Sametime are trademarks of International Business
Corporation. Java is a trademark of Sun Microsystems, Inc. Microsoft, Windows Server, Visual C++, Internet Explorer, and SQL Server are trademarks
of Microsoft Corporation. Novell and GroupWise are trademarks of Novell, Inc. RSA is a trademark of RSA Security. TrueType is a trademark of Apple
Inc. Kerberos is a trademark of the Massachusetts Institute of Technology. Wi-Fi is a trademark of the Wi-Fi Alliance. All other trademarks are the
properties of their respective owners.
The BlackBerry smartphone and other devices and/or associated software are protected by copyright, international treaties, and various patents,
including one or more of the following U.S. patents: 6,278,442; 6,271,605; 6,219,694; 6,075,470; 6,073,318; D445,428; D433,460; D416,256. Other
patents are registered or pending in the U.S. and in various countries around the world. Visit www.rim.com/patents for a list of RIM (as hereinafter
defined) patents.
This documentation including all documentation incorporated by reference herein such as documentation provided or made available at
www.blackberry.com/go/docs is provided or made accessible "AS IS" and "AS AVAILABLE" and without condition, endorsement, guarantee,
representation, or warranty of any kind by Research In Motion Limited and its affiliated companies ("RIM") and RIM assumes no responsibility for any
typographical, technical, or other inaccuracies, errors, or omissions in this documentation. In order to protect RIM proprietary and confidential
information and/or trade secrets, this documentation may describe some aspects of RIM technology in generalized terms. RIM reserves the right to
periodically change information that is contained in this documentation; however, RIM makes no commitment to provide any such changes, updates,
enhancements, or other additions to this documentation to you in a timely manner or at all.
This documentation might contain references to third-party sources of information, hardware or software, products or services including components
and content such as content protected by copyright and/or third-party web sites (collectively the "Third Party Products and Services"). RIM does not
control, and is not responsible for, any Third Party Products and Services including, without limitation the content, accuracy, copyright compliance,
compatibility, performance, trustworthiness, legality, decency, links, or any other aspect of Third Party Products and Services. The inclusion of a
reference to Third Party Products and Services in this documentation does not imply endorsement by RIM of the Third Party Products and Services or
the third party in any way.
EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOUR JURISDICTION, ALL CONDITIONS, ENDORSEMENTS,
GUARANTEES, REPRESENTATIONS, OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY
CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS OR WARRANTIES OF DURABILITY, FITNESS FOR A PARTICULAR PURPOSE
OR USE, MERCHANTABILITY, MERCHANTABLE QUALITY, NON-INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, OR ARISING FROM A
STATUTE OR CUSTOM OR A COURSE OF DEALING OR USAGE OF TRADE, OR RELATED TO THE DOCUMENTATION OR ITS USE, OR
PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES
REFERENCED HEREIN, ARE HEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY BY STATE OR PROVINCE. SOME
JURISDICTIONS MAY NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND CONDITIONS. TO THE EXTENT PERMITTED
BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE DOCUMENTATION TO THE EXTENT THEY CANNOT BE EXCLUDED AS
SET OUT ABOVE, BUT CAN BE LIMITED, ARE HEREBY LIMITED TO NINETY (90) DAYS FROM THE DATE YOU FIRST ACQUIRED THE
DOCUMENTATION OR THE ITEM THAT IS THE SUBJECT OF THE CLAIM.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO EVENT SHALL RIM BE LIABLE FOR ANY TYPE OF
DAMAGES RELATED TO THIS DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE,
SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED HEREIN INCLUDING WITHOUT LIMITATION ANY OF THE FOLLOWING
DAMAGES: DIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR AGGRAVATED DAMAGES, DAMAGES FOR
LOSS OF PROFITS OR REVENUES, FAILURE TO REALIZE ANY EXPECTED SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS
INFORMATION, LOSS OF BUSINESS OPPORTUNITY, OR CORRUPTION OR LOSS OF DATA, FAILURES TO TRANSMIT OR RECEIVE ANY DATA,
PROBLEMS ASSOCIATED WITH ANY APPLICATIONS USED IN CONJUNCTION WITH RIM PRODUCTS OR SERVICES, DOWNTIME COSTS, LOSS OF
THE USE OF RIM PRODUCTS OR SERVICES OR ANY PORTION THEREOF OR OF ANY AIRTIME SERVICES, COST OF SUBSTITUTE GOODS, COSTS
OF COVER, FACILITIES OR SERVICES, COST OF CAPITAL, OR OTHER SIMILAR PECUNIARY LOSSES, WHETHER OR NOT SUCH DAMAGES WERE
FORESEEN OR UNFORESEEN, AND EVEN IF RIM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, RIM SHALL HAVE NO OTHER OBLIGATION, DUTY, OR
LIABILITY WHATSOEVER IN CONTRACT, TORT, OR OTHERWISE TO YOU INCLUDING ANY LIABILITY FOR NEGLIGENCE OR STRICT LIABILITY.
THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVE OF THE NATURE OF THE CAUSE OF ACTION,
DEMAND, OR ACTION BY YOU INCLUDING BUT NOT LIMITED TO BREACH OF CONTRACT, NEGLIGENCE, TORT, STRICT LIABILITY OR ANY OTHER
2
Release Notes
LEGAL THEORY AND SHALL SURVIVE A FUNDAMENTAL BREACH OR BREACHES OR THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS
AGREEMENT OR OF ANY REMEDY CONTAINED HEREIN; AND (B) TO RIM AND ITS AFFILIATED COMPANIES, THEIR SUCCESSORS, ASSIGNS,
AGENTS, SUPPLIERS (INCLUDING AIRTIME SERVICE PROVIDERS), AUTHORIZED RIM DISTRIBUTORS (ALSO INCLUDING AIRTIME SERVICE
PROVIDERS) AND THEIR RESPECTIVE DIRECTORS, EMPLOYEES, AND INDEPENDENT CONTRACTORS.
IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALL ANY DIRECTOR, EMPLOYEE, AGENT,
DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR OF RIM OR ANY AFFILIATES OF RIM HAVE ANY LIABILITY ARISING FROM OR RELATED
TO THE DOCUMENTATION.
Prior to subscribing for, installing, or using any Third Party Products and Services, it is your responsibility to ensure that your airtime service provider
has agreed to support all of their features. Installation or use of Third Party Products and Services with RIM's products and services may require one
or more patent, trademark, copyright, or other licenses in order to avoid infringement or violation of third party rights. You are solely responsible for
determining whether to use Third Party Products and Services and if any third party licenses are required to do so. If required you are responsible for
acquiring them. You should not install or use Third Party Products and Services until all necessary licenses have been acquired. Any Third Party
Products and Services that are provided with RIM's products and services are provided as a convenience to you and are provided "AS IS" with no
express or implied conditions, endorsements, guarantees, representations, or warranties of any kind by RIM and RIM assumes no liability whatsoever,
in relation thereto. Your use of Third Party Products and Services shall be governed by and subject to you agreeing to the terms of separate licenses
and other agreements applicable thereto with third parties, except to the extent expressly covered by a license or other agreement with RIM.
The terms of use of any RIM product or service are set out in a separate license or other agreement with RIM applicable thereto. NOTHING IN THIS
DOCUMENTATION IS INTENDED TO SUPERSEDE ANY EXPRESS WRITTEN AGREEMENTS OR WARRANTIES PROVIDED BY RIM FOR PORTIONS
OF ANY RIM PRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION.
3
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
Related resources
Guide Information
BlackBerry Enterprise Server Feature and Technical Overview • BlackBerry® Enterprise Server features
• system architecture
• data and process flows
BlackBerry Enterprise Server Installation and Configuration Guide • system requirements
• installation instructions
BlackBerry Enterprise Server Upgrade Planning Guide • upgrade considerations
• environment-specific configurations
BlackBerry Enterprise Server Upgrade Guide • system requirements
• upgrade instructions
BlackBerry Enterprise Server Planning Guide • high availability considerations
• high availability configuration information
BlackBerry Enterprise Server Administration Guide • system setup and management
• BlackBerry device implementation instructions
BlackBerry Enterprise Server Monitoring Guide • monitoring configuration
• monitoring instructions
BlackBerry Enterprise Server Device Software Update Guide • BlackBerry Device Software update methods
• update instructions
Policy Reference Guide • IT policy rule descriptions
• application control policy rule descriptions
• configuration settings
BlackBerry Enterprise Solution Security Technical Overview • BlackBerry Enterprise Server security information
• security process flows
Product information
Do not use the Back, Forward, or Refresh buttons in your web browser when using the BlackBerry® Administration
Service, BlackBerry Monitoring Service, or BlackBerry MDS Application Console, because this might have an
unexpected impact on the settings you configure.
BlackBerry Enterprise Server version 5.0 supports upgrading an earlier version of the BlackBerry MDS Integration
Service to BlackBerry MDS Integration Service version 5.0, but you must follow certain configuration steps after you
install the BlackBerry MDS Integration Service version 5.0. For more information, see the BlackBerry Enterprise Server
Installation and Configuration Guide.
Research In Motion® has de-emphasized support for BlackBerry® Instant Messaging for Microsoft® Office Live
Communications Server 2005 for Windows® Messenger users. Research In Motion does not plan to release new
versions of the BlackBerry Instant Messaging Connector or collaboration client for Windows Messenger.
If the BlackBerry Attachment Service is hosted on a computer that uses Windows Server® 2008, the BlackBerry
Attachment Service does not support .mp3 audio files on BlackBerry devices, and the BlackBerry Attachment Service
does not support any audio file formats on BlackBerry® 7100 Series devices that support CDMA networks. You must
host the BlackBerry Attachment Service on a computer that uses Windows Server 2003 if you want the BlackBerry
Attachment Service to support .mp3 audio files on BlackBerry devices and all audio formats on BlackBerry 7100 Series
devices that support CDMA networks.
4
Release Notes
Feature Description
BlackBerry® Web Desktop Manager The BlackBerry Web Desktop Manager is a web application that permits users to manage their
BlackBerry devices. For example, users can activate BlackBerry devices, back up and restore data,
select messaging options, and synchronize data. The BlackBerry Web Desktop Manager includes the
BlackBerry Device® Manager.
BlackBerry Enterprise Server high BlackBerry Enterprise Server high availability consists of a minimum of two BlackBerry Enterprise
availability Server instances and the BlackBerry Configuration Database replicated across two database servers.
High availability is designed so that no single point of failure exists in the BlackBerry® Enterprise
Solution that could stop the messaging and application data flow to and from BlackBerry devices.
High availability for a distributed If you install multiple BlackBerry Enterprise Server components on different computers to create a
environment distributed environment, you can configure the components for high availability. High availability for
a distributed component requires that you install two or more instances of the component in your
organization's environment. When an instance stops responding, the other instances can take over.
Support for database mirroring If your organization uses Microsoft® SQL Server® 2005 SP2 or later, you can configure database
mirroring. Database mirroring requires a principal database, mirror database, and, optionally, a
witness. Although the BlackBerry Enterprise Server can contact the mirror database, it opens active
connections to the principal database only. If the principal database stops responding, the
BlackBerry Enterprise Server opens an active connection to the mirror database automatically.
Database mirroring provides fault tolerance for the BlackBerry Enterprise Solution.
Support for Microsoft SQL Server 2005 BlackBerry Enterprise Server version 5.0 supports Microsoft SQL Server 2005 Express Edition. The
Express Edition setup application can install Microsoft SQL Server 2005 Express Edition if your organization's
environment does not already include a database server.
Support for IBM® Lotus® Domino® version BlackBerry Enterprise Server version 5.0 supports Lotus Domino version 8.5 and Lotus Notes version
8.5 and IBM® Lotus Notes® version 8.5 8.5.
Support for Windows Server® 2008 BlackBerry Enterprise Server version 5.0 supports Windows Server 2008.
Enrolling certificates over the wireless You can configure the BlackBerry Enterprise Server to permit BlackBerry devices to enroll certificates
network over the wireless network. Permitting BlackBerry devices to enroll certificates is an alternative to
instructing users to send the certificates to themselves in an email message or using the certificate
synchronization tool in the BlackBerry® Desktop Software.
New method for installing and managing the You can use the BlackBerry Administration Service to install and manage the BlackBerry Device
BlackBerry Device Software and BlackBerry Software and BlackBerry Java Applications on BlackBerry devices.
Java® Applications In the BlackBerry Administration Service, you create software configurations to specify the versions
of the BlackBerry Device Software and BlackBerry Java Applications that you want to install or
update on BlackBerry devices, or remove from BlackBerry devices. You also use software
configurations to specify which applications are required, optional, or not permitted on BlackBerry
devices. When you create a software configuration, you must also specify whether users can install
applications that are not listed in the software configuration on their BlackBerry devices.
When you add a BlackBerry Java Application to a software configuration, you must assign an
application control policy to the application to specify what resources the application can access on
BlackBerry devices. If you permit users to install unlisted applications, you must create an application
control policy for unlisted applications that specifies what resources the applications can access on
BlackBerry devices.
If you assign more than one software configuration to a user account, all of the settings in the
multiple software configurations are applied to the BlackBerry device. The BlackBerry Enterprise
Server resolves conflicting settings using predefined reconciliation rules and prioritized rankings
that you can specify using the BlackBerry Administration Service.
For more information about installing and managing the BlackBerry Device Software on BlackBerry
devices, visit www.blackberry.com/go/serverdocs to see the BlackBerry Device Software Update
Guide.
BlackBerry MDS Application Console The BlackBerry MDS Application Console is a web administration console that you can use to
manage BlackBerry MDS Runtime Applications and BlackBerry® Browser Applications that reside in
the BlackBerry MDS Application Repository. You can use the BlackBerry MDS Application Console to
send requests to a BlackBerry MDS Integration Service to install or update BlackBerry MDS Runtime
Applications and BlackBerry Browser Applications on BlackBerry devices, or to remove the
applications from BlackBerry devices. You install the BlackBerry MDS Application Console when you
install the BlackBerry MDS Integration Service.
The BlackBerry MDS Application Console supports BlackBerry MDS Integration Service version 5.0
or later.
5
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
Feature Description
Support for new BlackBerry Browser BlackBerry Enterprise Server version 5.0 supports the following types of BlackBerry Browser
Applications Applications:
• browser channel push applications: An icon displays on the Home screen of BlackBerry devices
to indicate whether users viewed the latest version of the web content that the Browser Push
Engine pushed to the BlackBerry devices.
• browser cache push applications: The Browser Push Engine pushes web content to the cache of
the BlackBerry Browser on BlackBerry devices. To view the web content, users browse to the
appropriate web address using the BlackBerry Browser.
• browser message push applications: A message appears in the message list on BlackBerry
devices to provide a link to new or updated web content.
For more information about developing and customizing BlackBerry Applications, visit
www.blackberry.com/developers.
Follow-up flag on email messages Users with BlackBerry devices that are running BlackBerry Device Software version 5.0 or later can
flag email messages on their BlackBerry devices and set reminder times.
Forward calendar entries Users with BlackBerry devices that are running BlackBerry Device Software version 5.0 or later can
forward meeting invitations and calendar entries from their BlackBerry devices.
Manage personal folders Users with BlackBerry devices that are running BlackBerry Device Software version 5.0 or later can
add, delete, move, and rename personal folders from their BlackBerry devices.
View and manage personal contact Users with BlackBerry devices that are running BlackBerry Device Software version 5.0 or later can
subfolders view personal contact subfolders on their BlackBerry devices and change contact information.
Users can specify which contact subfolders that they want to synchronize to their BlackBerry devices
using the BlackBerry® Desktop Manager or BlackBerry Web Desktop Manager. You can limit the
number of contact subfolders that users can synchronize to their BlackBerry devices.
View and use contacts in public folders Users with BlackBerry Device Software version 5.0 or later can view and use contacts in public
folders from their BlackBerry devices, and copy the contacts to their contact lists. Users can only view
the public folders that they have the appropriate permissions for.
Users can specify which public folders they want to synchronize to their BlackBerry devices using the
BlackBerry Desktop Manager or BlackBerry Web Desktop Manager. You can limit the number of
public folders that users can synchronize to their BlackBerry devices.
Encrypt email messages using Lotus Notes You can configure the BlackBerry Enterprise Server to permit users to encrypt email messages using
encryption on the BlackBerry device Lotus Notes encryption. When users create, forward, or reply to messages, they can indicate whether
they want the BlackBerry Enterprise Server to encrypt the messages.
Support for Lotus Notes links In Lotus Notes, users can include document links, anchor links, view links, or database links
(application links) in their email messages. BlackBerry Enterprise Server version 5.0 supports Lotus
Notes links in the email messages that users receive on their BlackBerry devices. The BlackBerry
Enterprise Server retrieves the target information from the appropriate Lotus Domino server and
converts it into HTTP format. In plain text messages, the link appears as a web address. In HTML
messages, the link appears as an icon.
Users can click the HTTP links to view documents, folders, views, or database information in the
BlackBerry Browser. If the target information is stored on a secure Lotus Domino server, the
BlackBerry device might prompt users to type their login information after they click the link.
This feature is turned on by default.
For more information, visit www.blackberry.com/go/serverdocs to see the Support for IBM Lotus
Notes Links on BlackBerry Devices document.
Attachment support for the .wma file The BlackBerry Attachment Service now supports the .wma audio file format.
format
New IT policy rules For information about new IT policy groups and IT policy rules, visit www.blackberry.com/go/
serverdocs to see the Policy Reference Guide.
Changes to the BlackBerry Configuration BlackBerry Enterprise Server version 5.0 contains changes to the BlackBerry Configuration Database
Database schema schema. The changes occur in the following files:
• 4.5\UpgradeV20070831.sql
• 4.5\UpgradeV20071010.sql
• 4.5\UpgradeV20071030.sql
• 4.5\UpgradeV20080715.sql
• 5.0\UpgradeV20090122.sql
• 5.0\UpgradeV99990101.sql
6
Release Notes
Fixed issues
Key issues
SDR 187260 In previous versions of the BlackBerry Enterprise Server, if the BlackBerry Enterprise Server experiences a timeout with the
SDR 170644 Microsoft SQL Server while you are moving a user to a different BlackBerry Enterprise Server, the user might not be moved to
the BlackBerry Enterprise Server successfully.
In BlackBerry Enterprise Server version 5.0, this issue is resolved.
SDR 176909 After upgrading to BlackBerry Enterprise Server version 4.1 SP5 or later and starting the BlackBerry Enterprise Server, the
BlackBerry Enterprise Server might write incorrect information to the log files about a messaging server failover if the name of
the messaging server obtained from the BlackBerry profiles database does not match the case of the name of the messaging
server obtained from API calls.
In BlackBerry Enterprise Server version 5.0, this issue is resolved.
7
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
BlackBerry® Client for use with Microsoft® Office Live Communications Server 2005 version 2.1.18
SDR 208750 In certain circumstances, previous versions of the client might use an increased amount of memory on the BlackBerry device,
and the client might stop responding.
In the BlackBerry Client for use with Microsoft Office Live Communications Server 2005 version 2.1.18, this issue is resolved.
SDR 182032 In previous versions of the client, in certain circumstances, when a user sends a message in a conversation, the message might
display three times instead of once in the conversation on the recipient’s client.
In the BlackBerry Client for use with Microsoft Office Live Communications Server 2005 version 2.1.18, this issue is resolved.
SDR 182031 In previous versions of the client, in rare circumstances, if a user adds a contact to the contact list using the BlackBerry device,
the contact might not receive an Add Request notification.
In the BlackBerry Client for use with Microsoft Office Live Communications Server 2005 version 2.1.18, this issue is resolved.
SDR 136586 In previous versions of the client, if a user sends a request to the BlackBerry Collaboration Service to add a contact to their
contact list, and the request contains an invalid group ID or group name, the BlackBerry Collaboration Service does not respond
to the request and the client does not display an error message.
In the BlackBerry Client for use with Microsoft Office Live Communications Server 2005 version 2.1.18, this issue is resolved.
BlackBerry Client for use with Microsoft Office Live Communications Server 2005 version 2.2.19
SDR 301851 Automatic login is turned off by default.
SDR 228634 In previous French versions of the client, the emoticon selection list is not translated into French.
In the French version of the BlackBerry Client for use with Microsoft Office Live Communications Server 2005 version 2.2.19,
this issue is resolved.
BlackBerry® Client for use with Microsoft® Office Communications Server 2007 version 2.1.18
SDR 300315 In previous versions of the client, the client login timeout limit is 2 minutes.
In the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.1.18, the client login timeout is 5
minutes.
SDR 297572 In previous French versions of the client, users cannot change the status from Busy to Available.
In the French version of the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.1.18, this
issue is resolved.
SDR 208750 In certain circumstances, previous versions of the client might use an increased amount of memory on the BlackBerry device,
and the client might stop responding.
In the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.1.18, this issue is resolved.
SDR 185831 In previous versions of the client, if a user performs a contact lookup and adds a contact to their contact list from the lookup
results, the contact’s email address is added to the collaboration client, but not their SIP login name. If a contact’s email address
is not the same as the contact’s SIP login name, the contact does not function optimally.
In the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.1.18, this issue is resolved by using
an IT policy to disable lookups.
SDR 182031 In previous versions of the client, if a user adds a contact to the contact list using the BlackBerry device, the contact does not
receive an Add Request notification.
In the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.1.18, this issue is resolved.
BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19
SDR 301851 Automatic login is turned off by default.
SDR 301257 In previous Italian versions of the client, users can not set their status to Do not Disturb.
In the Italian version of the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19, this
issue is resolved.
SDR 300315 In previous versions of the client, the client login timeout limit is 2 minutes.
In the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19, the client login timeout is 5
minutes.
SDR 298904 In previous localized versions of the client, emoticon descriptions are not translated from English into French, Italian, German,
or Spanish.
In the localized versions of the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19, this
issue is resolved.
SDR 297496 In previous French versions of the client, emoticon descriptions and shortcuts are mapped to the wrong emoticons.
In the French version of the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19, this
issue is resolved.
8
Release Notes
BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19
SDR 286479 In previous versions of the client, when users change their location in the My Info screen, the location field does not update until
the user exits and returns to the My Info screen.
In the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19, this issue is resolved.
SDR 228634 In previous Italian versions of the client, the emoticon selection list is not translated into Italian.
In the Italian version of the BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.2.19, this
issue is resolved.
BlackBerry Controller
SDR 187253 In previous versions of the BlackBerry Enterprise Server, when the BlackBerry Controller restarts a BlackBerry Enterprise Server
SDR 170295 component, it causes debugging activities such as NSD to fail.
In BlackBerry Enterprise Server version 5.0, this issue is resolved.
9
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
Logging
SDR 187256 In previous versions of the BlackBerry Enterprise Server, if a user’s contact list exists on a different server than the user’s
SDR 180186 messaging account, the BlackBerry Messaging Agent does not write information about the user to the BlackBerry Messaging
Agent log file successfully.
In BlackBerry Enterprise Server version 5.0, this issue is resolved.
Monitoring
SDR 166533 In previous versions of the BlackBerry Enterprise Server, if you restart the BlackBerry Dispatcher with no SRP connection, the
dispSysHealthSRPTotalSecNotConnected SNMP object reports an incorrect value.
In BlackBerry Enterprise Server version 5.0, this issue is resolved.
Setup application
SDR 187227 In previous versions of the BlackBerry Enterprise Server, the setup application stops responding at the Preinstallation
SDR 169735 Checklist screen.
In BlackBerry Enterprise Server version 5.0, this issue is resolved.
SDR 157913 When upgrading from BlackBerry Enterprise Server version 4.1 SP4 to BlackBerry Enterprise Server version 4.1 SP5 or later, the
SDR 177085 following error might be displayed: "Failed to check the component GUID. Refer to the installation log for more information.
Setup will now exit."
In BlackBerry Enterprise Server version 5.0, this issue is resolved.
10
Release Notes
Known issues
Key issues
SDR 299265 If you specify the LDAP password using the BlackBerry Configuration Panel, the password is entered into the BlackBerry
Configuration Database in plain text. As a result, the BlackBerry Administration Server cannot read the password, and you
cannot log into the BlackBerry Administration Service using Windows authentication.
Workaround
Reinstall the BlackBerry Administration Service and specify the LDAP password.
SDR 293488 When you run the setup application, you are prompted to install Microsoft SQL Server 2005 Express Edition SP2. For
information about a security vulnerability with Microsoft SQL Server Express Edition SP2 that could impact the BlackBerry
Enterprise Server, visit www.microsoft.com to read advisory MS09-004. You must install the required update.
SDR 211317 If you are using the full recovery model, the size of the BlackBerry Configuration Database might be larger than expected, and
the transaction log file might increase in size erratically.
Workaround
Add a shrink log file task to your regular maintenance plan after performing a complete backup.
Activation
SDR 284923 The activation process for new BlackBerry devices can take several hours to complete if there are many unread checks in the
BlackBerry state database.
Workaround
Remove the unread checks in the BlackBerry state database before activating new BlackBerry devices.
SDR 283362 When moving a user list from one BlackBerry Enterprise Server to another, if some of the users are not initialized on the source
BlackBerry Enterprise Server, they are not recognized by the destination server. The destination BlackBerry Enterprise Server
stops responding while scanning the user list when it encounters the uninitialized user.
SDR 272457 In certain circumstances, after activating either a BlackBerry® Bold™ or BlackBerry® Storm™ device using the BlackBerry
Enterprise Server, users might be prompted to switch their device to use the same PIN number after connecting their
BlackBerry devices to the BlackBerry Desktop Manager.
SDR 270541 A wireless activation can take several hours if the user is switching to a new BlackBerry device and their email account contains
a large number of unread messages.
SDR 179376 Users cannot activate BlackBerry devices with BlackBerry Connect® version 4.0.
SDR 169257
SDR 171446 If you set the expiry time for an enterprise activation password to less than 48 hours (the default), the BlackBerry Messaging
Agent clears the password from the BlackBerry Configuration Database within a few seconds after you set the password. Users
receive an error message when they try to activate their BlackBerry devices.
Workaround
Do not set the expiry time for the activation password to less than 48 hours.
11
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
12
Release Notes
BlackBerry Client for use with Microsoft Office Live Communications Server 2005 version 2.1.18
SDR 295920 If a user adds a Windows Live Messenger contact to the contact list, the Windows Live Messenger contact appears offline.
Workaround
Instruct users to log out, and then log back in to the client.
BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.1.18
SDR 304781 If a user deletes a blocked contact, the blocked contact might remain in the contact list. When the user logs out, and then logs
back in to the client, the user receives an add request for the contact that they deleted.
SDR 304881 If a user specifies a custom location that meets the character limit of the Location field (approximately 256 characters), the user
can no longer specify their current location.
SDR 304713 A user can send messages to a blocked contact if the user has an existing conversation with the contact.
SDR 303950 If a user sends a message to an invalid contact, the error message "Failed to execute your last action" displays. The error
message does not specify that the contact does not have a valid ID or that the contact might reside in an external domain.
SDR 302669 In certain circumstances, after a user deletes a contact from the contact list, the user receives an add request for a contact the
SDR 281795 next time the user logs in to the client.
Workaround
Instruct users to clear the “Add to Contact List” check box and accept the add request.
SDR 300871 In certain circumstances, if a user has AOL® contacts on their contact list, the user cannot log in to the BlackBerry Client for
use with Microsoft Office Communications Server 2007.
SDR 279862 Users cannot log in to the BlackBerry Client for use with Microsoft Office Communications Server 2007 if their user name is in
the following format: <domain_name>\<user_name>, and if the Active Directory domain name is different than the SIP domain
name.
13
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
BlackBerry Client for use with Microsoft Office Communications Server 2007 version 2.1.18
SDR 257764 When using Windows NTLM authentication, an error occurs if two or more users try to log in to the BlackBerry Client for use
with Microsoft Office Communications Server 2007, or if one user logs out, and then quickly logs in.
Workaround
Set up Kerberos™ authentication or force forms-based authentication.
SDR 251895 Personal notes are not displayed in the BlackBerry Client for use with Microsoft Office Communications Server 2007 if they
contain special characters (for example, è, é, or $ ).
SDR 186430 There is no message indicating that adding distribution lists to contact lists using the BlackBerry Client for use with Microsoft
Office Communications Server 2007 is not supported.
14
Release Notes
BlackBerry Controller
SDR 301760 In previous versions of the BlackBerry Enterprise Server, if a BlackBerry Messaging Agent stopped responding, the BlackBerry
Controller tried to restart the BlackBerry Messaging Agent up to 10 times, and stopped trying to restart the BlackBerry
Messaging Agent after a 24-hour period. In BlackBerry Enterprise Server version 5.0, the limit is not reset when you perform a
manual failover of the BlackBerry Messaging Agent. As a result, the BlackBerry Controller does not try to restart the BlackBerry
Messaging Agent if 10 attempts have already been made in 24 hours.
Workaround
Restart the BlackBerry Controller manually.
SDR 214488 If the BlackBerry Controller creates multiple consecutive dumps on hung threads, the latest dump file overwrites the previous
dump file if the latest file is created in the same minute as the previous dump file; the dump files are named based on the minute
that they are created.
BlackBerry Dispatcher
SDR 207982 The APB engine loops if it is unable to write to a hard drive. As a result, a high amount of hard drive and CPU resources are used.
15
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
16
Release Notes
17
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
18
Release Notes
BlackBerry Router
SDR 293136 If a Wi-Fi enabled BlackBerry device is activated on the BlackBerry Enterprise Server and the BlackBerry device is associated
with a wireless access point, the BlackBerry Router writes a warning message to the BlackBerry Router log file.
19
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
Logging
SDR 301360 The location of each user’s Tasks should be listed as each user’s mail file in the BlackBerry Messaging Agent log file, but instead
the location is blank in the BlackBerry Messaging Agent log file.
SDR 293969 “Queuing” is spelled inconsistently across the BlackBerry Enterprise Server component log files. Certain log files use
“queuing” while other log files use “queueing”.
SDR 286202 The logging system might stop responding while reading the HKEY_PERFORMANCE_DATA value. The logging subsystem
might stop responding if the BlackBerry Enterprise Server is not able to read the registry.
SDR 277730 If you restart the BlackBerry Enterprise Server, the event log ID 20644 does not contain a description. This event log ID
references the NotesInitExtended API, which is a Lotus Domino runtime initialization process.
SDR 276975 In certain circumstances, after the network contact list is updated, the full name of a user is not listed in the BlackBerry
Enterprise Server log files. Only the first letter of the user's name appears in the log file.
SDR 259814 In certain circumstances, when monitoring the virtual address space statistic to identify potential causes of excessive memory
use, memory spikes are not identified in the BlackBerry Enterprise Server logs.
20
Release Notes
Security
SDR 301794 If you remove a user account and reactivate it at a later time, the user cannot complete the certificate enrollment process over
the wireless network. The BlackBerry Messaging Agent does not write any OTACR related messages to its log file.
Workaround
Restart the BlackBerry MDS Connection Service.
SDR 298237 During certificate enrollment over the wireless network, if the certificate authority returns more than one certificate in the
certificate chain, the BlackBerry device does not receive the certificates. The BlackBerry Synchronization Service writes the
following error message to the BlackBerry Synchronization Service log file: “Error Logging: DevMgmt.Configuration
Channel::A-260-ERROR_VERIFICATION_FAILURE.”
Workaround
Instruct users to cancel the certificate enrollment process and run it again.
SDR 265532 If you are performing RSA® certificate enrollment over the wireless network and the Certificate Administrator email address
setting specified on the server does not match the case of the sender's email address in the notification email message, the
certificate might not be sent to the BlackBerry device.
SDR 208366 When you enroll certificates over the wireless network, if your organization’s environment includes a Microsoft enterprise
certificate authority that requires Windows authentication, the BlackBerry MDS Connection Service limits the password for
the account to 14 characters.
SDR 148393 If you change the enterprise encryption algorithm from 3DES to 3DES and AES, and the Enterprise Service Policy is enabled,
users' BlackBerry devices are deactivated. When the encryption algorithm changes, a new encryption key request is generated
for all user accounts. If the Enterprise Service Policy is enabled when the encryption algorithm changes, and users' PIN
numbers are not specified in the allowed user list, the user account is deactivated.
Setup application
SDR 311864 If you select Microsoft Active Directory on the Setup Option screen, and you select “Use Windows Authentication” on the
Advanced Administration Settings screen, if you click Back on the DIIOP Settings screen, you cannot edit any settings on the
Advanced Administration Settings screen.
SDR 310792 If the pool name for the BlackBerry Administration Service in a high availability configuration is the same as the FQDN of a
computer in the BlackBerry Domain, traffic is routed to that computer only. The setup application uses the local computer’s
FQDN as the default pool name.
Workaround
Do not use a computer’s FQDN as the pool name.
SDR 307301 The BlackBerry Enterprise Server setup application does not install Microsoft .NET if you do not choose to install a local
Microsoft SQL Server 2005 Express Edition. If Microsoft .NET is not installed, you cannot run traittool.exe.
Workaround
Install Microsoft .NET manually.
SDR 304819 If you upgrade to BlackBerry Enterprise Server version 5.0 from an earlier EAP build of the BlackBerry Enterprise Server version
5.0, the setup application overwrites any previously configured LDAP port with the default LDAP port of 389.
Workaround
Specify the appropriate LDAP port during the setup process, or using the BlackBerry Configuration Panel.
SDR 304750 If you install the BlackBerry Enterprise Server and specify “BAS” as the BlackBerry Enterprise Server name, the installation
process stops responding.
Workaround
Use another name for the BlackBerry Enterprise Server.
SDR 303134 The BlackBerry Enterprise Server setup application stops responding for a few minutes while installing the Microsoft® .NET
framework on Windows 2003 R2 SP2 (64-bit).
SDR 301989 A warning is not displayed if you select the wrong Microsoft SQL Server port type during the setup process. The services for
the BlackBerry Administration Service (and all other Java services) cannot run if you select the wrong port type.
Workaround
Use the BlackBerry Configuration Panel to change the Microsoft SQL Server port, and in Windows Services, restart the
BlackBerry Administration Service services.
SDR 300449 You cannot complete the installation process if the LDAP password includes any of the following special characters:
exclamation mark (!), number sign (#), dollar sign ($), percent sign (%), caret (^), comma (,), ampersand (&), equal sign (=),
apostrophe (‘), quotation mark (“), semi-colon (;), chevrons (<>), vertical bar (|).
Workaround
Change the LDAP password so that it does not include these characters.
21
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
Setup application
SDR 295533 When installing the BlackBerry Enterprise Server, the following error message might display after one minute if you attempt
to start the BlackBerry Enterprise Server before specifying the authentication credentials: “15 minutes passed after startup;
turning off message quarantine code. You can permanently turn on message quarantine code by setting ForceQuarantine
registry value”.
Workaround
Specify the authentication credentials before starting the BlackBerry Enterprise Server.
SDR 291494 When you install the BlackBerry Enterprise Server, create the BlackBerry Configuration Database, and do not install the
BlackBerry Administration Service, at the Start Services dialog box, the setup application tries to prepare the non-existent
BlackBerry Administration Service and stops responding for a few minutes.
SDR 290745 If you select Microsoft Active Directory authentication when you run the setup application, the LDAP settings tab does not
display in the BlackBerry Configuration Panel.
Workaround
Change LDAP settings using the BlackBerry Administration Service.
SDR 286463 When installing BlackBerry Enterprise Server version 5.0, the Microsoft SQL Server cannot be located if it is setup with a non-
standard static TCP port.
Workaround
Create an open database connection from the BlackBerry Enterprise Server to the Microsoft SQL Server and specify the static
port.
SDR 281658 If you remove an existing BlackBerry MDS Integration Service and BlackBerry MDS Integration Service database, and you run
the setup application to install a new BlackBerry MDS Integration Service and BlackBerry MDS Integration Service database,
a SQL Query error displays when you click the Start Services button, and the installation process cannot complete successfully.
Workaround
Run the setup application again. Select an existing BlackBerry MDS Integration Service pool and database and complete the
installation.
SDR 281116 On the Administration Settings screen, the SSL password that you specify must contain a combination of letters and/or
numbers, and cannot contain any of the following special characters: exclamation mark (!), number sign (#), dollar sign ($),
percent sign (%), caret (^), comma (,), ampersand (&), equal sign (=), apostrophe (‘), quotation mark (“), semi-colon (;), chevrons
(<>), vertical bar (|).
SDR 280876 If you configure your environment for high availability, the setup application permits you to install different instant messaging
environments for the primary and standby BlackBerry Enterprise Server instances. This configuration is not supported by the
BlackBerry Enteprise Server.
SDR 280151 When upgrading the primary BlackBerry Enterprise Server in a high availability environment that is running an evaluation
version of the BlackBerry Enterprise Server version 5.0 software, you must use the evaluation CAL key.
SDR 277912 If you use the setup application to remove a BlackBerry Monitoring Service that you installed on a computer that is separate
from the computer that hosts the BlackBerry Enterprise Server, the removal process does not complete successfully.
Workaround
Remove the BlackBerry Monitoring Service using Add or Remove Programs.
SDR 265332 When upgrading from BlackBerry Enterprise Server version 4.1 SP6 to BlackBerry Enterprise Server version 5.0, in certain
circumstances, conflicts can occur between the user entries in the ITPolicyKeyMapping and UserConfig database tables.
These conflicts prevent the upgrade from completing successfully.
Workaround
Remove the following conflicting user entries from the ITPolicyKeyMapping table:
DELETE from ITPolicyKeyMapping
WHERE UserConfigId NOT IN (SELECT UserConfig.Id FROM UserConfig)
SDR 257785 The setup application indicates that Lotus Domino is not installed when you install the BlackBerry Administration Service on
a computer that is separate from the computer that hosts the BlackBerry Enterprise Server.
Workaround
Ignore the warning.
SDR 249701 If you install a BlackBerry Enterprise Server on the same computer as the BlackBerry Collaboration Service, and then you install
another instance of the BlackBerry Collaboration Service on the same computer without starting the first BlackBerry
Collaboration Service instance, the second BlackBerry Collaboration Service instance overwrites the information of the first
BlackBerry Collaboration Service instance in the BlackBerry Configuration Database.
Workaround
Start the BlackBerry Collaboration Service instance before you install subsequent BlackBerry Collaboration Service instances
on the same computer.
22
Release Notes
Upgrade
SDR 306304 After you upgrade the BlackBerry MDS Integration Service from version 4.1 SP4 to version 5.0, the BlackBerry MDS Integration
Service information does not display on the BlackBerry MDS Integration Service administration web page, and you cannot
access the administration web page.
Workaround
In the Windows Services, restart the services for the BlackBerry Administration Service and BlackBerry MDS Integration
Service.
SDR 301858 After you migrate user accounts from a BlackBerry Enterprise Server version 4.1 environment to a BlackBerry Enterprise Server
version 5.0 environment, the users cannot complete certificate enrollment over the wireless network on their BlackBerry
devices. BlackBerry devices display the following message to users: “The configuration channel is not available. Please contact
your system administrator.”
Workaround
1. Remove the user account.
2. Restart the BlackBerry MDS Connection Service. For more information, see SDR 301794.
3. Create a user account for the user.
4. Reactivate the BlackBerry device.
SDR 300855 If you are using a BlackBerry Enterprise Server version 4.1 SP5 that is associated with a BlackBerry Web Desktop Manager that
is installed on a separate computer, and you upgrade BlackBerry Enterprise Server version 4.1 SP5 to BlackBerry Enterprise
Server version 5.0, the setup application does not generate the LDAP server URL and LDAP Search Base correctly.
SDR 299885 If you upgrade to BlackBerry Enterprise Server version 5.0 from an EAP version of the BlackBerry Enterprise Server, an
incorrect web address for the BlackBerry Administration Service displays on the Console Address screen.
SDR 299755 If you upgrade BlackBerry Enterprise Server version 4.1 SP4 to BlackBerry Enterprise Server version 5.0, the previous service
license agreement in <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server is not replaced by the new
service license agreement. Both service license agreements remain in this folder.
Workaround
Delete the previous service license agreement.
SDR 298829 If you have a Microsoft SQL Server that has a BlackBerry Configuration Database (BESMgmt) that is earlier than version 5.0,
and you run the setup application and create a new BlackBerry Configuration Database on the Microsoft SQL Server (for
example, BESMgmt_50), you can choose to use an existing database if you run the setup application on a separate computer.
If you select the wrong BlackBerry Configuration Database (for example, BESMgmt instead of BESMgmt_50) and select No
when asked to confirm if you want to upgrade the database, then you change the database name (for example, to
BESMgmt_50) and select Next, you are not prompted to upgrade the database, and the list of active servers contains the name
of the BlackBerry Enterprise Server from the wrong BlackBerry Configuration Database.
Workaround
Close the setup application and run it again. Specify the correct BlackBerry Configuration Database name before clicking Next
on the database information page.
SDR 297656 You cannot change the standby BlackBerry Enterprise Server field if you upgrade the wrong BlackBerry Configuration
Database and return to the previous screen in the setup application to specify the correct BlackBerry Configuration Database.
Workaround
Close the setup application and run the setup application again.
SDR 297641 If you upgrade to BlackBerry Enterprise Server version 5.0, the display name for the BlackBerry Enterprise Server does not
appear on the Accounts and Folders screen in the setup application.
Workaround
Write down the display name for the BlackBerry Enterprise Server during the initial installation of the BlackBerry Enterprise
Server, or use a Microsoft SQL Server management tool to locate the display name in the ServerConfig table in the BlackBerry
Configuration Database.
SDR 290954 If you upgrade from BlackBerry Enterprise Server version 5.0 EAP or Beta and you specify a non-default pool name for the
BlackBerry Administration Service, the setup application does not display the correct web addresses for the BlackBerry
Administration Service and the BlackBerry Web Desktop Manager in the Console Addresses dialog box, and the shortcuts from
the Start menu are incorrect.
Workaround
Before you start the upgrade process, write down the web addresses for the BlackBerry Administration Service and the
BlackBerry Web Desktop Manager. After the upgrade process completes, update the shortcuts in the Start menu.
SDR 286838 If you install a BlackBerry Enterprise Server version 5.0 instance that shares a BlackBerry Configuration Database with a
SDR 283732 BlackBerry Enterprise Server version 4.1 SP4 instance, you must restart the BlackBerry Synchronization Service on the
BlackBerry Enterprise Server version 4.1 SP4 instance so that users associated with this instance can activate their BlackBerry
devices.
23
BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino
Upgrade
SDR 282889 In certain circumstances, after upgrading the BlackBerry Device Software on a BlackBerry device using the BlackBerry
Desktop Manager, not all service books are added to users' BlackBerry devices.
Workaround
Send the service books to users using the BlackBerry Enterprise Server.
SDR 265332 If a user entry exists in the ITPolicyKeyMapping table but not in the UserConfig table, you might not be able to upgrade the
BlackBerry Configuration Database.
SDR 189869 If you upgrade a BlackBerry MDS Connection Service instance that is located on a computer that is separate from the
computer that hosts the BlackBerry Enterprise Server, the setup application cannot detect that Microsoft XML Parser version
6.0 SP2 already exists on the remote computer and reinstalls Microsoft XML Parser version 6.0 SP1.
For more information about a security vulnerability in Microsoft XML Parser version 6.0 SP1, visit www.microsoft.com to read
KB954459. Install the required update.
DPI 222589 If you upgrade the BlackBerry MDS Integration Service to version 5.0, the BlackBerry Monitoring Service and the BlackBerry
MDS Integration Service do not store and cannot access the secure communications password. As a result, you cannot log in
to the BlackBerry Monitoring Service or the BlackBerry MDS Application Console, and you cannot view information for the
BlackBerry MDS Integration Service in the BlackBerry Administration Service. This issue does not occur if you install the
BlackBerry MDS Integration Service on the same computer as the BlackBerry Enterprise Server.
Workaround
Reset the secure communications password using the BlackBerry Configuration Panel.
DPI 222533 If your organization’s environment uses a version of the BlackBerry MDS Integration Service that is earlier than version 5.0,
and you have quarantined BlackBerry MDS Runtime Applications on BlackBerry devices, and you upgrade the BlackBerry MDS
Integration Service to version 5.0, you cannot remove the quarantine on the BlackBerry MDS Runtime Applications.
Workaround
Reinstall the quarantined BlackBerry MDS Runtime Application on the BlackBerry devices.
DPI 221381 If you upgrade the BlackBerry MDS Integration Service to version 5.0, when the BlackBerry MDS Runtime activates with the
BlackBerry MDS Integration Service, the previously assigned application settings change to new default application settings.
Workaround
If necessary, assign a custom IT policy to user accounts.
DPI 175406 If you upgrade the BlackBerry MDS Integration Service to version 5.0, a “Vendor mismatch” error displays when the BlackBerry
MDS Integration Service provisions signed BlackBerry MDS Runtime Applications that already exist in the BlackBerry MDS
Application Repository.
Workaround
Republish the signed applications to the BlackBerry MDS Application Repository.
DPI 174220 If the BlackBerry MDS Runtime version 4.5 or later is installed on BlackBerry devices, and you upgrade the BlackBerry
Enterprise Server and the BlackBerry MDS Integration Service to version 5.0, default application settings are applied to the
BlackBerry devices when the BlackBerry MDS Runtime activates with the BlackBerry MDS Integration Service version 5.0. The
BlackBerry MDS Integration Service might install BlackBerry MDS Runtime Applications on BlackBerry devices again.
Workaround
Verify that the appropriate application settings are configured in the IT policy that you assign to groups and user accounts. If
you upgraded a BlackBerry MDS Integration Service earlier than version 4.1 SP5 to version 5.0, republish the signed
applications to the BlackBerry MDS Application Repository again.
24
Release Notes
25