Blog Post

Exchange Team Blog
1 MIN READ

BlackBerry Enterprise Server fully supported on Exchange 2010

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Dec 10, 2009

I'd like to share with everyone some good news today— BlackBerry® Enterprise Server (BES) is now fully supported on Microsoft® Exchange Server 2010 and BlackBerry® Technical Support Services are readily available.

This is the earliest customers have been able to deploy BlackBerry smartphones with a new Exchange release - ever. Customers who rely on BES as an important part of their messaging and collaboration infrastructure have told us that more rapid support for RIM's solution is critical to them. So we partnered with RIM earlier in the development cycle to ensure organizations moving to the new release experience no user downtime.

In order to enable full support, three updates are required:

All three of these updates are available to customers of Exchange Server 2010 and BlackBerry Enterprise Server v.5.0 with Service Pack 1 at no cost. BlackBerry Enterprise Server v5.0 Service Pack 1 and Maintenance Release 1 can be found here: http://www.blackberry.com/support/downloads

Additional information on the solution requirements, preparing the BlackBerry environment for Microsoft Exchange Server2010, can be found on the BlackBerry site here.

Today's roll up also includes other minor updates to areas including calendaring, OWA, and transport. You can read more about Exchange Server 2010 RU1 here.

- Paul Bowden, Exchange Release Manager

Updated Jul 01, 2019
Version 2.0

37 Comments

  • pingback from:
    http://chrislehr.com/2009/12/exchange-2010-and-blackberry-enterprise.htm

    Can't WAIT to get this deployed now.
  • A quick comment on verifying the version. Check the version of CDO.DLL on the system where you have installed the download to validate that it is 6.5.8147.0.
  • NOTE to everyone trying to get the MAPI/CDO download:



    The above URL is correct, but it currently still points to the older version of the MAPI download (6.5.8131.0). There is some replication that still needs to occur on the backend. Please verify the version before you download to prevent possible issues. We expect all of this to be sorted by tomorrow.

  • The link you posted for MAPI v.6.5.8147 goes to v 6.5.8131.

    Where can we get the new version?
  • UM: yeah - I think I had 2007 on my mind.
  • In Exchange 2010 (aka E14) MAPI-based clients have to go through the RPC Client layer (aka MAPI on the Middle Tier or MoMT). They don't communicate directly to the back-end mailbox server (UM doesn't do this either).
  • I can't seem to find the answer to the most important question (at least I think so).

    Does BES do direct MAPI to the mailbox role?  The idea of 14 means that it shouldn't, but, I'm wondering if BES will be an exception.  Sort of like UM can talk directly to the mailbox role.

    I was hoping that they wouldn't continue to use MAPI, it seems that EWS would be a better method.