Exploring Exchange 2010 RPC Client Access service

re: Exploring Exchange 2010 RPC Client Access service

Rashed K — Tue, 17 Aug 2010 15:13:14 GMT

Great Article, very helpful and activity, i look for it regarding of Exchange 2010 communicate with Blackberry Enterprise Server 5.0

re: Exploring Exchange 2010 RPC Client Access service

Arun — Tue, 01 Jun 2010 21:12:18 GMT

Great article Nagesh, really informative :)

re: Exploring Exchange 2010 RPC Client Access service

Office concierge — Mon, 31 May 2010 14:33:05 GMT

Great article, very useful in trying to get to grips with how the engine works.

re: Exploring Exchange 2010 RPC Client Access service

Nagesh — Thu, 27 May 2010 22:54:13 GMT

@Danny: The Directory endpoints are available for configuration via the app config file: Microsoft.Exchange.AddressBook.Service.exe.config. Look for the RpcTcpPort key. The MAPI endpoint is configurable via the registry: HKLM\System\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem\TCP/IP Port
You can also take a look at: http://technet.microsoft.com/en-us/library/ff625248.aspx ; section: Configuring Static Port Mapping for RPC-Based Services and http://technet.microsoft.com/en-us/magazine/ff626260.aspx
“Load Balancing CAS Arrays” section

@iamme: Not sure there may be a trust issue but I would need a lot more info/troubleshooting to determine the cause for this.

re: Exploring Exchange 2010 RPC Client Access service

DIck Beddoe — Wed, 26 May 2010 10:03:16 GMT

Great article, very useful in trying to get to grips with how the engine works... Thanks

re: Exploring Exchange 2010 RPC Client Access service

Paul — Tue, 25 May 2010 21:46:32 GMT

Nice article. Thanks..We're implementing 2010 and this helps.

re: Exploring Exchange 2010 RPC Client Access service

iamme — Mon, 24 May 2010 11:34:18 GMT

Why would setting the DS Server registry key to a GC in a different domain than Exchange/user domain cause Delegates to fail if the client is talking to the RPC CAS Array for NSPI? It seems like there's still some referral for clients directly to GCs in the code. Setting DS server key to a GC in same domain causes Delegates to start functioning again.

re: Exploring Exchange 2010 RPC Client Access service

Danny — Mon, 24 May 2010 07:47:05 GMT

Great Article!!!!
When implementing a Client Access Array, some people would use a third party NLBn now some of the third party NLB do not allow dynamic port required for Rpc connectivity (RPC range TCP 1024-65535) and some solutions or the only solution would be to hard code the ports for rpc and address list.

Is this something that is supported by Microsoft ???? if not is there a work around for the same ?

Thanks!!!!

re: Exploring Exchange 2010 RPC Client Access service

Frederic — Sat, 22 May 2010 12:51:02 GMT

I don't understand this part :
"This value is the endpoint that Autodiscover will give to the client, and that the client should use to connect to the user's mailbox."

Could you please explain with more details the link between the Autodiscover Service and the discovery process for those attributs (homeMDB, LegacyExchangeDN, DatabaseName)

thanks !!!

re: Exploring Exchange 2010 RPC Client Access service

joBot — Fri, 21 May 2010 19:39:00 GMT

Thanks for the interesting and informative post. I enjoyed reading it and look forward to more in the future.