Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Preferred Client Access throttling settings for outlook anywhere

Answered Preferred Client Access throttling settings for outlook anywhere

  • Friday, May 25, 2012 3:48 PM
     
     
    Sign In to Vote
    0

    Hi,

    We wish to move all our company's outlook clients (1700) from using a direct RPC connection to the CAS server to a RPC over HTTPS (Outlook Anywhere).

    What would be the preferable thottling settings that might need to be changed in order for a preference to connect via outlook anywhere? They are currently using the default throttling policy.

    Looking at user posts and blogs, which component refers to outlook anywhere? OWA, RPC?

    Acronym Component Description Note
    Anonymous N/A Anonymous connections to user’s calendar New in SP1
    EAS Exchange ActiveSync ActiveSync connections to  Exchange Server
    EWS Exchange Web Services Exchange Web Services connections to Exchange Server including Unified Messaging users
    IMAP IMAP4 IMAP4 connections to Exchange Server
    OWA Outlook WebApp Outlook WebApp connections to Exchange Server
    POP POP3 POP3 connections to Exchange Server
    RCA RPC Client Access RPC Client Access Server connections to Exchange Server
    CPA Cross Premise Access Cross premise connections to Exchange

    Many thanks to anyone who might know which component to change and the increase to the limits it would need for the CAS server to function correctly.

    (to note when we change the outlook client for users to start connecting via outlook anywhere, they start complaing of issues, similar to this MSDN blog post)

    http://blogs.msdn.com/b/pepeedu/archive/2010/01/13/exchange-2010-client-access-throttling.aspx

    Alex

     

All Replies

  • Friday, May 25, 2012 4:02 PM
     
     Answered
    Sign In to Vote
    0
    Outlook Anywhere is based on the Windows Server RPC-Over-HTTP-Proxy feature, and, as I understand it, is handled outside of Exchange.  I believe that these connections look like a regular MAPI connection to Exchange because the unencapsulation of the traffic is handled by Windows before the packets reach Exchange.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

     
  • Monday, May 28, 2012 8:11 AM
     
     
    Sign In to Vote
    0

    Ed,

    Many thanks for your response,

    If I understand what you have answered back, I have to increase the RCA component threshold to satisfy the client demand from users connecting via Outloook anywhere.  Can you confirm?

    Thanks

    Alex

     
  • Monday, May 28, 2012 12:28 PM
     
     
    Sign In to Vote
    0
    That isn't what I said.  I don't know the answer to your follow-up question.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

     
  • Tuesday, May 29, 2012 6:13 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hello,

    Here is a userful blog, and you can refer to it.

    http://blogs.msdn.com/b/stephen_griffin/archive/2010/01/07/throttling-exchange-2010.aspx

    Best Regards,

    Lisa


     
  • Tuesday, May 29, 2012 2:41 PM
     
     
    Sign In to Vote
    0

    Thanks fopr your help Lisa,

    I'm going to give it a try and increase the limit and see if it makes a difference...

    It's quite interesting to determine that by just transfering outlook connections from TCP/IP to HTTPS, that this throttling limit might come into play.

    Perhaps the two are not related, however it is quite puzzling to see the exact type of symptoms the throttling limit can cause happen with OutlookAnywhere.