BlackBerry Enterprise Server for IBM Lotus Domino

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. Send us your comments on release notes: www.blackberry.com/docsfeedback Document ID: 23749533 Last modified: 26 August 2009

3

BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino

Related resources
Guide BlackBerry Enterprise Server Feature and Technical Overview Information • • • • • • • • • • • • • • • • • • • • • • BlackBerry® Enterprise Server features system architecture data and process flows system requirements installation instructions upgrade considerations environment-specific configurations system requirements upgrade instructions high availability considerations high availability configuration information system setup and management BlackBerry device implementation instructions monitoring configuration monitoring instructions BlackBerry Device Software update methods update instructions IT policy rule descriptions application control policy rule descriptions configuration settings BlackBerry Enterprise Server security information security process flows

BlackBerry Enterprise Server Installation and Configuration Guide BlackBerry Enterprise Server Upgrade Planning Guide BlackBerry Enterprise Server Upgrade Guide BlackBerry Enterprise Server Planning Guide BlackBerry Enterprise Server Administration Guide BlackBerry Enterprise Server Monitoring Guide BlackBerry Enterprise Server Device Software Update Guide Policy Reference Guide

BlackBerry Enterprise Solution Security Technical Overview

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.

New in this release
Feature BlackBerry Administration Service Description The BlackBerry Administration Service is a web application that connects to the BlackBerry Configuration Database. You can use the BlackBerry Administration Service to manage the BlackBerry Domain, which includes user accounts and features that you can use to control BlackBerry devices. The BlackBerry Domain consists of a single BlackBerry Configuration Database and all of the BlackBerry Enterprise Server instances that use it. The BlackBerry Administration Service replaces the BlackBerry Manager as the administration console for the BlackBerry Enterprise Server and BlackBerry Enterprise Server components.

4

Release Notes

Feature BlackBerry® Web Desktop Manager

Description 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 availability consists of a minimum of two BlackBerry Enterprise 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. If you install multiple BlackBerry Enterprise Server components on different computers to create a 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. 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. BlackBerry Enterprise Server version 5.0 supports Microsoft SQL Server 2005 Express Edition. The setup application can install Microsoft SQL Server 2005 Express Edition if your organization's environment does not already include a database server. BlackBerry Enterprise Server version 5.0 supports Lotus Domino version 8.5 and Lotus Notes version 8.5. BlackBerry Enterprise Server version 5.0 supports Windows Server 2008. You can configure the BlackBerry Enterprise Server to permit BlackBerry devices to enroll certificates 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.

BlackBerry Enterprise Server high availability

High availability for a distributed environment

Support for database mirroring

Support for Microsoft SQL Server 2005 Express Edition Support for IBM® Lotus® Domino® version 8.5 and IBM® Lotus Notes® version 8.5 Support for Windows Server® 2008 Enrolling certificates over the wireless network

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 Support for new BlackBerry Browser Applications

Description BlackBerry Enterprise Server version 5.0 supports the following types of BlackBerry Browser 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 Forward calendar entries Manage personal folders View and manage personal contact subfolders 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. 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. 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. Users with BlackBerry devices that are running BlackBerry Device Software version 5.0 or later can 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 encryption on the BlackBerry device Support for Lotus Notes links You can configure the BlackBerry Enterprise Server to permit users to encrypt email messages using 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. 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 format New IT policy rules Changes to the BlackBerry Configuration Database schema The BlackBerry Attachment Service now supports the .wma audio file format. For information about new IT policy groups and IT policy rules, visit www.blackberry.com/go/ serverdocs to see the Policy Reference Guide. BlackBerry Enterprise Server version 5.0 contains changes to the BlackBerry Configuration Database 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 SDR 170644 In previous versions of the BlackBerry Enterprise Server, if the BlackBerry Enterprise Server experiences a timeout with the 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. BlackBerry Administration Service SDR 213034 SDR 140695 In previous versions of the BlackBerry Enterprise Server, if you turn off S/MIME message processing for a BlackBerry device using the BlackBerry Enterprise Server administration console, S/MIME message processing turns on for the BlackBerry device a short time later. In BlackBerry Enterprise Server version 5.0, this issue is resolved. SDR 187251 SDR 150208 In previous versions of the BlackBerry Enterprise Server, if the UNID of BlackBerry device users in the Lotus Domino directory changed (for example, users were accidentally deleted and restored in the directory by copying person documents from a backup into the directory), the BlackBerry Enterprise Server cannot find the users by their UNID. The BlackBerry Enterprise Server then searches for the users by name and might locate the wrong user. As a result, users may be associated with incorrect user accounts. In BlackBerry Enterprise Server version 5.0, this issue is resolved. BlackBerry Attachment Service SDR 153315 In previous versions of the BlackBerry Enterprise Server, if you upgrade a remote BlackBerry Attachment Service, the maximum file size settings that you configure change to the default values. In BlackBerry Enterprise Server version 5.0, this issue is resolved. BlackBerry® Client for IBM® Lotus® Sametime® 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 IBM Lotus Sametime version 2.1.18, this issue is resolved. SDR 197626 In previous versions of the client, if a user sends a file to a contact whose BlackBerry device is locked, an incorrect file transfer message displays in the recipient’s client, or an uncaught exception displays and the recipient is logged out of the client. In the BlackBerry Client for IBM Lotus Sametime version 2.1.18, this issue is resolved. SDR 177400 In previous versions of the client, if a user adds a contact from the client’s contact list to the main contact list on the BlackBerry device using the Add Person feature, some of the contact’s information is not added to the contact list entry. In the BlackBerry Client for IBM Lotus Sametime version 2.1.18, this issue is resolved. SDR 171751 In previous versions of the client, if a user uses the Link to Address Book feature and selects New Address, the first name and last name fields for the contact are blank. In the BlackBerry Client for IBM Lotus Sametime version 2.1.18, this issue is resolved. SDR 54096 In previous versions of the client, in certain circumstances, if a user declines a conference request and sends a decline message, the decline message is not received by the other participants. In the BlackBerry Client for IBM Lotus Sametime version 2.1.18, this issue is resolved. BlackBerry Client for IBM Lotus Sametime version 2.2.19 SDR 301851 SDR 298003 SDR 296640 Automatic login is turned off by default. In previous versions of the client, users cannot create multiple custom status messages with the same status icon. In the BlackBerry Client for IBM Lotus Sametime version 2.2.19, this issue is resolved. In previous versions of the client, if a user transfers a file and selects the optimize checkbox, an error might display on the BlackBerry device when the recipient tries to open the file, and the file does not open. In the BlackBerry Client for IBM Lotus Sametime version 2.2.19, this issue is resolved. SDR 286479 In previous versions of the client, when users set 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 IBM Lotus Sametime version 2.2.19, 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 SDR 228634 Automatic login is turned off by default. 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 SDR 301257 Automatic login is turned off by default. 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 Client for Novell® GroupWise® Messenger version 2.1.18 SDR 247975 In previous versions of the client, in certain circumstances, if a user adds a contact to the contact list, then logs out and logs back in to the client, the contact that the user added is not in the contact list. In the BlackBerry Client for Novell GroupWise Messenger 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 Novell GroupWise Messenger version 2.1.18, this issue is resolved. BlackBerry Client for Novell GroupWise Messenger version 2.2.19 SDR 301851 Automatic login is turned off by default.

BlackBerry Configuration Database SDR 217622 SDR 171273 SDR 217556 SDR 181269 In previous versions of the BlackBerry Enterprise Server, if you try to install the BlackBerry database notification system, the installation process fails if you have configured more than one non-default Microsoft SQL Server. In BlackBerry Enterprise Server version 5.0, this issue is resolved. In previous versions of the BlackBerry Enterprise Server, if you move multiple users to a different BlackBerry Enterprise Server, the operation might take longer than expected. As a result, the BlackBerry Enterprise Server reports the operation as nonresponsive, which causes the BlackBerry Controller to restart the BlackBerry Messaging Agent. In BlackBerry Enterprise Server version 5.0, this issue is resolved. SDR 173464 In previous versions of the BlackBerry Enterprise Server, if you install the BlackBerry database notification system, a SELECT statement might cause multiple SQL recomputations, which can increase the CPU utilization of the Microsoft SQL Server. In BlackBerry Enterprise Server version 5.0, this issue is resolved. BlackBerry Controller SDR 187253 SDR 170295 In previous versions of the BlackBerry Enterprise Server, when the BlackBerry Controller restarts a BlackBerry Enterprise Server component, it causes debugging activities such as NSD to fail. In BlackBerry Enterprise Server version 5.0, this issue is resolved. BlackBerry Enterprise Server Alert Tool SDR 187311 SDR 181271 In previous versions of the BlackBerry Enterprise Server, if the SMTP server is unavailable, the BlackBerry Enterprise Server Alert Tool causes the TCP/IP stack to run out of memory due to the number of queued alerts. As a result, the BlackBerry Enterprise Server stops responding. In BlackBerry Enterprise Server version 5.0, this issue is resolved. BlackBerry Messaging Agent SDR 241687 In previous versions of the BlackBerry Enterprise Server, in certain circumstances, a memory leak occurs if a user opens an image in an email message using the BlackBerry device. In BlackBerry Enterprise Server version 5.0, this issue is resolved. SDR 217597 SDR 174787 SDR 174554 SDR 217544 SDR 178517 SDR 190050 In previous versions of the BlackBerry Enterprise Server, if a message has more than 32 recipients in the To or CC field, the field is truncated when the message is received on users’ BlackBerry devices. As a result, the recipient’s name might not be listed in the To or CC field. In BlackBerry Enterprise Server version 5.0, this issue is resolved. In previous versions of the BlackBerry Enterprise Server, in certain circumstances, the BlackBerry Messaging Agent might create duplicate tag IDs for messages. As a result, if a user deletes a message, other messages with the same tag ID are also deleted. In BlackBerry Enterprise Server version 5.0, this issue is resolved. In previous versions of the BlackBerry Enterprise Server, if you turn on support for HTML format and RTF formal email messages, when the BlackBerry Enterprise Server Alert Tool sends a message to a user’s BlackBerry device, the body of the message is blank if the device is running on BlackBerry Device Software version 4.5 or BlackBerry Device Software version 4.6. If the user clicks More, an error message displays. In BlackBerry Enterprise Server version 5.0, this issue is resolved.

9

BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino

BlackBerry Messaging Agent SDR 187239 SDR 169942 SDR 176000 In previous versions of the BlackBerry Enterprise Server, in certain circumstances, the BlackBerry Messaging Agent might stop responding while decoding certain messages from BlackBerry devices. In BlackBerry Enterprise Server version 5.0, this issue is resolved. In previous versions of the BlackBerry Enterprise Server, the Domino error code was not referenced if the following error appeared in the log files generated by the BlackBerry Messaging Agent: “Unable to get modified notes”. In BlackBerry Enterprise Server version 5.0, this issue is resolved. BlackBerry Policy Service SDR 187317 SDR 171638 In previous versions of the BlackBerry Enterprise Server, in certain circumstances, the BlackBerry Policy Service sends the update service data command to a BlackBerry device after it sends the switch service command to the BlackBerry device. As a result, the BlackBerry device receives incorrect SRP information. In BlackBerry Enterprise Server version 5.0, this issue is resolved. SDR 187316 SDR 175714 In previous versions of the BlackBerry Enterprise Server, if you move users to a different BlackBerry Enterprise Server, for some user accounts, the BlackBerry Policy Service uses the source server’s SRP address or IT policy commands instead of the destination server’s SRP address. As a result, the correct IT policy might not be applied to users until you restart the BlackBerry Enterprise Server. In BlackBerry Enterprise Server version 5.0, this issue is resolved. Logging SDR 187256 SDR 180186 In previous versions of the BlackBerry Enterprise Server, if a user’s contact list exists on a different server than the user’s 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. Organizer data synchronization SDR 187245 SDR 149614 In previous versions of the BlackBerry Enterprise Server, the contact list lookup on the BlackBerry device returns unexpected results when too many matches are found in the Lotus Domino directory. In BlackBerry Enterprise Server version 5.0, this issue is resolved. Setup application SDR 187227 SDR 169735 SDR 157913 SDR 177085 In previous versions of the BlackBerry Enterprise Server, the setup application stops responding at the Preinstallation Checklist screen. In BlackBerry Enterprise Server version 5.0, this issue is resolved. When upgrading from BlackBerry Enterprise Server version 4.1 SP4 to BlackBerry Enterprise Server version 4.1 SP5 or later, the 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. Wireless calendar synchronization SDR 187257 SDR 171564 In previous versions of the BlackBerry Enterprise Server, when a user checks the availability of meeting invitees from the BlackBerry device, if the availability information can not be retrieved for a single invitee, the availability information for the other meeting invitees is not available as well, and an "Unable to find time where all attendees are available" error message displays. 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. 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. 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. 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. Users cannot activate BlackBerry devices with BlackBerry Connect® version 4.0. 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. BlackBerry Administration Service SDR 310044 In a multi-domain environment with non-contiguous domain names, the BlackBerry Administration Service does not allow you to create a user account. Workaround 1. During the installation process, specify one of the domains as the LDAP search base.
value = ' ' where PluginId=111 and TraitId=1

SDR 211317

SDR 272457

SDR 270541 SDR 179376 SDR 169257 SDR 171446

2. Run the following SQL statement against the BlackBerry Configuration Database (BESMgmt): Update BASTraits set 3. In the BlackBerry Administration Service, specify the LDAP server web address to reference the Global Catalog Server and port 3268: ldap://<global_catalog_server_name>:3268 4. In the BlackBerry Administration Service, create the user account. SDR 305797 SDR 305521 SDR 304333 SDR 303677 In certain circumstances, if you create a user account in the Lotus Domino directory, you cannot create a BlackBerry device user account for the user. The $USERS view in the names.nsf file contains multiple user rows with the same Internet address. You cannot assign more than one WLAN configuration set at a time to a user account. After you specify and save a default domain on the LDAP Authentication tab, you cannot delete the default domain that you specified. If the BlackBerry Configuration Database contains invalid license key information, you cannot access the BlackBerry Administration Service component web page. Workaround Run the setup application again and enter valid license key information.

11

BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino

BlackBerry Administration Service SDR 302412 SDR 300139 SDR 299466 If you perform a quick search for a user, click Manage multiple users, select multiple users, and then perform an action (for example, adding the user accounts to a group), no results are shown when you click Back to previous search results. The setup application does not complete successfully if you rename or remove the Security Administrator role. If your organization's environment uses LDAP zones, the BlackBerry Administration Service cannot resolve the LDAP zone into an IP address. Workaround Specify a hostname in the LDAP URL for the BlackBerry Administration Service. SDR 299327 SDR 298667 The BlackBerry Administration Service does not validate the file format extensions that you specify for the BlackBerry Attachment Service. If you try to delete the <server>_BAS-NCCJ_01_<date>_loginstance.txt file that is created when the BlackBerry Enterprise Server is installed, the following error message displays: “Cannot delete <server>_BAS-NCCJ_01_<date>_loginstance.txt. It is being used by another person or program. Close any programs that might be using the file and try again.” Workaround Restart the BAS-NCC.exe service, then delete the file. SDR 296580 If the version of the BlackBerry database notification system installed on the database server is earlier than version 5.0, the BlackBerry Administration Service does not receive database notifications and only receives heartbeat messages. This issue might occur if you run a BlackBerry Configuration Database version 4.1 or earlier and a BlackBerry Configuration Database version 5.0 on the same database server. Workaround Perform one of the following actions: • • SDR 294931 SDR 293315 SDR 292184 On the database server, replace the RIMesp.dll file with the latest version and restart the Microsoft SQL Server. Create a separate SQL instance for BlackBerry Enterprise Server version 5.0.

You cannot change the start date for jobs with a Ready to run status. When you edit job distribution settings and change the Maximum number of automatic retries value to 0, after you save your changes, the BlackBerry Administration Service does not display the Retry processing section. When you search for BlackBerry Device Software bundles that can be distributed over the wireless network, the BlackBerry Administration Service searches for and displays the bundles that are compatible with the BlackBerry devices that are supported by the wireless service provider. If the user accounts that are associated with BlackBerry devices that are supported by the wireless service provider are deleted from the BlackBerry Enterprise Server, and you search for BlackBerry Device Software bundles that can be distributed over the wireless network, the BlackBerry Administration Service might display BlackBerry Device Software bundles that are no longer supported in your BlackBerry Enterprise Server environment. If the name you specify for the BlackBerry Enterprise Server ends with “_<number>”, and the BlackBerry Enterprise Server is not part of a high availability pair, the BlackBerry Enterprise Server name is displayed as the ServiceName in the BlackBerry Administration Service. When you change the Auto backup Include all IT policy rule to Yes, the Back up on-board device memory option in the BlackBerry Web Desktop Manager is cleared automatically and users cannot back up the BlackBerry device memory for BlackBerry Storm smartphones and BlackBerry Bold smartphones. You cannot add a user account that has an email address that contains special characters. If you change organizer data synchronization settings, the settings are not applied to roaming users or to iNotes users. If you add an application to a software configuration, specify a wired installation using the BlackBerry Web Desktop Manager, and then assign the software configuration to users, the application does not install on users’ BlackBerry devices if users have a later version of the application installed on their BlackBerry devices. If you configure DIIOP in a clustered Lotus Domino environment, and a failover occurs for the Lotus Domino server that is running DIIOP, the BlackBerry Administration Service cannot authenticate users with Lotus Domino. Workaround Perform one of the following actions: • • Use the BlackBerry Configuration Panel to specify the new Lotus Domino server that is running DIIOP and restart the BlackBerry Administration Service. Configure a hardware load-balancer that permits the BlackBerry Administration Service to contact more than one Lotus Domino server that is running DIIOP.

SDR 291518

SDR 290289

SDR 288125 SDR 286630 SDR 265410

SDR 204868

If you can log in to the BlackBerry Administration Service using BlackBerry Administration Service authentication, in the BlackBerry Administration Server, specify the new Lotus Domino server that is running DIIOP and restart the BlackBerry Administration Service. For more information, see the BlackBerry Enterprise Server Administration Guide.

12

Release Notes

BlackBerry Attachment Service SDR 300174 If a user tries to open a .wma message attachment on the BlackBerry device, the attachment does not open, and an “unrecognized document format” error message displays on the BlackBerry device. Workaround Before running the setup application on the computer that you want to host the BlackBerry Attachment Service, visit www.microsoft.com to download and install the Microsoft® Visual C++® 2005 SP1 Redistributable Package (x86). SDR 272080 If a user receives a message on the BlackBerry device that contains a Microsoft® Excel (.xls) attachment that contains dates formatted in Chinese, when the user views the file, the dates display as numbers or do not display.

BlackBerry Client for IBM Lotus Sametime version 2.1.18 SDR 302901 SDR 253466 SDR 194043 The BlackBerry Client for IBM Lotus Sametime version 2.1.18 permits users to create custom status messages with no status text entered. Users cannot create a personal group named “Test” or “Users”. If a user invites another user to a meeting using the Lotus Sametime application on their computer, and the recipient declines the invite using the BlackBerry Client for IBM Lotus Sametime, the recipient cannot receive additional invitations to the same meeting using the BlackBerry Client for IBM Lotus Sametime. In certain circumstances, the bcol.exe process experiences a memory leak. Workaround Instruct users to log out of the client periodically. SDR 189012 SDR 186581 In certain circumstances, a user might be added to a meeting without receiving a meeting request. If multiple users exist with similar user names, incorrect contacts might be added to the users’ contact lists. Workaround When adding contacts, instruct users to select the user name from the Lookup list. SDR 181474 If a user has a large number contacts in the contact list (for example, over 100 contacts in a public folder), the user might receive a “Device has been denied access by the server” error message when logging in. This issue only occurs if the BlackBerry Collaboration Service uses a proxy server. Workaround Restart the BlackBerry Collaboration Service. SDR 177400 SDR 174697 SDR 69679 SDR 69400 If a BlackBerry device user adds an instant messaging contact to the contact list using the BlackBerry Client for IBM Lotus Sametime, the New Address screen is not populated with the correct information. The incorrect time is displayed on the View Person’s Info screen. Users cannot set an alert for contacts who have an Away or Do Not Disturb status. The presence notification is turned off if a user logs in to the Lotus Sametime application on their computer, and then logs in to the BlackBerry Client for IBM Lotus Sametime on the BlackBerry device.

SDR 191616

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 SDR 304881 SDR 304713 SDR 303950 SDR 302669 SDR 281795 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. 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. A user can send messages to a blocked contact if the user has an existing conversation with the contact. 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. In certain circumstances, after a user deletes a contact from the contact list, the user receives an add request for a contact the 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 SDR 279862 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. 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 SDR 186430 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 $ ). 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.

BlackBerry Collaboration Service SDR 287243 When using the BlackBerry Collaboration Service with Microsoft Office Communications Server 2007, the BlackBerry Collaboration Service might use more private memory resources than expected. As a result, the BlackBerry Collaboration Service might stop responding, and the BlackBerry Controller might not restart the BlackBerry Collaboration Service. Workaround If this problem occurs, please contact your support representative. SDR 271303 The BlackBerry Collaboration Service is not compatible with Microsoft® Office Communications Server 2007 R2. For information about a workaround, visit www.blackberry.com/support to read KB 17757.

BlackBerry Configuration Database SDR 300344 SDR 298246 SDR 213910 If the BlackBerry Synchronization Service cannot connect to the BlackBerry Configuration Database, the computer that hosts the BlackBerry Synchronization Service might use more CPU resources than expected. If you install the BlackBerry Enterprise Server on a Japanese operating system, you cannot start the BlackBerry database notification system. If you configure database mirroring for the BlackBerry Configuration Database in a high availability environment, and the principal BlackBerry Configuration Database instance fails over to the mirrored instance, you can no longer log in to the BlackBerry Administration Service. You cannot upgrade the BlackBerry Configuration Database with database replication turned on.

SDR 146177

BlackBerry Configuration Panel SDR 308639 If you install a BlackBerry Collaboration Service instance on a remote computer, a shortcut for the BlackBerry Configuration Panel appears in the Start menu but does not run when clicked. Workaround Ignore the shortcut. The BlackBerry Configuration Panel does not include any functionality relevant to the remote instance of the BlackBerry Configuration Service. SDR 297897 If you installed the BlackBerry Enterprise Server in a 64-bit Windows environment, you cannot launch the BlackBerry Configuration Panel from the Windows Control Panel. Workaround You can open the BlackBerry Configuration Panel from Start > All Programs > BlackBerry Enterprise Server. SDR 296184 The test attachment service feature has been removed from the BlackBerry Configuration Panel. Workaround Manually run BBAttachConfig.exe from the BlackBerry Enterprise Server installation files. SDR 293579 If you use the BlackBerry Configuration Panel to configure the BlackBerry Enterprise Server to use dynamic ports, the registry is not updated. Workaround In HKEY_LOCAL_MACHINE/Software/RIM/BlackBerry Enterprise Server/Database, change the DynamicSQLPort registry value to 1. SDR 284933 If your organization’s environment uses Windows 2008, certain settings that you change using the BlackBerry Configuration Panel (for example, log directory settings) are not applied unless you run the BlackBerry Configuration Panel with administrator permissions.

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 Desktop Manager SDR 300720 The BlackBerry Desktop Manager stops responding if the user’s auto-signature contains a “%” character.

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.

BlackBerry Enterprise Server Alert Tool SDR 281079 In certain circumstances, on Windows Server 2008 operating systems, BlackBerry Enterprise Server version 5.0 alert console messages are not supported.

BlackBerry MDS Connection Service SDR 220951 Users cannot update the chain status of certificates over the wireless network. The BlackBerry MDS Connection Service cannot verify the signature of the certificate and users cannot send S/MIME encrypted messages. Workaround 1. Connect the user’s BlackBerry device to the user’s computer. 2. Open the BlackBerry Desktop Manager. 3. Click Synchronize Certificates. 4. Select a check box beside one or more certificates. 5. Click Synchronize. BlackBerry MDS Integration Service SDR 263253 In certain circumstances, the BlackBerry MDS Integration Service stops responding shortly after starting because the BlackBerry MDS Integration Service cluster experiences a failure and cannot failover successfully. Workaround From any BlackBerry MDS Integration Service instance in the cluster, run the mdsis-cluster-failure-recovery.bat script that resides in the bin folder of the BlackBerry MDS Integration Service instance, and follow the instructions on the screen. You can also manually delete all entries in the MEMBERSHIP table in the BlackBerry MDS Integration Service database for that cluster. Restart the BlackBerry MDS Integration Service instance. DPI 223758 You can install a signed application on BlackBerry devices without adding the certificate to the BlackBerry MDS Integration Service if you schedule the application installation to occur while the BlackBerry MDS Integration Service is configured to allow unsigned applications. You cannot log in to the BlackBerry MDS Application Console if the BlackBerry Configuration Database is configured for database mirroring and fails over using a non-default port number (1345). Workaround Restart the BlackBerry Administration Service services. DPI 223697 In certain circumstances, after the BlackBerry Enterprise Server fails over, the BlackBerry MDS Integration Service cannot connect to the BlackBerry MDS Connection Service. As a result, you cannot manage or install BlackBerry MDS Runtime Applications on BlackBerry devices, and users cannot search for BlackBerry MDS Runtime Applications using the BlackBerry MDS Control Center on the BlackBerry device. Workaround Restart the BlackBerry MDS Integration Service. DPI 223537 Users can activate the BlackBerry MDS Runtime manually from their BlackBerry devices even if you turn off this functionality using the Disable User-Initiated Activation with the BlackBerry MDS Integration Service IT policy rule.

DPI 223730

15

BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino

BlackBerry MDS Integration Service DPI 223533 If you configured your BlackBerry Enterprise Server environment to support high availability for the BlackBerry MDS Integration Service, the high availability page in the BlackBerry Administration Service might not display accurate information about the BlackBerry MDS Integration Service instances. Workaround Remove quarantined applications from BlackBerry devices and from the BlackBerry MDS Application Repository, and publish the applications to the BlackBerry MDS Application Repository again. DPI 223298 If you install the BlackBerry MDS Integration Service with a BlackBerry Enterprise Server environment that supports high availability, and you select support for database mirroring and the dynamic port type during the install, the BlackBerry MDS Integration Service might not start when the setup application completes. Workaround Perform one of the following actions: • • DPI 222584 Use the BlackBerry Configuration Panel to select static ports instead of dynamic ports. In the Registry Editor, in HKEY_LOCAL_MACHINE/Software/Research In Motion/BlackBerry Enterprise Server/Database, delete Failover DBregistry.

When a user requests a list of available applications using the BlackBerry MDS Control Center on the BlackBerry device, if the application list that the BlackBerry MDS Integration Service sends to the BlackBerry MDS Connection Service is close in size to the maximum data amount permitted per connection that you configured for the BlackBerry MDS Connection Service, the BlackBerry MDS Connection Service might not accept the application list. Workaround Change the maximum data amount permitted per connection in the BlackBerry Configuration Database.

DPI 222151

If you stop the BlackBerry Configuration Database, the BlackBerry MDS Integration Service services do not stop. Workaround Stop the BlackBerry MDS Integration Service services manually using Windows Services.

DPI 222132

In the BlackBerry MDS Application Console, if you switch between the user management page and the device management page multiple times in quick succession, the pages do not refresh correctly, and might display incorrect user or device information. Workaround Refresh the pages manually.

DPI 222098

If a user uses a BlackBerry MDS Runtime Application that uses a Db Connector Plugin to retrieve data from a database server, when the user clicks “More” to view data that is displayed on multiple pages, data might not be returned and an “invalid request or session timed out” error message might display. On Windows 2008 operating systems, in certain circumstances, a stack trace appears in the BlackBerry MDS Integration Service log file when the BlackBerry MDS Runtime on BlackBerry devices tries to activate with the BlackBerry MDS Integration Service, and the BlackBerry MDS Runtime does not activate successfully. Workaround Use IP version 4.

DPI 222082

DPI 222080

If the BlackBerry MDS Integration Service receives a response from a web service with empty or null strings in a string array, the BlackBerry MDS Integration Service drops the empty and null strings, and in certain circumstances, turns the empty strings into null strings. Workaround Use empty strings to convey null values, or use a default value (for example, “N/A”) to convey an empty value.

DPI 220428 DPI 202465

The BlackBerry MDS Integration Service version 5.0 does not support the best-effort delivery mode for messages. If you install more than one BlackBerry MDS Integration Service to create a pool for high availability, the BlackBerry MDS Integration Service on the primary computer stops responding. Workaround Restart the BlackBerry MDS Integration Service. Or, install the BlackBerry MDS Integration Service instances on a computer that is separate from the computer that hosts the BlackBerry Administration Service.

DPI 219009

After the BlackBerry Enterprise Server fails over, if users use the BlackBerry MDS Control Center on the BlackBerry device to search for BlackBerry MDS Runtime Applications that are stored in the BlackBerry MDS Application Repository, the search might not return any results. Workaround Restart the BlackBerry MDS Integration Service instances.

DPI 168992

If the state of a BlackBerry MDS Runtime Application is suspended, the BlackBerry MDS Integration Service stores this information in memory, but does not store this information in the BlackBerry MDS Integration Service database. This information does not display in the BlackBerry Administration Service or the BlackBerry MDS Application Console.

16

Release Notes

BlackBerry Messaging Agent SDR 293085 SDR 287464 SDR 287348 If a user’s name contains an apostrophe (‘), and the user name is specified as part of the criteria for an email message filter, the email message filter might not be applied for the user. If a user replies to an email message that was received in rich-content format on the BlackBerry device, and attaches a contact from the user’s contact list to the reply, the message is not delivered successfully. In a Lotus Domino version 8.0 environment, the BlackBerry Messaging Agent might take longer than expected to send messages and calendar items to BlackBerry devices, and in certain circumstances, BlackBerry devices might not activate with the BlackBerry Enterprise Server. This issue impacts users whose mail file path in the operating system has a different case than the mail file path specified in the person document. Workaround Perform one of the following workarounds: • • SDR 279712 SDR 277847 Verify that the mail file path for users in the operating system is the same as the mail file path for those users specified in the person document. In HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents, change the DWORD value PollByMailServer to 0.

Memory usage by the BlackBerry Messaging Agent process, nbes.exe, spikes by more than 30 MB for a few seconds when a user sends an email with a large attachment. In certain circumstances, if you restart Windows on the computer that hosts the BlackBerry Enterprise Server, the BlackBerry Messaging Agent might not be able to start worker threads, and cannot perform processing for any users. Workaround Manually restart the BlackBerry Enterprise Server components that were running on the Lotus Domino server prior to restarting Windows.

SDR 269826 SDR 267463 SDR 259394 SDR 256062

In certain circumstances, users cannot turn off the redirection of sent items from their BlackBerry devices. HotSpot links embedded in an email message cannot be opened unless a “http” prefix is used. In certain circumstances, if your organization's mail server stops responding, the BlackBerry Enterprise Server Alert Tool generates hundreds of error messages, causing the BlackBerry Messaging Agent log file to grow dramatically. In certain circumstances, if the BlackBerry Enterprise Server encounters low memory conditions, the Inbox folder reference for some user accounts is deleted in the BlackBerry state database. Email messages are not sent to user accounts that do not have an Inbox folder reference in the BlackBerry state database. The BlackBerry Enterprise Server stops responding if the BlackBerry Messaging Agent creates multiple worker threads when deleting a large number of entries on a user's BlackBerry device. The worker threads are reported as unresponsive in the BlackBerry Messaging Agent log file. If a user sends a message using the BlackBerry device, and the user’s mail file name contains certain special characters (for example, "ñ"), the message is not saved in the Lotus Notes mail file. In certain rare circumstances, users cannot view unencoded attachments contained in incoming MIME messages on their BlackBerry devices. The attachments are encoded into the text of the message body instead of being rendered as an attachment. If a user forwards a message with a .wav message attachment, the recipient cannot open the attachment on the BlackBerry device if support for rich-content email messages is turned on for the BlackBerry device. Workaround Turn off support for rich-content email messages for the BlackBerry device.

SDR 250169

SDR 248591 SDR 232290

SDR 218023

SDR 194682

If special characters are specified when using the User word Variants option to search for an email message on a user's BlackBerry device (for example, õ Èä t"), no search results are displayed. Workaround Do not use special characters in the search criteria.

SDR 187261 SDR 179162

If a user sets their Out of Office profile using the BlackBerry device, the Out of Office profile is incompatible with the IBM iNotes™ web client. The BlackBerry Messaging Agent might stop responding when processing the cancellation of single instance of a repeating Calendar entry. Workaround Restart the BlackBerry Messaging Agent.

SDR 164714 SDR 141367

Certain email messages might not be sent to a user's BlackBerry device if the messages were received by the BlackBerry Messaging Agent while the user's Lotus Domino mail server is in the process of failing over. In certain circumstances, email messages are not wirelessly redirected to a user's BlackBerry device even though the message was placed in a redirected folder. This is more likely to occur if your mail server is geographically located a great distance from the BlackBerry Enterprise Server.

17

BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino

BlackBerry Messaging Agent SDR 136345 If users are using service mode in Lotus Notes version 8.0, users cannot turn on or turn off the Out of Office agent from their BlackBerry devices. If Lotus Notes automatically disables the Out of Office agent, the Out of Office agent is not disabled on users’ BlackBerry devices. Workaround Turn off the Out of Office service. BlackBerry Monitoring Service SDR 307868 If you restart the BlackBerry Enterprise Server or if the BlackBerry Enterprise Server fails over, users might be identified by their user configuration IDs instead of by their user names in the alarm and messages details in the BlackBerry Monitoring Service. This issue might also occur if the number of users exceeds the UserPollMax value. If you edit a user’s email address, the user’s email address is updated in the User search and User details pages, but not in the Address list or Contacts pages. Workaround Delete the user’s previous email address and add the new email address to the Address list and Contact pages. SDR 307779 SDR 303538 Message timestamps are based on the timezone of the BlackBerry Monitoring Service database. As a result, the timestamps of certain messages might not be consistent with the timestamps of the corresponding alarms. If you install the BlackBerry Monitoring Service on a computer with a Japanese operating system, notification messages display in Japanese in the BlackBerry Monitoring Service, but the notification message body does not display correctly when it is received in the mailbox on the recipient’s computer and on the BlackBerry device. If your BlackBerry Domain contains more than one BlackBerry Enterprise Server, the global user threshold shares the same server maintenance window even when users are assigned to different BlackBerry Enterprise Servers. If you clear the temporary server maintenance window and test the configuration settings, an exception error displays and you cannot test the configuration settings. If you add more than 10 notification addresses, only the first 10 notification addresses display in the BlackBerry Monitoring Service. If you create more than 10 contacts, only the first 10 contacts display in the Contacts by contact name screen. All contacts display in the Contacts by server name screen. After the BlackBerry Enterprise Server completes an automatic failover, the BlackBerry Dispatcher SRP connection alarm message displays even though the corresponding threshold entered a pass state. Workaround Delete the alarm message. SDR 298777 SDR 298222 SDR 297695 In certain circumstances, a time-based component threshold triggers immediately after you set the threshold. If you do not save the SMS settings, an error message displays when you try to send a test SMS message to BlackBerry devices. If you add a warning user threshold rule to a user account, the warning messages that display in the alarm panel when the threshold is triggered are not cleared when you disable the threshold rule from the rule level. Workaround Delete or disable the warning user threshold rule from the threshold level. SDR 294753 SDR 294739 In certain circumstances, the BlackBerry Monitoring Service does not run a diagnostic test after the BlackBerry Configuration Database fails over. You cannot change the high availability scope of a BlackBerry Enterprise Server component after you add a threshold on a BlackBerry Enterprise Server component that uses load balancing (the BlackBerry Router, BlackBerry Attachment Service, and the BlackBerry MDS Integration Service). Workaround Create a new threshold on the BlackBerry Enterprise Server component that does not use load balancing. Then, change the high availability scope. SDR 294689 SDR 294505 SDR 294086 SDR 293583 The threshold alarm for a user account is cleared when you configure a threshold maintenance window for the current moment. In certain circumstances, duplicate failover detected messages display for BlackBerry Enterprise Server components. Alarm messages for a BlackBerry Enterprise Server environment that is not configured for high availability might use high availability terms such as failover and primary BlackBerry Enterprise Server. When a standby BlackBerry Enterprise Server is unavailable, the BlackBerry Monitoring Service console displays a critical alarm in the BlackBerry solution topology for the connection status of the Host component, but does not display a critical alarm in the Alarm panel. When you perform a ping test from the BlackBerry Monitoring Service console for a device that is connected to the BlackBerry Enterprise Server using a Wi-Fi® connection, the ping test fails.

SDR 307781

SDR 303132 SDR 303005 SDR 302972 SDR 302968 SDR 302891

SDR 291862

18

Release Notes

BlackBerry Monitoring Service SDR 290827 In a high availability environment, when the active BlackBerry Enterprise Server fails over to the standby BlackBerry Enterprise Server, the BlackBerry Monitoring Service console does not change the status of the failed over BlackBerry MDS Connection Service to standby. When the alarm severity of a threshold for a data attribute of a BlackBerry device user that is in an alarm state changes, the Alarm panel in the BlackBerry Monitoring Console might not update the alarm state for the threshold. When you add an IP address and port number to send SNMP trap messages to a computer that is not part of your organization's network, the BlackBerry Monitoring Service does not add the port number correctly. The BlackBerry Monitoring Service adds the port number to the IP address. Workaround Include the SNMP community name as well as the IP address and port number using the format <ipaddress>:<portnumber>:<community>. SDR 286133 SDR 286082 An exception error displays when a user with only the View BlackBerry Monitoring Service information permission searches for user accounts. When a threshold that includes duration-based rules goes from a fail state to a pass state, the BlackBerry Monitoring Service does not update the alarm state of the threshold in the BlackBerry Monitoring Service console. Workaround In the BlackBerry Monitoring Service console, save the threshold again. SDR 285428 When a BlackBerry device user sends a message to another BlackBerry device user, the BlackBerry Monitoring Service increments the value for the number of messages from a BlackBerry device for the BlackBerry Dispatcher component by two instead of one. The user statistic “Synchronization message to” is reported even though the user account is not associated with a BlackBerry device. If you delete a threshold for a user or component data item that is in an alarm state, the alarm clears but a pass notification is not sent. As a result, an incorrect Fail message displays for a data item that is no longer in a failed state. The BlackBerry Enterprise Server cannot fully monitor 3G BlackBerry devices using an MIB browser. The 3G BlackBerry devices are displayed as “Filtered” in the BlackBerry Monitoring Service. In this state, the BlackBerry Monitoring Service cannot monitor incoming data connections or outgoing data connections to the BlackBerry Enterprise Server or any other applications that an administrator has configured the BlackBerry Monitoring Service to send SNMP traps to.

SDR 289828 SDR 288671

SDR 284986 SDR 280608 SDR 272457

BlackBerry Policy Service SDR 266801 SDR 219718 SDR 192721 SDR 175863 In certain circumstances, the correct default language is not displayed on the Customize screen when a BlackBerry device user checks for BlackBerry Device Software updates over the wireless network. In certain circumstances, invalid log entries appear in the Synchronization Log (for example, EventId:0(0x00000000)). In certain circumstances, if the Enterpise Service Policy is enabled on a user’s BlackBerry device, error messages are logged when the user tries to regenerate encryption keys. The BlackBerry Enterprise Server does not support the “Is access to the media API allowed” application control policy (formerly known as Media Access application control policy), and the BlackBerry Administration Service does not display this application control policy. If you restart the BlackBerry Policy Service, the following data items do not return any values: Config ID, IT Policy Name, and IT Policy Time Applied.

SDR 168314

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.

BlackBerry Synchronization Service SDR 287389 If the connection to the Microsoft SQL Server is lost, the DevMgmt Connector database connection pool cannot initialize until you restart the BlackBerry Synchronization Service.

BlackBerry Web Desktop Manager SDR 301322 When a user tries to log in to the BlackBerry Web Desktop Manager, the user is prompted to install Adobe® Flash® Player if it is not already installed on the user’s computer. Adobe Flash Player is not required to run the BlackBerry Web Desktop Manager. If the user does not choose to install Adobe Flash Player, the user cannot log in to the BlackBerry Web Desktop Manager successfully. Users might encounter problems when logging in to the BlackBerry Web Desktop Manager if you did not define an application network share using the BlackBerry Administration Service. If a user configures data backup options and then performs a manual backup, the BlackBerry Web Desktop Manager uses the automatic backup settings.

SDR 300192 SDR 295738

19

BlackBerry Enterprise Server version 5.0 for IBM Lotus Domino

Logging SDR 301360 SDR 293969 SDR 286202 SDR 277730 SDR 276975 SDR 259814 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. “Queuing” is spelled inconsistently across the BlackBerry Enterprise Server component log files. Certain log files use “queuing” while other log files use “queueing”. 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. 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. 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. 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.

Organizer data synchronization SDR 289800 In certain circumstances, if you move a user account to a different BlackBerry Enterprise Server, organizer data synchronization is turned off for the user’s BlackBerry device, and the user cannot turn organizer data synchronization back on using the BlackBerry device. Workaround Restart the BlackBerry Controller. SDR 287389 If the connection between the BlackBerry Enterprise Server and the Microsoft SQL server is lost, and the connection pool needs to be restarted, the BlackBerry Device Manager Connector cannot initialize until the BlackBerry Synchronization Service is restarted. In a Lotus Domino version 8.5 environment, when users perform contact list lookups using their BlackBerry devices, the results do not adhere to the organizer data synchronization settings that you configure using the BlackBerry Administration Service. If you specify Japanese characters when searching for a user account using a BlackBerry device, the user's name is displayed incorrectly in the search results (for example, the characters are displayed as 4E0A or 4F0A). Workaround Do not use Japanese characters in the search criteria. SDR 277907 SDR 270467 SDR 267839 In certain circumstances, a user’s contact list is rescanned multiple times during an activation, causing the activation process to take a long time. Synchronization over the wireless network can take a long time when processing contact lists with a large number of entries during the activation process. In certain circumstances, synchronization over the wireless network can take a long time for user accounts that have a large number of contact list entries (for example, over 5000 entries). The cache is rebuilt every time the synchronization process is run on the contact list while looking for duplicate entries, causing a decrease in performance. Setting the MaxPIMRecordTransfer registry entry to a specific value does not limit the number of contact list entries that can be synchronized to a BlackBerry device. All updated entries in the user's contact list are synchronized to the user's BlackBerry device. The BlackBerry Enterprise Server can take a longer time than expected to synchronize the contacts on users’ BlackBerry devices with the contacts in large iNotes contact lists over the wireless network. Workaround Increase the synchronization timeout to more than 200 minutes. SDR 233223 In certain circumstances, a BlackBerry device stops responding or its performance is significantly diminished after wirelessly synchronizing monthly calendar events with the BlackBerry Enterprise Server if the ReapeatAdjust value in Lotus Notes contains a zero value entry. If a user adds new organizer data while the BlackBerry Configuration Database is not responding, this organizer data is not synchronized to the user’s BlackBerry device when you restart the BlackBerry Configuration Database. The BlackBerry Enterprise Server might take a long time to start if your organization's mail server is linked to the BlackBerry Enterprise Server over a wireless network. New contacts are saved in the Contacts folder even if a user specifies a folder other than “Contacts” as the default. Overdue items in the To Do list in Lotus Notes are not synchronized to a user's BlackBerry device. If you move a roaming user account to a different messaging server, the location of the destination server and relative path for the wireless contact list and journal are not updated on the user’s BlackBerry device. The company name and email address do not appear in the Native_BasicAddrFields.vcf file for the Windows Mobile Voice Card versions 2.1 and 3.0.

SDR 281646 SDR 280139

SDR 264776

SDR 250861

SDR 219721 SDR 219343 SDR 197354 SDR 144850 SDR 133509 SDR 87673

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. 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. 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.

SDR 208366

SDR 148393

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. 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 SDR 301989 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). 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.

SDR 310792

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. 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 nonstandard 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 (|). 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. 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. 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.

SDR 290745

SDR 280876

SDR 280151 SDR 277912

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. 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. 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 SDR 283732 If you install a BlackBerry Enterprise Server version 5.0 instance that shares a BlackBerry Configuration Database with a 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.

SDR 299885 SDR 299755

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 SDR 189869 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. 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. Wireless calendar synchronization SDR 289431 SDR 287348 If the BlackBerry Enterprise Server is running in low memory conditions, it might stop responding when processing a large number of calendar items in a user's state database. On Windows 2008 operating systems, with Lotus Domino version 8.5, you must restart the BlackBerry Messaging Agent so that activation and message delivery can occur. Workaround Restart the BlackBerry Messaging Agent. For example, in the Lotus Domino console type “restart task bes". SDR 279398 If a user has a large number of documents in their iNotes contact list or journal stored in the mail file, it can take a long time to synchronize those documents to their BlackBerry device. Workaround Keep iNotes contact list and journal documents in separate databases (not in the mail file). SDR 269376 SDR 264758 SDR 262240 If you change a customized anniversary date in the BlackBerry calendar (for example, a national holiday), the date appears everyday in the BlackBerry calendar instead of once a year if the device is running BlackBerry Device Software version 4.2.2. In certain circumstances, the BESExtentionAPI fails to open an attachment that is sent from a user's BlackBerry device.

24

Release Notes

Wireless calendar synchronization SDR 258698 SDR 257729 SDR 257304 If a user is removed from a meeting and subsequently added to the same meeting using the Lotus Notes calendar, the updated meeting invitation does not appear in the calendar on users’ BlackBerry devices. In certain circumstances, changes made to the notification message for a recurring meeting using the BlackBerry device are not synchronized with the calendar in Lotus Notes. In certain circumstances, if a meeting is accepted using a BlackBerry device, the meeting status for all participants is not updated in the calendar. For example, the meeting organizer might appear as having accepted the meeting on a participant's BlackBerry device, but might appear as invited on another participant's BlackBerry device. An “Assertion Failed” error message is logged in the Application Event Viewer and BlackBerry Messaging Agent log files after updating the BlackBerry state database. Despite the error message, updated calendar entries are correctly processed by the BlackBerry Enterprise Server and sent to the user’s BlackBerry device. In certain circumstances, if the "Display new (unprocessed) notices" option is turned on on the BlackBerry device, the user cannot accept a calendar event that has changed. Calendar meetings might be one hour behind between May 31 and August 31, 2009, in Pakistan and Morocco, as daylight saving time (DST) has been introduced in these nations. The BlackBerry Device Software does not yet recognize DST in these nations. In certain circumstances, if a user deletes a meeting using Lotus Notes, the calendar invitation is not deleted on the recipients’ BlackBerry devices. In certain circumstances, calendar invitations are not removed from users' BlackBerry devices. If a roaming user is moved to a different mail server, the location server and relative path for the wireless contact list and journal are not updated to reflect the new mail server and path to the mail server database. Workaround Clear the values for the location server and relative path for the user.

SDR 235116

SDR 218100 SDR 188415 SDR 185807 SDR 187706 SDR 187248 SDR 151218 SDR 133509

25

Sign up to vote on this title
UsefulNot useful