June 1, 2013 fiducheah


This is to document my challenges setting up both Blackberry Enterprise and Enterprise Express 5 to integrate with Exchange 2013 (which is no picnic) as part of my migration from Exchange 2010 for two customer (~1000 seats).  I had to create a separate BES server dedicated to Exchange 2013 while leaving the existing BES to service the Exchange 2010 users.  Using Blackberry Transporter tools, we coincide the migration of BES users to that of Exchange 2010 to Exchange 2013 mailboxes. You would migrate the Exchange account first, and once that is successful you would use Blackberry Transport Tool to migrate that same user to the new BES.


The Blackberry Pre-Requisites are listed here in this KB:

Several Deviations from this Document:

Here are certain actions I have taken in excess of this KB in my struggles to get the BES to work:

  1. Create a BES5ADMIN account and left the original BESADMIN account alone. You need to grant that user Send As rights.
  2. Important: KB calls for MAPI CDO 1.2.1; however, there are multiple flavors of CDO 1.2.1, the one I applied was dated February 2013 release and I was getting the following Event 20400 in the Applications Log:

    {xxx@xxx.com} MAPIMailbox::MAPIMailbox – OpenMsgStore (0x8004011d) failed

    Only to find out there are multiple versions of 1.2.1, and after uninstalling the Feb 2013 release, rebooting and installing the latest May 2013 release of CDO 1.2.1 did this error go away for Exchange 2013 mailboxes.

  3. Disable LDAPSEARCH in registry:

  4. Set throttling policy syntax is different
    New-ThrottlingPolicy BESPolicy2013 -RCAMaxConcurrency unlimited –EWSMaxConcurrency unlimited –EWSMaxSubscriptions unlimited -CPAMaxConcurrency unlimited (The highlighted section was not included in RIM KB)

  5. Applied the BESPolicy2013 throttling policy to BES5Admin Account

  6. Disable Public Folder authentication with registry hack. Workaround 1 in this KB:

Other Important Things to Note:

  1. EWS must be working on the Exchange 2013 side otherwise you will have problems.  Browse to your 2013 Front-End servers with your IE:

    It should return information error free

  2. Check the integrity of your MAPI profile for your BES account (Blackberry Server Configuration) needs to return the GUID of your Exchange Mailbox Server
  3. Check if your MAPI profile is corrupt (use IEMSTEST in the Utility Folder)






Comments (8)

  1. Pedong

    Your MAPI profile for your BES (Blackberry Server Configuration) needs to return the GUID of your Exchange Mailbox Server

    i have my mapi profile running the Hostname of my mailbox, how should i get it to display it using GUID

    • fiducheah

      Same as Colin Mc. Make sure you don’t have any Office Group Policy forcing Outlook clients to connect to legacy Exchange.

  2. Tom Erdely

    Hello, great blog. Very helpful! Can you tell me which step comes first? Mailbox move completion or migration to new BES? I am having issues where the new BES is not “seeing” the new messaging server for the migrated users.

    • fiducheah

      You need the BES 5 with Exchange 2013 integration setup before you start moving users over to Exchange 2013. You migrate the mailbox first, after that’s done you use Blackberry Transport to move the BES user from old BES to new BES.

  3. Colin Mc

    We’ve followed your instructions to the letter but are still getting the same error

    MailboxManager::TestOpenMsgStore – OpenMsgStore (0x8004011d)

    Do you have any other ideas that we could try?

  4. Varghese Kurian

    We are in the process of migrating from Domino to Exchange for our existing BB users to work with Exchange 2013 we were advised to have a new BES 5.0.4 server installation. We are trying to follow the following link http://btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB33406&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl but we have issues while enabling NTLM authentication for IISExternalaccess but ignored and tried to install the application. We are now getting stuck in Mapi Settings and is not able to get pass this stage as it is giving some MAPI client settings error. Can somebody please advise what could be the problem.

  5. Varghese Kurian

    We have managed to install the application but now getting stuck with the activation. Can somebody please help us on how to populate HomeMTA attribute for the service account as per the below article?


    If our values are as below, please advise what will be our HomeMTA attribute?

    CN=ACME-Executive,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ACME,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ACME,DC=ho

    /o=ACME/ou=Exchange Administrative Group

Comments are closed.