RSS Subscription 168 Posts and 2,769 Comments

Exchange 2010 SP1 and Blackberry Enterprise Server (BES)

Many will be upgrading to Exchange 2010 SP1 soon.  Many of you also have Blackberry Enterprise Server.  RIM has provided a pre-installation guide for Exchange 2010 here.  I wanted to touch on one of these pre-installation steps.  This is where we increase the maximum number of connections to the Address Book service.  The specific guide for this step is located here.  As you can see, you have to go into the following file “” and set MaxSessionsPerUser to 100000.

Note: Blackberry now has full support for Exchange 2010 SP1 as of 10/12/2010.  RIM retroactively modified their September 29th document to have full support when the same September 29th document previously only had Exchange 2010 SP1 listed with limited support. Please see the following document for support guidance which includes versioning information as well as a support KB article on supporting BES with Exchange 2010 SP1:

In Exchange 2010 SP1, MaxSessionsPerUser does not exist anymore.  You can take a look at an Exchange 2010 SP1 “” file below:

<?xml version="1.0" encoding="utf-8" ?>
        <gcServer enabled="true" />
        <generatePublisherEvidence enabled="false"/>
        <add key="NspiEndpointEnabled" value="true" />
        <add key="RfrEndpointEnabled" value="true" />
       <!-- Set port to an empty string to disable ncacn_ip_tcp. -->
        <!-- Set the port to 0 to allow the server to assign a port number dynamically. -->
        <add key="RpcTcpPort" value="0" />
        <!-- Set port to an empty string to disable ncacn_http for the specific interface -->
        <!-- Standard port assignments: Nspi=6004, Rfr=6002 -->
        <add key="NspiHttpPort" value="6004" />
        <add key="RfrHttpPort" value="6002" />
        <!-- Enables and disables the logging for the address book service. -->
        <add key="ProtocolLoggingEnabled" value="true" />
        <!-- Specifies the folder in which log files will be generated. -->
        <add key="LogFilePath" value="D:\Program Files\Microsoft\Exchange Server\V14\Logging\AddressBook Service\" />
        <!-- Specifies the max size that a single log file can grow to before a new one is generated. -->
        <add key="PerFileMaxSize" value="10MB" />
        <!-- Specifies the max size that the entire directory of logs can grow to before the oldest log is deleted. -->
        <add key="MaxDirectorySize" value="1GB" />
        <!-- Specifies length of time in hours log files will be retained before being deleted. -->
        <add key="MaxRetentionPeriod" value="720" />
        <!-- Specifies if we need to switch log file each hour. -->
        <add key="ApplyHourPrecision" value="true" />

So the big question here is, what do we do?  What do we need to make sure of prior to upgrading to Exchange 2010 SP1 to ensure the BESAdmin account does not have issues connecting to the Address Book Service?  Well, the reason why there is no more MaxSessionsPerUser is that the throttling mechanism was moved to the Throttling Policies and is shared with the RPC Client Access Service which uses the RCA* parameters in the Throttling Policies.

One of the prerequisites steps in the BES Documentation (even for RTM)  is to create a Throttling Policy for the BES Admin Account.  You can see that step here.  Because the Address Book throttling has been moved to the Throttling Policy using the RCA* parameters instead of the “” we will want to take a look at the throttling policy we created for the BESAdmin account and make sure the RCA* parameters are set to $null.

Run the following command on Exchange 2010 to check the throttling policy:

Get-ThrottlingPolicy BESPolicy

We will see results as such:

As we can see, the RCA* parameters are set to $null which means we will be safe upgrading to Exchange 2010 SP1.  If these parameters are not set to $null, set them to $null.  This can be done by running the following command:

Set-ThrottlingPolicy BESPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null

If you are doing a greenfield deployment of BES and need to create a new Throttling Policy with all of the options and then assign the BES Mailbox (assuming the mailbox is BESAdmin), run the following commands:

  1. New-ThrottlingPolicy BESPolicy
  2. Set-ThrottlingPolicy BESPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null
  3. Set-Mailbox “BESAdmin” -ThrottlingPolicy BESPolicy.

52 Responses to “Exchange 2010 SP1 and Blackberry Enterprise Server (BES)”

  1. on 25 Aug 2010 at 11:33 amMatt

    A timely post! I was just looking for information on why this change was required. I wasn’t crazy about bumping up that limit for all users, but I’m glad to see that in SP1 it won’t be an issue anymore. Thanks!

  2. on 26 Aug 2010 at 10:33 am@kkuphal

    Invaluable info for BES admins upgrading to Exchange 2010 SP1. We had to set these values on the Default policy as the BESPolicy would never apply in our environment.

  3. on 29 Aug 2010 at 1:17 pmMarco Marzola

    Great info ! Is this valid for bes express too ??

  4. on 29 Aug 2010 at 3:35 pmElan Shudnow

    I would assume so but don't know. Haven't dealt with bes express or read the documentation on how it integrates into Exchange.

  5. on 13 Dec 2010 at 12:50 pmRobert Edgel

    Worked for me on BES Express. Thanks Elan!

  6. on 30 Aug 2010 at 2:11 pmDavid McCue

    We also had to make a change to the default throttlingpolicy when we moved our BESadmin account from the EX2003 server to the EX2010 server. We received this error:OpenMsgStore failed (8004011d) error in Exchange 2010 and resolved it per this link.

    The BESPolicy seems to be useless.

  7. on 31 Aug 2010 at 3:35 pmL.B.

    Thanks for posting this – saved our bacon as well when we upgraded to Exchange 2010 SP1!!

    Get-ThrottlingPolicy | Set-ThrottlingPolicy -RCAPercentTimeInCAS:$null -RCAPercentTimeInMailboxRPC:$null -RCAMaxConcurrency:$null -RCAPercentTimeInAD:$null

  8. on 01 Sep 2010 at 6:24 pmElan Shudnow

    I would not recommend running the command L.B. provided by the way. If you have multiple Throttling Policies in the organization, this will configure all of them with RCA set to $null which may not be what you want.

  9. on 01 Sep 2010 at 5:53 pm@FirmBizzle

    We're in the middle of an upgrade to EX2010 and would love to install SP1. We're just worried about BES compatibility. Is anyone successfully running BES 5.0.1 MR1 and Exchange 2010 SP1?

  10. on 01 Sep 2010 at 6:23 pmElan Shudnow

    I was in the Technology Adoption Program for Exchange 2010 SP1 and there were a lot of people running BES with Exchange 2010 SP1 as long as you followed the above. Just keep in mind, RIM doesn't officially support this though (not supporting != not working) so you may still want to hold off for official support. I would also suggest upgrading to 5.0.2 before upgrading to SP1.

  11. on 15 Sep 2010 at 9:54 amKarl

    We are having troubles with our BES working w/ E2K10 SP1 (and have followed all of the above as well as troubleshooting ideas from other posts) and cannot get support from RIM.

  12. on 11 Sep 2010 at 3:41 pmSteven Rodriguez

    I am running BES 5.0.2 (SP2) and foolishly upgraded to Exchange 2010 SP1 before reading this, and now the RpcClientAccess.Service.Exe keeps crashing and throwing exceptions in the event viewer. I tried nulling all the values mentioned above, but I am still getting the following exceptions logged in the System and Application logs. Are these entries supposed to stay nulled? Can anyone offer a solution?

    System Log
    The Microsoft Exchange RPC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

    Application Log
    Application popup: Visual Studio Just-In-Time Debugger : An unhandled exception ('CrashNowException') occurred in Microsoft.Exchange.RpcClientAccess.Service.exe [11072].

    Watson Report
    <watson-report event-type="E12" issue-type="4" timestamp="2010-09-11 20:34:17Z" reporting-enabled="0" xml:space="preserve">
    <details>InvalidOperationException (Nullable object must have a value.) in Microsoft.Exchange.RpcClientAccess.Handler.RopHandler.Logon</details>

  13. on 12 Sep 2010 at 7:05 amElan Shudnow

    Yes, it is supposed to stay $null. Not sure why you're getting that error. I would open up a case with Microsoft. And for the record, 5.0.2 is not SP2. It's MR2. SP1 for BES 5.0 isn't even out yet and therefore, either is SP2.

  14. on 15 Sep 2010 at 8:57 amNeo3000

    RIM version notation is strange:
    5.0.2 = 5.0 SP2 != 5.0 MR2

    Proof: There is a 5.0.2 MR1 available as of today

  15. on 15 Sep 2010 at 9:59 amElan Shudnow

    Thanks for the correction.

  16. on 30 Nov 2010 at 6:13 amRIM BES Tech Support

    For the record
    BES 5.0.2 is SP 2

  17. on 12 Sep 2010 at 7:41 pmTrini

    I am 5.0.0 MR3 and running MSExchange 2010 SP1. Bad move on my part cause now I have to restart the BES every 3.5 hours in order for the data to flow to the handheld. Sucks! Does anyone have a solution? Null is not working for me.

  18. on 12 Sep 2010 at 7:55 pmSteven Rodriguez

    See above, my situation is similar, but the RPCClientAccess.Service.exe automatically restarts every 5 seconds when it crashes, so, the BES logs the mail store access failures, but when it restarts, its all back to normal, I dont have to restart me BES. I don't have a solution yet.

  19. on 13 Sep 2010 at 3:03 pmLee Silk

    We installed SP1 on our Exchange 2010 server over the weekend and are running BES MR2, since SP1 the calendars on our handhelds aren't synchronising unless we manually re-sync on the server which works for a few hours before it drops out again. Any one else having this same issue?

  20. on 13 Sep 2010 at 4:35 pmMichael Bowers

    Elan, how many production environments do you know of running Exchange 2010 SP 1 with BES 5.0.2?

  21. on 14 Sep 2010 at 3:18 pmElan Shudnow

    None yet as RIM has no official support yet. I've been recommending to all my clients to wait for RIM's official support.

    As for my post, this is what people were doing in the TAP with BES due to MaxSessionsPerUser being removed. My article is by no means saying, "This is all you have to do and you don't have to worry about RIM's support." All it's saying is, this is what you have to do for MaxSessionsPerUser.

  22. on 14 Sep 2010 at 3:06 pmDean Colpitts

    Lee Silk – I can confirm this issue as well in two other production environments with Exchange 2010 SP1 and BES Express 5.0.2.

  23. on 16 Sep 2010 at 4:27 amDens

    I encountered this issue yesterday.
    Exchange 2010 RTM and Blackberry Server 5.02 is present.

    Issue :
    Unable to send receive emails using both Outlook and OWA. (OWA webpage trying to open but doesn’t open too)
    Outlook shows connected in status, but while sending email it just sits in the Outbox. Doesn’t receive any emails too.

    CAS and hub role is on same server…..On CAS server i can see event logs generated by Blackberry user and service account crashing the Microsoft.Exchange.RpcClientAccess.Service.exe
    Reboot of CAS server didn’t fix it. The sessions again got exhausted looking at event viewer.

    The max sessions got exhausted due to getting filled up by Blackberry account and couple of BB user accounts.

    Came across your article and Bingo it worked. The MaxSessionsPerUser on was earlier 50 . I changed to 100000 . All looks good now.

    Your Post proved very useful . Thanks !

  24. on 16 Sep 2010 at 9:54 amGary Cutri

    Re: calendar entries disappear

  25. on 25 Oct 2010 at 2:05 pmWill

    I have Exchange 2010 SP1 RU1 and BES 5.0 MR1. I am about to start moving mailboxes from ex 2003. Is this supported now? Any update?

  26. on 25 Oct 2010 at 3:52 pmElan Shudnow

    Read the 2nd paragraph.

  27. on 25 Oct 2010 at 5:42 pmWill

    Should we set below all throttling policy parameters to Null while working wirh Ex2010 SP1 ?

    Set-ThrottlingPolicy BESPolicy
    -RCAMaxConcurrency $null
    -RCAPercentTimeInAD $null
    -RCAPercentTimeInCAS $null
    -RCAPercentTimeInMailboxRPC $null
    -EWSMaxConcurrency $null
    -EWSPercentTimeInAD $null
    -EWSPercentTimeInCAS $null
    -EWSPercentTimeInMailboxRPC $null
    -EWSMaxSubscriptions $null
    -EWSFastSearchTimeoutInSeconds $null
    -EWSFindCountLimit $null

    Any directions will be appreciated.

  28. on 25 Oct 2010 at 7:10 pmElan Shudnow

    I typically do.

  29. on 26 Oct 2010 at 10:57 pmWill

    Thanks for your suggesion. I have Exchange 2010 SP1 RU1 and BES 5.0.1 MR1. I am planing to update CDO to 1.2.1 6.5.8190.0

    So lets say if we do all the necessory permission related cahnges on BESadmin account, move BESadmin account to exchange2010 SP1, create new throttling policy and follow all the BES guideline for migration. But for some reason, if this plan doesnt work after BESadmin account migration to ex2010 server and if we see some unexpected issues. What do you think should be the fall back plan?

    Should we just move BES admin back to exchange 2003 server? Do I need to delete newly created throttling policy? In short, what neccessory changes required, in order to revert back config and move changes back to normal as it was.

    Urgent help needed. Thanks in advance.

  30. on 31 Oct 2010 at 4:22 pmJan

    Hey Guys,

    i'm just setting up an 2k8r2 x64 enviroment a few days ago. one ad controller, one exchange, one bes. using 2010 sp1 with ru1 and all the latest updates for the os. installed also outlook 2010 with all patches as x64 version importing pst data. installed also bes express 5.0.2 on the single server. followed all faq's and some tricky guides for resolving some issues with bes 5.0.2, everything working just fine, but, 2 issues: the first, IEMSTest is not able to do the command "EWS calendar find request… failed", not a nice present, but also, not for all users. i've figured out this as an issue with the exchange default address policys and autorisized domains, but not sure, what's the main error. iis is logging an http 500 for my besadmin, but with no other information. even, calendar syncro works fine, after manually enabling ews. for my scenario, exchange required an uc ssl certificate for fine working with autodiscover, wich is a musst have. the other issue is described in KB21309 with a solution, but it's 2010 SP1 with RU1, not RTM ;-)

    A not important issue is described in DT742344, also not figured out yet.

    in addition, yesterday i've applied the pdf security fix for bes and also bes x 5.0.2 mr1, but, the issues are still existing.

    Does anyone have the same issues? The attachment issue sucks ;-)

    CDO 8190 not tested at this time. Next days, i will try and will keep you posted.

    Finally, the rest of bes works great and fast.

    Also i have opened a ticket at rim, well'see, just now i'm waiting for response.

    greetings to all,


  31. on 31 Oct 2010 at 4:56 pmMJanosch

    Ok, great nice things happend ;-)

    The post from Will (many many thanks to you for the note about M$ CDO Release) was the solution for the attachment issue and all my error messages in MAGT log and the Error Messages described in DT742344. Everything now works great and very very fine, also too calendar attachments and so on. A very fine solution now in my DELL ESX ;-)

    Not fixed yet is the IEMSTest EWS calendar request issue, but, Calendar Syncro and FreeBusy Review works also fine, so for me i will monitorong this in case of updates coming in the next time and will keep you posted.

    Finally, BES 5.0.2 works great with Ex2010 SP1 and RU1, a very good recommed scenario. If you have questions, post it here, i've subscribed the threads.



  32. on 05 May 2011 at 12:06 pmgarin

    Hi Will, Did you manage to get a solution to this. i am looking to do the upgrade but would also like to have an escape plan. your experience would help if you managed to test this.


  33. […] of connections to the Address Book service." Follow the directions here to complete this step. Exchange 2010 SP1 and Blackberry Enterprise Server (BES) | Elan Shudnow's Blog Remember, take it one step at a time and TEST TEST […]

  34. on 04 Feb 2011 at 8:25 amM.Preissner

    Hello Mr. Elan
    May I Ask You for a clue?

    Scenario We are running BB-Enterprise 5.0.2 MR1 with CDO 6.5.8190 on W2008R2 ,since the Update of the CDO the server gaind a speedup that was unbelieveble.
    But we still have a strange problem that the latest users who have ben BB-Enabled cannot forward Emails with attachments (Signatures with jpgs for example)
    0x19C4} {} MAPIMailbox::RIMAttachtoMAPIAttach – OpenProperty (0x80004005) failed
    [30147] (02/04 14:54:37.206):{0x19C4} {} MAPIMailbox::Send(ppMAPIMessage) Cleanup – HrGetOneProp (0x8004010f) failed
    0x19C4} {} Send() failed: ERR_FAIL, RefId=1103922550, Tag=528762
    [40277] (02/04 14:54:37.224):{0x19C4} {} Sending message error to device for message 1103922550

    any advise?

    Best Reguards Preissner Manfred

  35. […] Re: Exchange 2010 Address book setting for BESX 5.0.2 oops, didnt google long enough Exchange 2010 SP1 and Blackberry Enterprise Server (BES) | Elan Shudnowxxx039;s Blog […]

  36. on 11 Apr 2011 at 2:48 pmFire

    Thanks a lot for your post.

  37. on 13 Apr 2011 at 8:38 pmGary Cutri

    Updated BESPolicy for Exchange 2010 SP1 (this also corrects the "MaxSessionsPerUser" requirement):

    New-ThrottlingPolicy BESPolicy -CPAMaxConcurrency $NULL -CPAPercentTimeInCAS $NULL -CPAPercentTimeInMailboxRPC $NULL -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null

    Set-Mailbox "BESAdmin" -ThrottlingPolicy BESPolicy

    Further Info: To resolve Exchange 2010 SP1 latency issues please ensure BES 5.0.2 is running MR4 (5.0.3 MR is recommended) and update your BES MAPICCO Client to version 6.5.8211.0 or higher.

  38. on 01 Jun 2011 at 11:36 pm@idermunkh

    Hi ,Elan.

    Recently we upgraded our Exchange Server 2010 (with BES express) by SP1. But we have problem with outlook register. Is it works after upgrade?

  39. on 06 Jun 2011 at 11:43 amDavid

    Great Post, thanks for the info!!!

  40. […] In Exchange 2010 SP1, MaxSessionsPerUser does not exist anymore.  You can take a look at an Exchange 2010 SP1 “” file below: ?View Code XML […]

  41. on 25 Oct 2011 at 2:13 amlucky

    Hi Elan,
    I am running BES 5.0 SP3 with exchange 2010 — I tried "get-throttlingpolicy bespolicy " and it said BESPolicy does not exist. I then ran "get-throttlingpolicy" and I got output the same as yours and all the values you mention in your post are set to null. My throttling policy is called Defaultthrottlingpolicy_8dac7bda-9e5b-4b53-8de1-cad85fd2554f.
    My BES is working well and I have no problems with services etc…. Do you think I can safetly go ahead and install exchange 2010 SP1

  42. on 02 Nov 2011 at 7:54 pmElan Shudnow

    You should create the Throttling Policy and assign it to BES as per instructions on my site as well as RIM's official instructions.

  43. on 11 Nov 2011 at 2:56 pmboma23

    thank you – doing my ever first BES install on a SBS 2011 recently migrated, this is also my first time with Exchange 2010. They don't make i easy, given that the most recnt install guide on BB site I can find still has outdated info…

  44. on 18 Nov 2011 at 8:40 pmMark

    Hi Elan,
    I have BES 5.0 latest service pack in a 2003 sp2 environment. I'm getting ready to introduce exchange 2010 to the mix. Is it still the case that I will have problems unless I do the additional things you list here before applying SP1, even though they now officially support SP1 with their latest service packs? I wasn't clear if I would just be screwed with no recourse or if I could also apply these settings after the migration. In my case the 2010 server would have no users on it prior to following the blackberry migration plan. I just really liked the idea of applying all the latest updates to Exchange 2010 before configuring it and moving any users, including besadmin, over to it.

  45. on 18 Nov 2011 at 8:55 pmMark

    Sorry, I just noticed the Greenfield section after rereading it. So if I understand it correctly, the section before the Greenfield install is about fixing an already existing throttling policy created pre sp1. Since my server will be brand new I can create the throttling policy after installing SP1 using the shell cmdlet in the Greenfield section?

  46. on 23 Nov 2011 at 10:51 amElan Shudnow

    Mark, the idea here is you will end up moving the BESAdmin Mailbox to Exchange 2010. And therefore, you will want to make sure that a custom throttling policy is created so BES is not throttled. Check out the following article:

  47. on 29 Dec 2011 at 12:13 am@tegbains

    Thank you for the post. I wish RIM would update their BESX guides…

  48. […] Rob confirmed that Calendaring was working so I have not further tried to resolve this point (I do suggest that it be looked into and this article may assist ) […]

  49. on 14 Mar 2012 at 9:27 pmSerg

    Hey thanks for the Tip I was looking all over wondering why the option to increase the connections was not in my file you would think the blackberry shmucks would update this manual 1 year after SP1 thanks agian

  50. on 14 Mar 2012 at 9:37 pmElan Shudnow

    It is in the BES documentation. It has been for a long time.

  51. on 02 May 2013 at 4:43 pmPayday Loans

    I’m pretty pleased to discover this great site. I wanted to thank you for ones time just for this fantastic read!! I definitely appreciated every bit of it and i also have you book marked to check out new information on your blog.

  52. on 18 May 2013 at 4:58 amFern

    Hi there, I read your blogs regularly. Your writing style is awesome, keep it up!

Trackback this post | Feed on Comments to this post

Leave a Reply