BlackBerry Enterprise Server for IBM Lotus Domino
Version 4.1 Service Pack 2 Release Notes
BlackBerry Enterprise Server Version 4.1 Service Pack 2 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. 2006 Research In Motion Limited. All Rights Reserved. The BlackBerry and RIM families of related marks, images, and symbols are the exclusive properties of Research In Motion Limited. RIM, Research In Motion, BlackBerry, Always On, Always Connected and the envelope in motion symbol are registered with the U.S. Patent and Trademark Office and may be pending or registered in other countries. Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. IBM, Lotus, Domino, Lotus Notes, DB2 Universal Database, and Sametime are either registered trademarks or trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Novell and GroupWise are either registered trademarks or trademarks of Novell, Inc., in the United States and other countries. PGP is either a registered trademark or a trademark of PGP Corporation in the United States and other countries. VMware is a registered trademark of VMware. Wi-Fi is either a registered trademark or trademark of the Wi-Fi Alliance.All other brands, product names, company names, trademarks and service marks are the properties of their respective owners. The BlackBerry device 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 various countries around the world. Visit www.rim.com/patents for a list of RIM [as hereinafter defined] patents. This document is provided as is and Research In Motion Limited and its affiliated companies (RIM) assume no responsibility for any typographical, technical, or other inaccuracies in this document. In order to protect RIM proprietary and confidential information and/or trade secrets, this document may describe some aspects of RIM technology in generalized terms. RIM reserves the right to periodically change information that is contained in this document; however, RIM makes no commitment to provide any such changes, updates, enhancements, or other additions to this document to you in a timely manner or at all. RIM MAKES NO REPRESENTATIONS, WARRANTIES, CONDITIONS, OR COVENANTS, EITHER EXPRESS OR IMPLIED (INCLUDING WITHOUT LIMITATION, ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OF FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, MERCHANTABILITY, DURABILITY, TITLE, OR RELATED TO THE PERFORMANCE OR NONPERFORMANCE OF ANY SOFTWARE REFERENCED HEREIN OR PERFORMANCE OF ANY SERVICES REFERENCED HEREIN). IN CONNECTION WITH YOUR USE OF THIS DOCUMENTATION, NEITHER RIM NOR ITS RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES, OR CONSULTANTS SHALL BE LIABLE TO YOU FOR ANY DAMAGES WHATSOEVER BE THEY DIRECT, ECONOMIC, COMMERCIAL, SPECIAL, CONSEQUENTIAL, INCIDENTAL, EXEMPLARY, OR INDIRECT DAMAGES, EVEN IF RIM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, INCLUDING WITHOUT LIMITATION, LOSS OF BUSINESS REVENUE OR EARNINGS, LOST DATA, DAMAGES CAUSED BY DELAYS, LOST PROFITS, OR A FAILURE TO REALIZE EXPECTED SAVINGS. This document might contain references to third-party sources of information, hardware or software, products or services and/or third-party web sites (collectively the Third-Party Information). RIM does not control, and is not responsible for, any Third-Party Information, including, without limitation the content, accuracy, copyright compliance, compatibility, performance, trustworthiness, legality, decency, links, or any other aspect of Third-Party Information. The inclusion of Third-Party Information in this document does not imply endorsement by RIM of the Third-Party Information or the third-party in any way. Installation and use of Third-Party Information with RIM's products and services may require one or more patent, trademark, or copyright licenses in order to avoid infringement of the intellectual property rights of others. Any dealings with Third-Party Information, including, without limitation, compliance with applicable licenses and terms and conditions, are solely between you and the third-party. You are solely responsible for determining whether such third-party licenses are required and are responsible for acquiring any such licenses relating to Third-Party Information. To the extent that such intellectual property licenses may be required, RIM expressly recommends that you do not install or use Third-Party Information until all such applicable licenses have been acquired by you or on your behalf. Your use of Third-Party Information shall be governed by and subject to you agreeing to the terms of the Third-Party Information licenses. Any Third-Party Information that is provided with RIM's products and services is provided as is. RIM makes no representation, warranty or guarantee whatsoever in relation to the Third-Party Information and RIM assumes no liability whatsoever in relation to the Third-Party Information even if RIM has been advised of the possibility of such damages or can anticipate such damages. Part number: 10072782 Version 2

3. At the command prompt, type
Action In a BlackBerry Enterprise Server environment that uses a DB2 UDB database, remove the obsolete database record.
Procedure 1. At the command prompt, type

db2cmd

2. At the command prompt, type
3. Type one of the following commands: connect to <database name> connect to <database name> user besadmin Note: The second command results in a password prompt. 4. If the current owner is not the database schema owner, type the following command at the command prompt:
set current schema <schema owner>
where the default <schema owner> value is BESADMIN. 5. At the command prompt, type
delete from MDSAGConfig where substr(ServerURL,1,5) = 'http:' and substr(ServerURL,1,locate(':',ServerURL,6)) in (select replace(substr(ServerURL,1,locate(':',ServerURL,7)),'https:','http:') from MDSAGConfig where substr(ServerURL,1,6) = 'https:')
6. At the command prompt, type

disconnect all

Functional Changes
Feature support for a WLAN-only environment Description In BlackBerry Enterprise Server Version 4.1 SP2 and later, you can create a BlackBerry Enterprise Server environment that supports only WLAN-enabled BlackBerry devices. See the BlackBerry Enterprise Server in a WLAN-only Environment Version 4.1.2 Installation Guide Supplement for more information. improved formats for requests on In BlackBerry Enterprise Server Version 4.1 SP2 and later, the BlackBerry Messaging Agent adds the file IBM Lotus Domino database extension.nsf to requests on IBM Lotus Domino databases. (SDR 94141) optimized mail file polling In BlackBerry Enterprise Server Version 4.1 SP2 and later, the BlackBerry Messaging Agent uses new IBM APIs (NSFDbModifiedTimeByName) to poll mail file databases for changes without having to open the databases. You can prevent this default behaviour. Perform the following actions. 1. On the computer on which you installed the BlackBerry Enterprise Server, start the Registry Editor. 2. In the left pane, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents\ 3. Create the DWORD value DontUseModifiedByName. 4. Type 1 to prevent the functionality, or type 0 to permit the functionality. The BlackBerry Messaging Agent will continue to open mail file databases every hour to confirm that the DSID did not change and to obtain server versions and latency statistics. The BlackBerry Messaging Agent will also continue to poll for message moves and unread message statuses. (SDR 91483) localized Out Of Office automatic text In BlackBerry Enterprise Server Version 4.1 and later, when a user enabled their Out Of Office message from their BlackBerry device, the BlackBerry Messaging Agent used default English text for the message content. In BlackBerry Enterprise Server Version 4.1 SP2 and later, the BlackBerry Messaging Agent updates only the dates in the default message text, so the message displays in the desired language. (SDR 91214)

Feature improved database error reporting
Description In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances (for example, if the Microsoft SQL Server database becomes too large), transaction deadlocks are reported in the log files. In BlackBerry Enterprise Server Version 4.1 SP2 and later, if transaction deadlocks or timeouts occur, the BlackBerry Enterprise Server tries to reconnect, with an increasing delay between attempts, to a default maximum of five attempts. You can also change the default maximum number of retry attempts. Perform the following actions: 1. On the computer on which you installed the BlackBerry Enterprise Server, start the Registry Editor. 2. In the left pane, browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Database\ 3. Create the DWORD value CommandRetryCount. 4. Type a new value for the number of attempts, or type 0 for unlimited attempts. (SDR 91189)
ability to limit the number of error In BlackBerry Enterprise Server Version 4.1 SP2 and later, when the connection to the BlackBerry Configuration messages when database Database drops, error messages are now logged every 60 seconds at trace level 6. connection failures occur You can also change the default error message interval. Perform the following actions: 1. On the computer on which you installed the BlackBerry Enterprise Server or a BlackBerry component, start the Registry Editor.
2. In the left pane, browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Logging Info\<component>\ 3. Create the DWORD value EventLogTimeThreshold. 4. Type a new value, in seconds. (SDR 90217) ability to limit the number of attempts to start a user account In BlackBerry Enterprise Server Version 4.1 SP2 and later, you can limit the number of times the BlackBerry Messaging Agent tries to start a user account. Perform the following actions: 1. On the computer on which you installed the BlackBerry Enterprise Server, start the Registry Editor. 2. In the left pane, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents\ 3. Create the DWORD value InitAttemptLimit. 4. Type a new value for the number of attempts, or type 0 for unlimited attempts. (SDR 88912) improved logging levels In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Messaging Agent reported certain errors at logging level OTHER, which could cause the BlackBerry Alert Service to generate an unnecessary alarm. In BlackBerry Enterprise Server Version 4.1 SP2 and later, the BlackBerry Messaging Agent reports certain errors at logging level DEBUG instead of logging level OTHER. (SDR 87936) new confirmation dialog for changed encryption types In BlackBerry Enterprise Server Version 4.1, you could change the encryption type (for example, from Triple DES to AES) without confirming the change. In BlackBerry Enterprise Server Version 4.1 SP2, a confirmation dialog appears when you change the encryption type. This dialog warns you that users are not be permitted to send or receive messages until they insert their BlackBerry device in the cradle or generate a new encryption key wirelessly. (SDR 85213) improved repeating appointment In BlackBerry Enterprise Server Version 4.1 SP2 and later, when you add new attendees to an existing repeating calendar functionality meeting, the BlackBerry Messaging Agent now tries to guess the pattern of repetition based on the meeting instances and add that pattern to the invitation for the new attendee. In this implementation, the BlackBerry Messaging Agent does not attempt to detect patterns that include the following complications: weekend instances that have been moved monthly patterns on more than one day a month monthly patterns specified as x days from the end of the month

BlackBerry Instant Messaging for Live Communications Server SDR 80118 Previously, if users were using Microsoft Windows Messenger, and they tried to switch conversations using the message indicator, a message queue overflow error message appeared.
BlackBerry MDS Connection Service SDR 80201 In BlackBerry enterprise Server Version 4.1 and later, if you changed the properties for a BlackBerry MDS Connection Service, the changes were not saved. In the BlackBerry Enterprise Server Version 4.1 SP2 and later, this issue is resolved. SDR 78922 In the BlackBerry Enterprise Server Version 4.1, if you created a BlackBerry MDS Connection Server access control push rule with the same name as an access control pull rule, an application error appeared. The same behavior occurred if you created a pull rule with the same name as a push rule. In the BlackBerry Enterprise Server Version 4.1 SP2 and later, this issue is resolved. BlackBerry MDS Services SDR 100855 In BlackBerry Enterprise Server Version 4.1 and later, if you remove a BlackBerry MDS Studio Application, the application record is not removed from the BlackBerry MDS Application Repository. In the BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 88104 In the BlackBerry Enterprise Server Version 4.1 SP1, the BlackBerry MDS Services Properties page title contained unnecessary padding before (Audit Only) appeared. In the BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. BlackBerry Manager SDR 95479 In BlackBerry Enterprise Server Version 4.1 and later, when you remove a user account from the BlackBerry Enterprise Server, the user account is not removed from the BlackBerry MDS Server. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.
BlackBerry Manager SDR 91948 In BlackBerry Enterprise Server Version 4.1 and later, if you resend service books to multiple users at once, you must click OK for each user. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 91507 In BlackBerry Enterprise Server Version 4.1 and later, junior help desk administrators cannot access the Devices Registered properties dialogs. This administrator role should have Delete permission for this screen. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 89278 In BlackBerry Enterprise Server Version 4.1 and later, if you select a user on the Users tab, click Assign to Group, and then click OK without selecting a group for the user, an SQL error appears in the BlackBerry Manager log file. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 88155 In BlackBerry Enterprise Server Version 4.1 and later, the Local Access Control properties dialog for the BlackBerry MDS Connection Service incorrectly appears in the BlackBerry Collaboration Service properties dialog. In BlackBerry Enterprise Server Version 4.1 SP2, you are able to create user groups in the BlackBerry Manager. SDR 88002 In BlackBerry Enterprise Server Version 4.1 and later, if you create a pull rule with a name that is longer than 40 characters, an application error occurs. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87609 In BlackBerry Enterprise Server Version 4.1 and later, if you set an enterprise activation password to expire at a time other than the default (48 hours), the expiry time reverts to the default after you close the Set Activation Password dialog and re-open it. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87255 In the Device Policies properties dialog on the MDS Services tab, the Allow Push Application Install option displays the incorrect UI description. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87162 In BlackBerry Enterprise Server Version 4.1 and later, if you edit and then reapply a group template, a warning message appears (NSD Is Running: Saving to file <path name>), and the BlackBerry Manager and the IBM Lotus Domino server shut down unexpectedly. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 86049 In BlackBerry Enterprise Server Version 4.1 and later, security administrators cannot view the Query Device Status option on the Devices Registered screen. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 85927 In BlackBerry Enterprise Server Version 4.1, if you are using database authentication to connect the BlackBerry Manager to the BlackBerry Configuration Database, and the credentials you supply are not accepted, the BlackBerry Manager does not clear the login credential stored in the registry. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 82677 In BlackBerry Enterprise Server Version 4.1 and later, in some circumstances, if you highlight a user name on the Users tab when there is only one user on the BlackBerry Enterprise Server, the user name might appear multiple times in the bottom pane of the Users tab. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 80832 In BlackBerry Enterprise Server Version 4.1 and later, senior help desk administrators have read-only access to the Add Users dialog on the Servers tab, but full access to the Add Users dialog on the Users tab. This administrator role should have full access to the Add User dialog in all circumstances. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 80383 In BlackBerry Enterprise Server Version 4.1 and later, BlackBerry device administrators could add, copy, and modify software configuration details when they should have read-only permission. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 80350 In BlackBerry Enterprise Server Version 4.1 and later, BlackBerry device administrators and audit BlackBerry device administrators could access several dialogs for which they should have read-only permission on the Servers tab and User Groups List tab. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 80328 In BlackBerry Enterprise Server Version 4.1 and later, if a junior help desk administrator logs in to a remote BlackBerry Manager, this administrator can access and perform the Move User action. This option should be hidden from this administrator role. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 80314 In BlackBerry Enterprise Server Version 4.1 and later, if a junior help desk administrator logs in to a remote BlackBerry Manager, this administrator can access the Edit PIM Sync Global Field Mapping dialog. This option should be hidden from this administrator role. If the administrator tries to edit these field mappings, a Database Update Problem error message appears in the BlackBerry Manager, and error messages appear in the BlackBerry Manager log file. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

BlackBerry Manager SDR 80244 In BlackBerry Enterprise Server Version 4.1 and later, a Clear Statistics option link incorrectly appears on the Collaboration Service tab. This link does not provide any functionality. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 79622 In BlackBerry Enterprise Server Version 4.1 and later, audit security administrators can perform the Export Stats to File task on the Users tab. This administrator role should not have permission to perform this task. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 79600 In BlackBerry Enterprise Server Version 4.1 and later, if you assign a user to a group when no other groups exist in the BlackBerry Domain, an incorrect error message (There are no other groups to copy properties to) appears. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 79532 In BlackBerry Enterprise Server Version 4.1 and later, in some circumstances, the Set Activation Password option does not appear on the User Groups List tab. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 79196 In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, when two BlackBerry Enterprise Servers share the same BlackBerry Configuration Database, if you use the BlackBerry Manager on one BlackBerry Enterprise Server to find a user on another BlackBerry Enterprise Server, user status information displays momentarily and then is not visible. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 78256 In BlackBerry Enterprise Server Version 4.1 and later, if an audit security administrator attempts to map a global IT policy to a user, an application error occurs. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 77891 In BlackBerry Enterprise Server Version 4.1 and later, in the BlackBerry Manager, the Enable S/MIME Message Processing option appears in the Groups template although BlackBerry Enterprise Server for IBM Lotus Domino does not support S/MIME message processing. Do not try to use this option to enable S/MIME message processing. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 77569 In BlackBerry Enterprise Server Version 4.1 and later, if you create message monitors to monitor BlackBerry MDS Services message traffic, the monitors do not persist in the BlackBerry Manager. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 77401 In BlackBerry Enterprise Server Version 4.1 and later, if you assign an invalid PIN number to a BlackBerry MDS Services message monitor definition, an application error message appears. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 77233 In BlackBerry Enterprise Server Version 4.1 and later, if you change the BlackBerry MDS Connection Service server host name to a URL that does not exist, an application error message appears. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 77176 In BlackBerry Enterprise Server Version 4.1 and later, if the BlackBerry MDS Services is installed on a remote computer, and you create a new BlackBerry MDS Services device policy but leave the Policy Name field blank, an application error appears and the BlackBerry Manager might stop responding. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 76827 In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, when two BlackBerry Enterprise Servers share the same BlackBerry Configuration Database, if you attempt to clear the user statistics, only some of the statistics are successfully removed. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. BlackBerry Messaging Agent SDR 99713 In BlackBerry Enterprise Version 4.1 and later, if the BlackBerry Messaging Agent encounters a COM exception error when querying the BlackBerry Configuration Database, the BlackBerry Messaging Agent flags that it should check to see if the database connection pool requires reinitialization. If the database connection pool does not require reinitialization, the BlackBerry Messaging Agent does not reset the flag and no additional database functions occur. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 97967 In BlackBerry Enterprise Server Version 4.1 and later, when you remove an inactive user account from the BlackBerry Enterprise Server, the BlackBerry Messaging Agent deletes the wrong profile document. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 96105 In BlackBerry Enterprise Server Version 4.1 and later, if you change a user on the BlackBerry Enterprise Server to a different messaging and collaboration server, the BlackBerry Enterprise Server continues to scan the previous messaging server for modifications to the mail file. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87741, SDR 87742

BlackBerry Messaging Agent SDR 87737 In BlackBerry Enterprise Server Version 4.1 and later, in some circumstances, if you attempt to perform an administrative action, the action might fail if the BlackBerry Messaging Agent is unable to start a thread. The cause of the failed attempt might not be added to the BlackBerry Messaging Agent log file. In BlackBerry Enterprise Server Version 4.1 and later, if an exception occurs while the BlackBerry Enterprise Server checks for messages and the BlackBerry Enterprise Server cannot process a message, an APB might not be sent. In BlackBerry Enterprise Server Version 4.1 and later, if an exception occurs while the BlackBerry Enterprise Server checks for messages and the BlackBerry Enterprise Server cannot process a message, an APB might not be sent. In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Messaging Agent returns Access Control List groups in address lookup results. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87226 In BlackBerry Enterprise Server Version 4.1 and later, if time zone data exists in the BlackBerry Configuration Database for the BlackBerry Synchronization Server, it overwrites the equivalent information that is hard-coded into the BlackBerry Messaging Agent. In BlackBerry Enterprise Server Version 4.1 and later, when the BlackBerry Messaging Agent starts and all threads are working as expected, it reports this using Event 5001. This event generates a trap that is incorrectly reported in the SNMP HungThreadTrap. In certain circumstances, when you start up the BlackBerry Enterprise Server, the SNMP trap console incorrectly reports a non responsive thread. In BlackBerry Enterprise Server Version 4.1 and later, if you import a user from a BlackBerry Enterprise Server earlier than Version 4.0, when the user connects their BlackBerry device to the BlackBerry Desktop Manager, a Redirection settings could not be saved because the messaging system is not available error occurs and the BlackBerry Messaging Agent does not send service books to the BlackBerry device. In BlackBerry Enterprise Server Version 4.1 and later, if you deactivate a users BlackBerry device using the Erase Data and Disable Device task in the BlackBerry Manager, the user profile information is not completely cleared. When the user attempts to reactivate their BlackBerry device by connecting it to the BlackBerry Desktop Manager, the BlackBerry Messaging Agent sends service books to the BlackBerry device but enterprise activation does not occur. In BlackBerry Enterprise Server Version 4.1 and later, if a user creates a task with a reminder set one day before the task is due in their desktop email program, the BlackBerry Messaging Agent changes the reminder during reconciliation to the BlackBerry device the reminder appears one day before the user created the task. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 86483 In BlackBerry Enterprise Server Version 4.1 and later, if a user added an email address to an existing contact on the BlackBerry device and then synchronized the BlackBerry device to the IBM Lotus Notes client, the user could not send a message from the IBM Lotus Notes client using the contact name that was edited on the BlackBerry device. In BlackBerry Enterprise Server Version 4.1 and later, if a user receives a message containing an attachment that is Huffman encoded, the BlackBerry Messaging Agent logs a Unknown type of compression technique error, sends an APB message notification to the users BlackBerry device, and does not deliver the message. In BlackBerry Enterprise Server 4.1 and later, if the BlackBerry Messaging Agent issues a stop command to a worker thread during threadpool optimization and does not receive a response, the BlackBerry Messaging Agent continues to wait indefinitely for a response. In BlackBerry Enterprise Server Version 4.1 SP2, the BlackBerry Messaging Agent stops waiting for a response after 60 seconds, does not delete the thread, and creates the following message in the log file: Thread::Stop() - Timeout exceeded. Thread not stopped. thread Id=0xBA4, Handle=0x5E0, timeout=60000 ms SDR 86306 In BlackBerry Enterprise Server Version 4.1 and later, if a user changes BlackBerry devices using the BlackBerry Desktop Manager and email messages are sent to the user while the old BlackBerry device was turned off, the pending email messages are not sent to the new BlackBerry device when it is turned on. In BlackBerry Enterprise Server Version 4.1 and later, when a user updates a contacts first or last name on their BlackBerry device, the BlackBerry Messaging Agent removes the content of the Full Name field and replaces it with the first and last name. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 85727 In BlackBerry Enterprise Server Version 4.1 and later, if you install the BlackBerry Enterprise Server with an evaluation license key while the Simple Network Management Protocol (SNMP) services is running, license information values in the BlackBerry Enterprise Server Management Information Base (MIB) file for dispConfigLicenseTotal, dispConfigLicenseUsed, and dispConfigLicenseRemaining are not correct. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 85277 In BlackBerry Enterprise Server Version 4.1 and later, if you prevent wireless organizer data (PIM) synchronization for a user, those changes are displayed in the users properties in the BlackBerry Manager, but the BlackBerry Messaging Agent continues to permit wireless organizer data synchronization. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

Setup program SDR 78977 In BlackBerry Enterprise Server Version 4.1 and later, when you upgraded the BlackBerry Enterprise Server the setup program selected Windows authentication as the default authentication method to the BlackBerry Configuration database. If you had previously selected database authentication when installing the BlackBerry Enterprise Server, this choice was not detected by the setup program. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 77498 In BlackBerry Enterprise Server Version 4.1 and later, when upgrading the BlackBerry Enterprise Server with BlackBerry MDS Services, the BlackBerry MDS Services might start after the BlackBerry Enterprise Server restarts during the upgrade and the setup program cannot complete successfully. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 76573 In BlackBerry Enterprise Server Version 4.1 and later, if you enter the SRP address with spaces, you cannot validate the SRP ID and key. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 68142 In BlackBerry Enterprise Server Version 4.1 and later, you had to perform manual steps after completing the setup program to associate a BlackBerry Enterprise Server with an instance of BlackBerry MDS Services. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 65361 In BlackBerry Enterprise Server Version 4.1 and later, the setup program does not validate the proxy connection information that you type to confirm that the information is expected (for example, numbers in the port field). In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 64673 In BlackBerry Enterprise Server Version 4.1 and later, the setup program did not confirm that the account with which you installed the BlackBerry Enterprise Server was part of the Local Administration group. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. Wireless calendar synchronization SDR 94274 In BlackBerry Enterprise Server 4.1 and later, when a meeting organizer updates the location of a recurring meeting from their desktop email program, the location does not synchronize to the BlackBerry device. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 88416 In BlackBerry Enterprise Server 4.1 SP1, if a meeting organizer updates a meeting to select the Pencil In option from their BlackBerry device, the change is not saved in the meeting on the BlackBerry device but does reconcile to the users desktop email program. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87994, SDR In BlackBerry Enterprise Server 4.1 and later, if a meeting organizer creates a recurring meeting with the Pencil In option 87599 selected from their desktop email program, the recurrence pattern is incorrect when the meeting invitees receive the invitation on their BlackBerry devices. When invitees accept the meeting, their status might show as Tentative on the meeting organizers BlackBerry device, but appear as Accepted on the meeting organizers desktop email program. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87780 In BlackBerry Enterprise Server Version 4.1 and later, if an exception error occurs while the BlackBerry Messaging Agent is reconciling an update to an instance of a recurring meeting, the update might not be delivered to the users BlackBerry device. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87649 In BlackBerry Enterprise Server Version 4.1 and later, if you receive your service books during enterprise activation, the BlackBerry Messaging Agent does not include the flags to prevent users from inviting attendees to all-day meetings that they create on their BlackBerry device. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87644 In BlackBerry Enterprise Server 4.1 and later, when the BlackBerry Messaging Agent reconciles a deleted calendar appointment, it might also generate an unnecessary Unable to save calendar state document error message in the log file. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87550 If BlackBerry Enterprise Server Version 4.1 and later, when a meeting organizer edits an instance of a recurring meeting and sends the updated meeting invitation, the organizer receives the This meeting update conflicts with an update that was sent to the device error message and the attendees do not receive the meeting update. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 87534 In BlackBerry Enterprise Server 4.1 and later, when a meeting attendee declines an updated recurring meeting invitation from the BlackBerry device after first accepting the original recurring meeting invitation, all meeting instances are removed from the organizers BlackBerry device and mail client, but remain on the attendees BlackBerry device and mail client. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

Wireless calendar synchronization SDR 86567 In BlackBerry Enterprise Server Version 4.1 and later, an organizers meeting update might be unsuccessful if the sequence number of the meeting on the BlackBerry device is higher than the sequence number of the meeting on the messaging server (for example, if an organizer updates a meeting while their BlackBerry device is outside of a wireless coverage area and at the same time invitees are sending acceptances to the original meeting). The BlackBerry Messaging Agent is processing the meeting acceptance to the new appointment sent from the invitees BlackBerry device, so the messaging server does not send the update from the meeting organizer. In BlackBerry Enterprise Server Version 4.1 SP2, meeting invitees receive the organizers update successfully and respond to the updated meeting. SDR 85900 In BlackBerry Enterprise Server 4.1 and later, a meeting organizer might have received unnecessary corrections to alarm settings or cancellations of an instance of a recurring meeting. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 79542 In BlackBerry Enterprise Server 4.1 and later, if a meeting organizer updates the location of an instance of a recurring meeting from their BlackBerry device, and a meeting invitee tentatively accepts the invitation from their BlackBerry device, the meeting organizer receives an acceptance on their desktop email program and the invitees status remains Invited on the meeting organizers BlackBerry device. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 79017 In BlackBerry Enterprise Server 4.1 and later, when a meeting invitee tentatively accepts an invitation from their BlackBerry device, the meeting organizer receives an acceptance instead of a tentative acceptance. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved. SDR 77637 In BlackBerry Enterprise Server Version 4.1 and later, if you move users repeatedly between BlackBerry Enterprise Servers in a BlackBerry Domain, error messages appear on the source BlackBerry Enterprise Server. In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.
The following issues are believed to be fixed in this software release, but have not been confirmed to be closed:
BlackBerry Configuration Database SDR 97058 SDR 94195 In BlackBerry Enterprise Server Version 4.1 and later, you cannot specify a path at the command prompt to the BESMgmt.cfg file when using the CreateDB tool. You were required to change the script root directory in the BESMgmt.cfg file instead. In BlackBerry Enterprise Server Version 4.1 and later, if you attempt to upgrade the BlackBerry Configuration Database and you have changed the machine name of the computer since creating the BlackBerry Configuration Database, the upgrade will not complete successfully. In BlackBerry Enterprise Server Version 4.1 and later, when you install a version of the BlackBerry Enterprise Server and specify a BlackBerry Configuration Database that is at a higher version (for example, a BlackBerry Enterprise Server Version 4.1 SP1 and a BlackBerry Configuration Database Version 4.1 SP2), the BlackBerry Configuration Database reports that the schema is not at the most current version. When the setup program checks the IsCurrent value, the BlackBerry Configuration Database supplies False instead of True. In BlackBerry Enterprise Server Version 4.1 and later, if the BlackBerry Configuration Database contains multiple entries in certain database tablesan expected result of merging two BlackBerry Configuration Databases into onethe database job that purges BlackBerry MDS Connection Service messages does not complete successfully.

SDR 98205 SDR 91525 SDR 87023
BlackBerry Attachment Service SDR 99041 SDR 98475 SDR 92514 SDR 90808 In certain circumstances, an error message displays when a user attempts to open an attachment on the BlackBerry device. Portable Document Format (PDF) attachments do not display layout or characters correctly in the BlackBerry Browser. In certain circumstances, PDF attachments created with Cognos PDF Server do not render correctly on the BlackBerry device. In certain circumstances, if a user opens a Microsoft Word attachment on a BlackBerry Connect device, bullet colors do not display correctly.
BlackBerry Collaboration Service SDR 101462, SDR If your instant messaging environment is GroupWise Messenger, you cannot turn off the default setting to show a mobile icon. 93661 This feature is only supported on GroupWise Messenger Version 2.x, so if your instant messaging environment contains users on GroupWise Messenger Version 1.x, those users cannot send instant messages from their BlackBerry devices. Workaround: In the BlackBerry Configuration Database, in the IMConfig table, edit the ShowMobile field using the following values: SDR 92584 Type 0 to prevent support for showing mobile icons. Type 1 to permit support for showing mobile icons.
If your instant messaging environment is IBM Lotus Sametime, when a user adds a contact to the Buddy List in their desktop instant messaging program and then starts a conversation with that contact, if the contact receives the invitation on their BlackBerry device the user on the desktop instant messaging program appears to be offline. When the contact joins the conversation on their BlackBerry device, the user on the desktop instant messaging program continues to appear offline until they type the first message of the conversation.
BlackBerry Configuration Database SDR 102857 When you upgrade your BlackBerry Configuration Database to Version 4.1 SP2, if the MDSConfig table contains rows where the ServerConfigID is null, the upgrade fails and the [10000] (09/11 23:28:08.243):{0xEEC} SQL Error Message from CBESDBInstaller::ExecuteSql.executeDirect: SQLSTATE: 23000 Native error:515 Message: Cannot insert the value NULL into column 'ServerConfigId',table 'BESMgmt.dbo.RelationSCMDS'; column does not allow nulls. INSERTfails. error appears in the setup program log file. Workaround: Before you perform the upgrade, confirm that no nulls exist using the following script: 1. At the command prompt, type

osql -E -d <database name>
delete from MDSConfig where ServerConfigID is NULL
Note: After this script completes, you can proceed with the upgrade. If this script reports that 0 rows are affected, you can also proceed with the upgrade. SDR 102605 When you use the DbCopyData tool to copy BlackBerry Configuration Database information from SQL Server to DB2 UDB, errors occur because of a missing file and the copy does not complete successfully.
BlackBerry Configuration Panel SDR 101690 In certain circumstances, if you change the path to the folder where the BlackBerry services create log files from a local drive to a network drive, the BlackBerry Configuration Panel completes the process, but the BlackBerry services cannot create logs in the network drive. Workaround: Specify a local drive as the destination folder for the log files and contact BlackBerry Technical Support BlackBerry Dispatcher SDR 98848 SDR 98703 SDR 79504 If an All Points Bulletin (APB) fails, the BlackBerry Dispatcher log file does not display that a failure occurred. In certain circumstances, if you set up a BlackBerry device during a period of high volume traffic on the BlackBerry Enterprise Server, the BlackBerry Dispatcher remote procedure call (RPC) times out. In certain circumstances, if you move a user from one BlackBerry Enterprise Server to another, errors display in the BlackBerry Dispatcher log file
BlackBerry Instant Messaging for Microsoft Live Communications Server SDR 99734 SDR 99593 SDR 99007 SDR 98758 SDR 96321 SDR 96070 If users are using Office Communicator, and they click the Accept&Add menu option on an incoming invitation from a contact that has never been in their contact list before, a setFocusField error appears. If users add themselves to their contact list using their user name and instead of their full email address, then delete themselves, a java exception appears and the user is logged out. If users are on a server with Public IM Connectivity turned on, and they try to involve Public Instant messaging contacts in a conference, an error message appears. If users block a contact using Office Communicator they can still send messages to that contact and receive messages from that contact. If users have a contact in the default group, and they select the Remove from Group menu option, a Command Failed error appears. If users are using Office Communicator on a BlackBerry device, the Remove Contact from Group option does not appear in the menu list.

SDR 79987 SDR 64736

BlackBerry Instant Messaging for Sametime SDR 100946 SDR 94672 SDR 82350 SDR 82113 If the BlackBerry MDS Connection Service and the BlackBerry Collaboration Service are disabled on the BlackBerry Enterprise Server, users who were online when the services were disabled are not notified that they are no longer connected. The <Start Typing Here> message that appears in the text entry field might not disappear when users start typing in that field. If users have a large contact list, when they log on to their account using their BlackBerry device, highlight a group, and select the Add Person menu option while the contact list is loading, an illegal argument exception. appears If a user creates two groups with the same name that differ only by capitalization on their desktop computer, and add at least one contact to each group, then log into the same account on their handheld client, highlight the first group in the contact list and select Add Person from the menu, an illegal argument exception appears. If a single chat between a BlackBerry device user and a desktop computer user is initiated by the device user and the desktop user invites other participants to the existing chat window, then the device that originated the single chat will receive an invitation instead of having the single chat window on the device converted to a meeting.

SDR 74118

BlackBerry MDS Services SDR 102745 The BlackBerry MDS Services lists BlackBerry Collaboration Services in its list of available BlackBerry MDS Connection Services. If you select a BlackBerry Collaboration Service instead of a BlackBerry MDS Connection Service, attempts to activate users for BlackBerry MDS Services do not complete successfully. Workaround: Remove instances of BlackBerry Collaboration Services from the BlackBerry MDS Connection Service Definition list of the BlackBerry MDS Services. SDR 102933 If you move a user from one BlackBerry Enterprise Server to another BlackBerry Enterprise Server, the BlackBerry MDS Studio applications supported only by the first BlackBerry Enterprise Server are not removed from the users BlackBerry device.
BlackBerry MDS Services SDR 101731, SDR 100803 If you are upgrading your BlackBerry environment from Version 4.1 and later to Version 4.1 SP2, and you add a new instance of BlackBerry MDS Connection Service created at Version 4.1SP2, the BlackBerry MDS Services adds this instance to the list of available BlackBerry MDS Connection Services. If you do not intend to use this instance and manually stop the service, the BlackBerry MDS Services retains the instance on its list of available BlackBerry MDS Connection Services. When activating BlackBerry MDS Runtime on BlackBerry devices, if the BlackBerry MDS Services attempt to connect to the stopped instance of the BlackBerry MDS Connection Service, the activation fails. Workaround: If you have a stopped instance of the BlackBerry MDS Connection Service in your BlackBerry environment, manually remove this instance from the BlackBerry MDS Connection Service Definition list of the BlackBerry MDS Services. SDR 100135 SDR 98753 After you removed a user account from the BlackBerry Enterprise Server, the users BlackBerry device is not removed from the BlackBerry MDS Application Repository. The BlackBerry MDS Application Repository server logs the content of secure messages when running in DEBUG mode.

SDR 99040

BlackBerry Synchronization Service SDR 99972 SDR 98110 SDR 98044 SDR 97657 SDR 96143 SDR 96027 SDR 95386 SDR 82813 SDR 75270 In certain circumstances, task list reminders on the BlackBerry device do not synchronize to the IBM Notes client. In certain circumstances, enterprise activation might not complete if the delivery status of the initialization verification packet is received by the BlackBerry device subsequent to a new BlackBerry device request. In certain circumstances, you cannot stop the BlackBerry Synchronization Service. Workaround: Use the task manager to stop the BlackBerry Synchronization Service. User PIN information does not synchronize wirelessly if a user changes BlackBerry devices or clears the BlackBerry device and re-initializes enterprise activation. The BlackBerry Synchronization Service log file does not log all events. The BlackBerry Synchronization Service and BlackBerry Synchronization Connector log files do not have a description for event ID [45001]. If conflict resolution for the BlackBerry Enterprise Server is set to Device Wins and wireless synchronization is turned off, filter updates on the BlackBerry device are not synchronized to BlackBerry Manager. If you create a new filter, delete a filter, and then move a filter from a BlackBerry device within a short period of time, the BlackBerry Synchronization Service reverts the changes. When creating a contact on the BlackBerry device, if a user modifies the name format preferences, the changes are not synchronized to the desktop email program.
Setup program SDR 101957 If you are installing the BlackBerry Enterprise Server Version 4.1 SP2, and you select Ukraine as your country, the setup program automatically populates the SRP connection with incorrect information. Workaround: 1. In the Host field, delete srp.uk.blackberry.net. 2. Type srp.ua.blackberry.net 3. Continue with the installation process. SDR 101910 When you upgrade from BlackBerry Enterprise Server Version 4.1 and later to BlackBerry Enterprise Server Version 4.1 SP2, and during the upgrade you add support for instant messaging, the setup program does not remove the placeholder record in the IMConfig table when it adds the new record listing the computer where you installed the BlackBerry Collaboration Service. As a result, when you view the IM to BES Mappings list in the BlackBerry Manager, you see the invalid computer name IM-1. Workaround: Do not select the invalid computer name when mapping instances of your BlackBerry Enterprise Servers to a BlackBerry Collaboration Service. SDR 101698 In certain circumstances, when you install the BlackBerry Enterprise Server Version 4.1 and later, if you specify a network path as the destination folder for the log files, the installation process completes but the BlackBerry services cannot create logs in the network drive. Workaround: After you complete the setup program, confirm that your log files appear on the network drive. If not, use the BlackBerry Configuration Panel to specify a local drive as the destination folder for the log files and contact BlackBerry Technical Support. SDR 100337 If your database environment is Microsoft SQL Server 2005, the setup program does not change the authentication mode to Mixed Mode when the user requests the change. The setup program creates the BlackBerry Configuration Database, but cannot create the BlackBerry MDS Services databases, and the DB upgrade failed. Database connection attempt failed error occurs. Workaround: You must change your database server to Mixed Mode before starting the setup program. See the BlackBerry Enterprise Server Installation Guide for more information about database environment settings required by the BlackBerry Enterprise Server. Wireless calendar synchronization SDR 98170 SDR 96592 If a meeting invitee tentatively accepts a simple meeting from their BlackBerry device, the BlackBerry Messaging Agent does not change their status in the invitation. If a meeting organizer creates an all day event from their BlackBerry device while in one time zone, and their desktop email program resides in another time zone, the BlackBerry Messaging Agent synchronizes the event to the day before the day selected by the organizer. If a meeting invitee accepts an information update on their BlackBerry device, the BlackBerry Messaging Agent applies the change to the users BlackBerry device but not their desktop email program. If a meeting organizer creates an invitation that includes a room resource, the BlackBerry Messaging Agent displays the status of the room as declined. If a meeting organizer updates the room resource on the desktop email program for a recurring appointment, the location of the appointment is not updated on invitees BlackBerry devices. If a meeting invitee declines an invitation from their BlackBerry device, the BlackBerry Messaging Agent does not send their status to the organizers BlackBerry device, so the invitee continues to receive updates. If a meeting attendee deletes a meeting that occurs in the past, the BlackBerry Messaging Agent sends the decline notice to the meeting organizer. If a meeting organizer adds comments to an exception of a recurring meeting, the BlackBerry Messaging Agent adds the content to the Description field of all instances of the meeting. If a meeting organizer cancels a single exception of a recurring meeting from their BlackBerry device, the BlackBerry Messaging Agent adds the start and end times of the other recurrences to the subject line of the cancellation notice. If a meeting organizer receives an invitees acceptance notice on their desktop email program but not on their BlackBerry device, the invitees status remains at invited.

BlackBerry Enterprise Server for IBM Lotus Domino Compatibility Matrix January 31, 2011
2010 Research In Motion Limited. All rights reserved. www.rim.com

Page: 1

Operating Systems: BlackBerry Enterprise Server and 5.0.2 5.0.1 5.0.0 BlackBerry Enterprise Server Components 32-bit Windows Server 2000 SP4 x x x Windows Server 2003 x x x Windows Server 2003 SP1 Windows Server 2003 SP2 Windows Server 2003 R2 Windows Server 2003 R2 SP2 Windows Server 2008 SP1 Windows Server 2008 SP2 64-bit Windows Server 2003 x x x x x x x x x x x x
4.1.7 x x x x x x x x x x 4.1.7 x x x x x x x
4.1.6 4.1.5 x x x x x x x x x x x x x x x x x x x x

4.1.4 x x x

4.1.3 4.1.2 x x x x x x
Windows Server 2003 SP1 x Windows Server 2003 SP2 Windows Server 2003 R2 SP2 Windows Server 2008 SP1 x Windows Server 2008 SP2 Windows Server 2008 R2 Operating System:

BB Manager

x x x 4.1.4 x x x x
5.0.2 5.0.1 5.0.0 32-bit Windows 2000 SP4 NA NA NA Windows Server 2003 NA NA NA Windows Server 2003 SP1 Windows Server 2003 SP2 Windows Server 2003 R2 Windows Server 2003 R2 SP2 Windows Server 2008 SP1 Windows Server 2008 SP2 Windows XP Professional SP1 Windows XP Professional SP2 Windows XP Professional SP3 Windows Vista SP1 Windows Vista SP2 Windows 7 64-bit Windows Server 2003 Windows Server 2003 SP1 Windows Server 2003 SP2 Windows Server 2003 R2 SP2 Windows Server 2008 SP1 Windows Server 2008 SP2 Windows Server 2008 R2 Windows 7
NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA
4.1.6 4.1.5 x x x x x x x x x x x x
4.1.3 4.1.2 x x x x x x x x
NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA

x x x x

x x x x x

Page: 2

Server Virtualization: BlackBerry Enterprise Server and 5.0.2 5.0.1 5.0.0 BlackBerry Enterprise Server Components VMware Infrastructure 3.0.0 x x x VMware Infrastructure 3.0.1 x VMware Infrastructure 3.0.2 x VMware Infrastructure 3.5.0 VMware vSphere 4 Microsoft Hyper-V Server 2008 Microsoft Hyper-V Server 2008 R2 x x x x x x x

4.1.7

4.1.6 4.1.5

4.1.4

4.1.3 4.1.2 x

Mail Server

5.0.2 5.0.1 5.0.0 IBM Lotus Domino v6.5.4

4.1.3 4.1.2 x x x

IBM Lotus Domino v6.5.5 x IBM Lotus Domino v6.5.6 x IBM Lotus Domino v7.0.0 x IBM Lotus Domino v7.0.1 x IBM Lotus Domino v7.0.2

x x x x

x x x

x x x

IBM Lotus Domino v7.0.3 x IBM Lotus Domino v7.0.4 x IBM Lotus Domino v8.0.0 x IBM Lotus Domino v8.0.1 IBM Lotus Domino v8.0.2 IBM Lotus Domino v8.5.0 x IBM Lotus Domino v8.5.1 IBM Lotus Domino v8.5.2 IBM Lotus Domino v9.0 BES Domino Server
5.0.2 5.0.1 5.0.0 IBM Lotus Domino v6.5.4 x IBM Lotus Domino v6.5.5

4.1.7 x

4.1.6 4.1.5 x

4.1.4 x

IBM Lotus Domino v6.5.6 x IBM Lotus Domino v7.0.0 x IBM Lotus Domino v7.0.1
IBM Lotus Domino v7.0.2 x IBM Lotus Domino v7.0.3 x IBM Lotus Domino v7.0.4 x IBM Lotus Domino v8.0.0 x
IBM Lotus Domino v8.0.1 x x x x IBM Lotus Domino v8.0.2 IBM Lotus Domino v8.5.0 x IBM Lotus Domino v8.5.1 IBM Lotus Domino v8.5.2 IBM Lotus Domino v9.0 *** Note: on a 64-bit OS, you must use the 32-bit edition of Domino for installation with the BES.

Page: 3

Database Server 32-bit
5.0.2 5.0.1 5.0.0 MSDE 2000 SP3 x Microsoft SQL Server 2000 SP4 x Microsoft SQL Server 2005 x Microsoft SQL Server 2005 SP2 x Microsoft SQL Server 2005 SP3 Microsoft SQL 2005 Express x Microsoft SQL 2005 Express SP2 Microsoft SQL 2005 Express SP3

4.1.7 x x x

4.1.6 4.1.5 x x

4.1.4 x

4.1.3 4.1.2

x x x x

x x x
Microsoft SQL Server 2008 x Microsoft SQL Server 2008 SP1 Microsoft SQL Server 2008 SP2 Microsoft SQL 2008 R2 Microsoft SQL 2008 Express x Microsoft SQL 2008 Express SP1 Microsoft SQL 2008 R2 Express IBM DB2 8.2.0 x IBM DB2 9.5 x IBM DB2 Express 8.2.0 x IBM DB2 Express 9.5 x 64-bit Microsoft SQL Server 2005 x Microsoft SQL Server 2005 SP2 Microsoft SQL Server 2005 SP3 Microsoft SQL Server 2008 x Microsoft SQL Server 2008 SP1 Microsoft SQL Server 2008 SP2 Microsoft SQL 2008 R2 Microsoft SQL 2008 Express x Microsoft SQL 2008 Express SP1 Microsoft SQL 2008 R2 Express Web Browser: BlackBerry Enterprise Server and BlackBerry Enterprise Server Components Microsoft Internet Explorer 6.0 Microsoft Internet Explorer 7.0 Microsoft Internet Explorer 8.0

x x x x x x x

x x x x x x x x x

x x x x x x x x x

x x x

5.0.2 5.0.1 5.0.0

NA NA NA NA NA NA NA NA NA

4.1.6 4.1.5

4.1.3 4.1.2

Page: 4

Web Browser for Accessing: BlackBerry Enterprise Server
Administration (BAS-WC) & BMS

5.0.2 5.0.1 5.0.0 x

4.1.6 4.1.5

4.1.3 4.1.2

Microsoft Internet Explorer 6.0 x Microsoft Internet Explorer 7.0 Microsoft Internet Explorer 8.0 Mozilla Firefox 3.6 Google Chrome 4.0 Safari 4 for Mac .NET Runtime Microsoft.NET v1.1 MS.NET v2.0 MS.NET v3.0 MS.NET v3.5

5.0.2 5.0.1 5.0.0

Referenced Compatibility Notes: BlackBerry Enterprise Server will currently not install under this platform. Database version bundled with respective BlackBerry Enterprise Server service pack or major release. For MDSS/MDS-IS, refer to BlackBerry KB14930 for more information. Installer will not permit the install on v4.1.6 and below. BlackBerry Administration Service 5.x is dependent on the browser version. USB device managment not supported

Page: 5

2010 Research In Motion Limited. All rights reserved. BlackBerry, RIM, Research In Motion, SureType, SurePress 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. IBM, Domino, Lotus, and DB2 are trademarks of International Business Machines Corporation. Microsoft, Internet Explorer, Hyper-V, SQL Server, Windows, Windows Server and Windows Vista are trademarks of Microsoft Corporation. Google and Google Chrome are trademarks of Google Inc. Mozilla and Firefox are trademarks of Mozilla Foundation. VMware is a trademark of VMware, Inc. Safari is a trademark of Apple Inc. All other trademarks are the property of their res pective owners. This documentation including any and all documentation incorporated by reference herein, including but not limited to those p rovided or made available by hyperlink, 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, trustwort hiness, 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 do es 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, REPRESENT ATIONS 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 THE 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 LIABILIT Y 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 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 C OMPANIES, 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. Some airtime service providers may not offer Internet browsing functionality with a subscription to BlackBerry Internet Serv ice. Check with your service provider for availability, roaming arrangements, service plans and features. Installation or use of Third Party Products and Services with RIMs 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 sol ely 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 RIMs 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 o f 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. Certain features outlined in this documentation require a minimum version of BlackBerry Enterprise Server, BlackBerry Enter prise Server Express, BlackBerry Desktop Software, and/or BlackBerry Device Software. 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.

Research In Motion Limited 295 Phillip Street Waterloo, ON N2L 3W8 Canada Research In Motion UK Limited Centrum House 36 Station Road Egham, Surrey TW20 9LF United Kingdom

Published in Canada

Page: 6