Download Print this page
Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - RELEASE NOTES Release Note
Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - RELEASE NOTES Release Note

Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - RELEASE NOTES Release Note

For microsoft exchange
Hide thumbs Also See for ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - RELEASE NOTES:

Advertisement

Quick Links

BlackBerry Enterprise Server for Microsoft
Exchange
Version 4.1 Service Pack 6
Release Notes

Advertisement

loading
Need help?

Need help?

Do you have a question about the ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - RELEASE NOTES and is the answer not in the manual?

Questions and answers

Summary of Contents for Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - RELEASE NOTES

  • Page 1 BlackBerry Enterprise Server for Microsoft Exchange Version 4.1 Service Pack 6 Release Notes...
  • Page 2 ©2008 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 as trademarks in the U.S., Canada, and countries around the world.
  • Page 3 OF ANY RIM PRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION. Certain features outlined in this documentation require a minimum version of BlackBerry Enterprise Server Software, BlackBerry Desktop Software, and/or BlackBerry Device Software and may require additional development or Third Party Products and Services for access to corporate applications.
  • Page 4: Related Resources

    Product information Research In Motion (RIM) plans to discontinue support for the “You were BCC’d” portion of messages as of BlackBerry Enterprise Server version 5.0 (SDR 79671). RIM certifies that the BlackBerry Enterprise Server operates on VMware® ESX Server version 3.0.1. As with any deployment of the BlackBerry Enterprise Server, consider taking baseline measurements of performance after you install the BlackBerry Enterprise Server, and then add users in stages to the server.
  • Page 5 GroupWise® Messenger is now named the BlackBerry® Client for Novell® GroupWise® Messenger. Connecting the BlackBerry Collaboration Users can use the BlackBerry Client for IBM Lotus Sametime to send files to the contacts in their Service to a remote BlackBerry Attachment contact lists.
  • Page 6: Fixed Issues

    SDR 170850 In BlackBerry Enterprise Server version 4.1 SP4 and later, if you applied the SQL script for Daylight Saving Time (DST) to your BlackBerry Domain, when a timezone change occurred only one of the BlackBerry Enterprise Servers in your BlackBerry Domain might have processed it.
  • Page 7 In previous versions of the collaboration client, when a user used the collaboration client to open a conversation with a contact, then invited more contacts to join the conversation, an invitation was sent to all contacts. If a contact on a different BlackBerry Enterprise Server refused the invitation, the user was unable to invite the contact to join the conversation again.
  • Page 8 In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved. SDR 159004 In BlackBerry Enterprise Server version 4.1 SP4 and later, if you tried to search for a user using the BlackBerry Manager, the user information was not always displayed correctly in the preview window in the BlackBerry Manager.
  • Page 9 SDR 145126 In BlackBerry Enterprise Server version 4.1 SP3 and later, if a user browsed to a web page with HTML errors, certain contents of the web page might not have been displayed on the user’s BlackBerry device. The user did not receive an error message indicating that some of the contents of the web page were not displayed.
  • Page 10 SDR 167837 In BlackBerry Enterprise Server version 4.1 SP4 and later, if you moved a user to a different BlackBerry Enterprise Server, the BlackBerry Enterprise Server might have sent an incorrect SRP ID to the user’s BlackBerry device with the BlackBerry MDS Integration Service service book.
  • Page 11 SDR 158481 In BlackBerry Enterprise Server version 4.1 SP4 and later, if a user deleted a calendar event while out of a wireless coverage area and the send queue was full, the deleted calendar event might not have synchronized correctly to the BlackBerry device when the user entered a wireless coverage area.
  • Page 12: Known Issues

    To field, and “FW:” is not included in the To field. SDR 171688 When the BlackBerry Enterprise Server starts, if a user account fails to start due to MAPI errors, a large number of worker threads might be created.
  • Page 13 In certain circumstances, when a user sends a message in a conversation, the message might be displayed three times instead of once in the conversation on the receiver’s client. SDR 182031 In rare circumstances, if a user adds a contact to the contact list using the BlackBerry device, the contact might not receive an Add Request notification. SDR 181128 In certain circumstances, an "An existing connection was forcibly closed by the remote host"...
  • Page 14 SDR 178403 If you assign a folder ID to a message folder that is monitored by the BlackBerry Enterprise Server, the folder is synchronized to the user’s BlackBerry device, but if the user files messages in this folder on the BlackBerry device, the messages are not synchronized to the email application on the user’s computer.
  • Page 15 SDR 178356 If the BlackBerry Enterprise Server tries to file a message to a folder ID that does not exist, an error condition is not returned to the user’s BlackBerry device, and no information about the error is written to the BlackBerry Messaging Agent log file.

This manual is also suitable for:

Enterprise server 4.1