How are Outlook Anywhere clients Proxied from Client Access Server to Mailbox (in same site)?

Where is the official Microsoft documentation on this?

I have read: https://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx

but this seems to only cover OWA, ActiveSync, IMAP & POP.  It does mention that clients (probably Outlook) use the CAS server (role) to obtain availability and autodiscover information... BUT ... is that all?

Thank you.
LVL 9
K BAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gheistCommented:
RPC over HTTP is used by OWA and Outlook Anywhere.
K BAuthor Commented:
Would you agree that OWA encapsulates at the server and Outlook Anywhere is sending RPC calls encapsulated by HTTP directly from the client.
I am speaking of the client traffic to the server.
K BAuthor Commented:
oh wait this question is asking about how Outlook (making a request of a CAS server) is proxied to its Mailbox.  More specifically, when the CAS server lives in a subnet that is the SAME as the mailbox server.

Is it CAS to CAS proxying or a direct connection from CAS to MBX server?  Any supporting documentation?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

gheistCommented:
Entourage 2008 web services edition was first to use this protocol - i.e browsing OWA site under the hood.
K BAuthor Commented:
that's cool but any thoughts on my last post/the question?
Guy LidbetterCommented:
hi K B,

To be specififc, OA uses RPC\HTTP. The RPC endpoint is the CAS box which "Proxies" your connection to your mailbox, also on RPC\HTTP.

So, from your Outlook client, there is an RPC\HTTP connection to the CAS box on port 80 (non SSL) or 443 (SSL), then there is a connection from the CAS box to the Mailbox Server using the same RPC\HTTP protocol but on port 6001.
In simple terms the CAS role acts like a gate way to forward the traffic to the server where the mailbox is located. If the mailbox moves servers (failover, migration etc), your rpc connection to the CAS remains and it re-establishes its RPC connection to the new Mailbox Server. Which prevents Client (Outlook) disconnections.

How your client finds the CAS server is another tale... but to correct you, it doesn't use the CAS to find Autodiscover, it's the other way around.
The Autodiscover DNS and SRV records or SCP provide a URL where the CAS box can be located.

Regards

Guy

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.