This article is part 3 in a series that discusses namespace planning, load balancing principles, client connectivity, and certificate planning.
Over the last several months, we have routinely fie...
Updated Jul 01, 2019
Version 2.0
Blog Post
As always very informative
especially this part which I was wondering about:
"But how does CAS2013 choose which legacy Client Access server to proxy the connection?"
also small question if you don't mind about this sentence regarding oab:
"1.For the Red User, Autodiscover will return the mail.contoso.com namespace for the Offline Address Book URL. CAS2013 will then proxy the request to any Client Access server within the local site that is a web distribution point for the Offline Address Book in question. "
I thought the "web distribution" option only decides which server the client is going to get back from autodiscovery(ex 2013) which server actually has the files in the mailbox server where its being generated on(where that arbitration mailbox is) no?
Thanks again for another informative post
especially this part which I was wondering about:
"But how does CAS2013 choose which legacy Client Access server to proxy the connection?"
also small question if you don't mind about this sentence regarding oab:
"1.For the Red User, Autodiscover will return the mail.contoso.com namespace for the Offline Address Book URL. CAS2013 will then proxy the request to any Client Access server within the local site that is a web distribution point for the Offline Address Book in question. "
I thought the "web distribution" option only decides which server the client is going to get back from autodiscovery(ex 2013) which server actually has the files in the mailbox server where its being generated on(where that arbitration mailbox is) no?
Thanks again for another informative post