BlackBerry Enterprise Server for IBM Lotus Domino

BlackBerry Enterprise Server for Microsoft
Exchange
Version 4.1 Service Pack 6 Maintenance Release 7 (Hotfix)
Release Notes
BlackBerry Enterprise Server for Microsoft Exchange
©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 Acrobat are trademarks of Adobe Systems Incorporated. AOL is a trademark of AOL LLC. IBM, Domino, and Lotus are trademarks of
International Business Machines Corporation. Microsoft, Excel, and Windows are trademarks of Microsoft Corporation. All other trademarks are the
property 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
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.
2
Release Notes
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 might not offer Internet browsing functionality with a subscription to the
BlackBerry® Internet Service. Check with your service provider for availability, roaming arrangements, service plans and 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.
Certain features outlined in this documentation require a minimum version of BlackBerry® Enterprise Server, 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.
Last modified: 10 July 2009
Document ID: 25680826 Version 2
3
BlackBerry Enterprise Server for Microsoft Exchange
Related resources
Guide
Information
BlackBerry Enterprise Server Installation Guide
•
•
system requirements
installation instructions
BlackBerry Enterprise Server Upgrade Guide
•
•
system requirements
upgrade instructions
BlackBerry Enterprise Server Feature and Technical Overview
•
•
•
BlackBerry® Enterprise Server features
system architecture
data workflows
BlackBerry Enterprise Server Administration Guide
•
•
system setup and management
BlackBerry device implementation instructions
Verify the system requirements
Requirement
Description
software version
This maintenance release works with BlackBerry® Enterprise Server version 4.1 SP6 for Microsoft®
Exchange®.
1.
On the taskbar, click Start > Settings > Control Panel or Start > Control Panel.
2. Double-click Add or Remove Programs.
3. In the list of currently installed programs, click BlackBerry Enterprise Server for Microsoft Exchange.
4. Click Click here for support information.
5. Verify that the version number is 4.1.6 (Bundle 30, 60, 73, 92, 105, 144, or 170).
remote components
You do not need to install this maintenance release on a remote computer that hosts a BlackBerry
Attachment Service, BlackBerry Manager, BlackBerry Router, BlackBerry Collaboration Service, or
BlackBerry MDS Connection Service.
original installation media
The maintenance release installation program requires access to the installation media that was used to
install the BlackBerry Enterprise Server. Depending on how the software was installed, this might be a
product CD or a network location.
Install the maintenance release
1.
While logged in to the computer that hosts the BlackBerry Enterprise Server, in Windows® Services, stop all
BlackBerry Enterprise Server services.
2. Close the BlackBerry Configuration Panel.
3. Double-click besx416mr7.zip.
4. Extract the installation files to a local drive on your computer.
5. Browse to the location of the setup program files.
6. Double-click besx416mr7.msp to run the executable.
7. Click Update.
8. Complete the configuration screens.
9. Click Finish.
10. In Windows Services, restart all BlackBerry Enterprise Server services.
Verify the maintenance release installation
1.
On the taskbar, click Start > Settings > Control Panel or Start > Control Panel.
2. Click Add or Remove Programs.
3. In the list of programs, click BlackBerry Enterprise Server for Microsoft Exchange.
4. Click Click here for support information.
4
Release Notes
5. Verify that the version number is 4.1.6 MR7 (Hotfix) (Bundle 174).
Fixed issues
Issues that are marked with an asterisk (*) are fixed in this maintenance release. All other issues were fixed in previous
maintenance releases.
BlackBerry Attachment Service
SDR 184864
In BlackBerry Enterprise Server version 4.1 SP4 or later, the upgrade process for a maintenance release reset the value for the
AllowRemoteServices registry key to 0.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
SDR 203140
In BlackBerry Enterprise Server version 4.1 SP2, if the user sent a malformed attachment, the BlackBerry Attachment Service
might stop running unexpectedly.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
SDR 205295
In BlackBerry Enterprise Server version 4.1 SP6, if the BlackBerry Attachment Service and BlackBerry MDS Integration Service
were installed remotely, the BlackBerry Controller did not start and the error message “Error 1069: the service did not start due
to logon failure” appeared.
In BlackBerry Enterprise Server version 4.1 SP6 MR2, this issue is resolved.
SDR 216533
In BlackBerry Enterprise Server version 4.1 SP6, in certain circumstances, when the BlackBerry Attachment Service processed
Microsoft® Word or Adobe® Acrobat® documents, service issues might have occurred.
In BlackBerry Enterprise Server version 4.1 SP6 MR3, this issue is resolved.
SDR 251215
In BlackBerry Enterprise Server version 4.1 SP4 or later, the BlackBerry device could not open Microsoft® Excel® attachments if
the spreadsheet included more than 99 worksheets.
In BlackBerry Enterprise Server version 4.1 SP6 MR4 and later, this issue is resolved.
SDR 278003,
SDR 278012, SDR
278031, SDR
278437
In earlier versions of the BlackBerry Enterprise Server, security vulnerabilities existed in the PDF distiller of some released
versions of the BlackBerry Attachment Service. These vulnerabilities could have allowed a malicious individual to send an email
message containing a specially crafted PDF file, which when opened for viewing on a BlackBerry smartphone, could have caused
memory corruption and could have possibly led to arbitrary code execution on the computer that the BlackBerry Attachment
Service runs on.
In BlackBerry Enterprise Server version 4.1 SP6 MR4, this issue is resolved. For more information, visit www.blackberry.com/btsc
to read KB17118.
SDR 314287
In earlier versions of the BlackBerry Enterprise Server, security vulnerabilities existed in the PDF distiller of some released
versions of the BlackBerry Attachment Service. These vulnerabilities could have allowed a malicious individual to send an email
message containing a specially crafted PDF file, which when opened for viewing on a BlackBerry smartphone, could have caused
memory corruption and could have possibly led to arbitrary code execution on the computer that the BlackBerry Attachment
Service runs on.
In BlackBerry Enterprise Server version 4.1 SP6 MR5, this issue is resolved. For more information, visit www.blackberry.com/btsc
to read KB17953.
SDR 324730
In earlier versions of the BlackBerry Enterprise Server, security vulnerabilities existed in the PDF distiller of some released
versions of the BlackBerry Attachment Service. These vulnerabilities could have allowed a malicious individual to send an email
message containing a specially crafted PDF file, which when opened for viewing on a BlackBerry smartphone, could have caused
memory corruption and could have possibly led to arbitrary code execution on the computer that the BlackBerry Attachment
Service runs on.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved. For more information, visit www.blackberry.com/btsc
to read KB18327.
BlackBerry Collaboration Service
SDR 181128
In BlackBerry Enterprise Server version 4.1 SP4 or later, in certain circumstances, when using the BlackBerry® Client for use with
Microsoft® Live Office Communications Server 2005, the BlackBerry Collaboration Service might log out sessions unexpectedly.
In BlackBerry Enterprise Server version 4.1 SP6 MR4 and later, this issue is resolved.
SDR 208463
In BlackBerry Enterprise Server version 4.1 SP4 or later, when using the BlackBerry® Client for use with Microsoft® Office
Communications Server 2007, if a user added a contact while the user was in a conversation with the contact, the presence for
the contact changed to “Presence Unknown”.
In BlackBerry Enterprise Server version 4.1 SP6 MR4 and later, this issue is resolved.
SDR 301185
In BlackBerry Enterprise Server version 4.1 SP6 MR4, the BlackBerry® Client for IBM®Lotus® Sametime® could not log in to the
IBM Lotus Sametime server if the server only allows certain types of clients to log in.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
5
BlackBerry Enterprise Server for Microsoft Exchange
BlackBerry Collaboration Service
SDR 300871
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, if a user had AOL® contacts on their contact
list, the user could not log in to the BlackBerry Client for use with Microsoft Office Communications Server 2007.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
SDR 315195
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, the BlackBerry Client for IBM Lotus Sametime
could not log in to the IBM Lotus Sametime server.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
BlackBerry Configuration Database
SDR 188496
In BlackBerry Enterprise Server version 4.1, the BlackBerry Enterprise Server polled the SynchBackupRestore table on a too
frequent basis for user state changes.
In BlackBerry Enterprise Server version 4.1 SP6 and later, this issue is resolved.
SDR 189686,
189687, 197654
In BlackBerry Enterprise Server version 4.0 SP7 and later, in certain circumstances, the BlackBerry Configuration Database did
not scale as required.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, you can run a SQL script to improve indexing for the BlackBerry
Configuration Database.
1.
Back up the BlackBerry Configuration Database.
2. Extract the setup program files to a local drive on the database server.
3. Run the 4.1.6MR5.sql script in the DBScripts/SQLServer folder.
BlackBerry Dispatcher
SDR 252092
In BlackBerry Enterprise Server version 4.1 SP5 or later, in certain circumstances, when moving users from one Blackberry
Enterprise Server instance to another, where both BlackBerry Enterprise Server instances used the same BlackBerry MDS
Services, automatic user activations failed and manual user activations removed BlackBerry MDS applications.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
BlackBerry Manager
SDR 94099
In BlackBerry Enterprise Server version 4.1 SP2, if the user attempted to copy text in BlackBerry Manager, the Clipboard
functions might not have worked properly.
In BlackBerry Enterprise Server version 4.1 SP6 MR2 and later, this issue is resolved.
SDR 285545
In BlackBerry Enterprise Server version 4.1 SP6 MR4, the Japanese version of the BlackBerry Manager did not display all the text
in the property dialog boxes.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
SDR 290723
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, BlackBerry devices were unable to receive
software updates over the wireless network.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
BlackBerry MDS Connection Service
SDR 243123
In BlackBerry Enterprise Server version 4.1 SP6, in certain circumstances, the BlackBerry MDS Connection Service stopped
responding daily when transcoding image content.
In BlackBerry Enterprise Server version 4.1 SP6 MR3 and later, this issue is resolved.
SDR 288265
In BlackBerry Enterprise Server version 4.1, a security vulnerability existed that could have allowed a user to execute potentially
malicious code on the BlackBerry MDS Connection Service web site.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
SDR 284969
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, installing applications with JAD files failed in
an environment with NTLM proxy authentication.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
SDR 310999
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, users could access web sites in the BlackBerry
Browser that were blocked by a proxy server.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
BlackBerry Messaging Agent
SDR 137535
In BlackBerry Enterprise Server version 4.1 SP6, if users sent messages from BlackBerry devices or received messages on the
BlackBerry device that included ISO-2022-JP character encoding, the BlackBerry device did not encode the messages properly.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
6
Release Notes
BlackBerry Messaging Agent
SDR 171235
In BlackBerry Enterprise Server version 4.1 SP6, if your organization’s messaging environment included Microsoft Exchange
2007, users could not send vCard attachments from their BlackBerry devices.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
SDR 179314
In BlackBerry Enterprise Server version 4.1 SP6, if your organization’s messaging environment included Microsoft Exchange
2003 and 2007, users could not look up the availability of other users from the BlackBerry devices, if the other users had user
accounts on the different Microsoft Exchange version.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
SDR 184848
In BlackBerry Enterprise Server version 4.1 SP4 and later, if your users had Microsoft® Outlook® 2007 installed and configured
in cached mode, the users’ BlackBerry devices shows the received icon for all sent items.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
SDR 200411
In BlackBerry Enterprise Server version 4.1 SP6, if you configured the BlackBerry Enterprise Server to support rich content
messages, errors might occur after too many attempts to retrieve more of the message from the BlackBerry device.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
SDR 201275
In BlackBerry Enterprise Server version 4.1 SP5, the BlackBerry Messaging Agent queued an IT Policy Check only when a
BlackBerry device was cradled at BlackBerry Desktop Manager and the IT Policy was updated.
In BlackBerry Enterprise Server version 4.1 SP6 MR2 and later, this issue is resolved.
SDR 212050
In previous versions of the BlackBerry Enterprise Server, when users had contact names that included multiple French
characters, the letters between the French characters were missing when viewed on their BlackBerry devices.
In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.
SDR 217944
In BlackBerry Enterprise Server version 4.1 SP6 MR3, optimizations have been made to some MAPI calls related to wireless
calendar synchronization.
SDR 178356
In BlackBerry Enterprise Server version 4.1 SP4 and later, if the BlackBerry Enterprise Server tried to file a message into a folder
that did not exist, the BlackBerry device did not display an error message and the BlackBerry Enterprise Server did not write an
error message to the log files.
In BlackBerry Enterprise Server version 4.1 SP6 MR3 and later, this issue is resolved.
SDR 178403
In BlackBerry Enterprise Server version 4.1 SP6, if you configured the BlackBerry Enterprise Server to monitor a folder with a
folderid that exceeded the 2 byte threshold, the BlackBerry Enterprise Server synchronized the folder to the BlackBerry device,
but could not synchronize messages in the folder.
In BlackBerry Enterprise Server version 4.1 SP6 MR3 and later, this issue is resolved.
SDR 219533
In BlackBerry Enterprise Server version 4.1 SP6, a user could not turn off the redirection of sent messages from the BlackBerry
device.
In BlackBerry Enterprise Server version 4.1 SP6 MR3 and later, this issue is resolved.
SDR 188618
In BlackBerry Enterprise Server version 4.1 SP5 and later, in certain circumstances, a user could not view messages on the
BlackBerry device that the BlackBerry Enterprise Server sent.
In BlackBerry Enterprise Server version 4.1 SP6 MR3 and later, this issue is resolved.
SDR 168709
In BlackBerry Enterprise Server version 4.1 SP4, the BlackBerry device did not receive a calendar invitation over the wireless
network if the invitation did not meet the requirements of a filter on the BlackBerry Enterprise Server.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
SDR 193477
In BlackBerry Enterprise Server version 4.1 SP5 and later, if a user turned off wireless calendar synchronization on the BlackBerry
device, after the BlackBerry Enterprise Server is restarted, wireless calendar synchronization is turned on again.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
SDR 196946
In BlackBerry Enterprise Server version 4.1 SP6, the BlackBerry Enterprise Server did not remove calendar appointments that
were orphaned when a meeting series was deleted.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
SDR 266939
In BlackBerry Enterprise Server version 4.1 SP5 and later, if a BlackBerry device received a meeting invitation which included
rich text formatting, the rich text formatting converted to plaintext when the user viewed the meeting invitation in the calendar.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
SDR 285661
In BlackBerry Enterprise Server version 4.1 SP6, when a user with a Microsoft Outlook 2007 client replied to a HTML formatted
message from a BlackBerry device, breaks in the message were removed.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved.
SDR 132389
In BlackBerry Enterprise Server version 4.1 SP3 or later, in certain circumstances, when a meeting recipient proposed a time
change for a meeting, the meeting organizer was not able to view the proposal time grid in Microsoft Outlook.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
7
BlackBerry Enterprise Server for Microsoft Exchange
BlackBerry Messaging Agent
SDR 257362
In BlackBerry Enterprise Server version 4.1 SP3 or later, in certain circumstances, if a meeting request was sent to a delegate of
a user, the meeting did not appear in the user’s calendar as tentative until the delegate performed an action on the meeting
request in Microsoft Outlook.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
SDR 299431
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, when users created meetings from their
BlackBerry devices, viewing the availability of invitees took a long time.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
SDR 302994
In BlackBerry Enterprise Server version 4.1 SP6 MR3 or later, in certain circumstances, when users on a hosted BlackBerry
Enterprise Server looked up addresses on their BlackBerry devices, no matches were returned.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
SDR 343744
In BlackBerry Enterprise Server version 4.1 SP4 or later, in certain circumstances, the connection between the BlackBerry
Messaging Agent and the BlackBerry Dispatcher dropped unexpectedly.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
SDR 334316
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, incorrect MAPI settings for wireless calendar
synchronization might have caused performance issues.
In BlackBerry Enterprise Server version 4.1 SP6 MR6, this issue is resolved.
*SDR 353296
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, when a user synchronized folders over the
wireless network to a BlackBerry device, the BlackBerry device might have sent an information packet to the BlackBerry
Enterprise Server that the BlackBerry Enterprise Server processed incorrectly. This might have turned off folder redirection for
some of the user’s folders.
In BlackBerry Enterprise Server version 4.1 SP6 MR7, this issue is resolved.
BlackBerry Monitoring Service
SDR 210995
In BlackBerry Enterprise Server version 4.1 SP6, the BlackBerry Enterprise Server reported the BlackBerry 9000 series on a 3G
network as “unknown”, which caused the BlackBerry Monitoring Service to show the BlackBerry 9000 device users as “Filtered”
and did not allow monitoring or reporting.
In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.
BlackBerry Policy Service
SDR 205580
In BlackBerry Enterprise Server version 4.1 SP6, when different versions of the BlackBerry Enterprise Server were set up on the
same BlackBerry Configuration Database, service books were resent to multiple users.
In BlackBerry Enterprise Server version 4.1 SP6 MR2 and later, this issue is resolved.
SDR 184854
In BlackBerry Enterprise Server version 4.1 SP4 and later, in large environments, the BlackBerry Enterprise Server might cause
a significant load on the BlackBerry Configuration Database when completing administrative tasks.
In BlackBerry Enterprise Server version 4.1 SP6 MR5 and later, this issue is resolved. For more information, visit
www.blackberry.com/support to read KB17869.
BlackBerry Synchronization Service
SDR 186799
In BlackBerry Enterprise Server version 4.1 SP6, in certain circumstances, the activation process might stop responding when
loading the time zone service books.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
Logging
SDR 200820
In BlackBerry Enterprise Server version 4.1 SP6, in certain circumstances, the log files would grow too quickly.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
S/MIME Support Package for BlackBerry smartphones
SDR 200654
In BlackBerry Enterprise Server version 4.1 SP6, if a signed S/MIME message included an attachment, the BlackBerry device
could not verify the signature.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
SDR 201196
In BlackBerry Enterprise Server version 4.1 SP6, if a user forwarded or replied to a signed S/MIME message that included an
inline image, the inline image was not sent.
In BlackBerry Enterprise Server version 4.1 SP6 MR1 and later, this issue is resolved.
8
Release Notes
Known Issues
BlackBerry Messaging Agent
SDR 220919
In BlackBerry Enterprise Server version 4.1 SP6 or later, if your organization’s environment includes the 64-bit version of
Windows Server®, the calendar synchronization tool might not work.
9