This article is part 2 in a series that discusses namespace planning, load balancing principles, client connectivity, and certificate planning.
Load Balancing
Unlike previous versions of Exchan...
Updated Jul 01, 2019
Version 2.0
Blog Post
Great article Ross!
I am a little confused about how this works with coexistence with Exchange 2010. Lets say you have everything working to the Exchange 2013 CAS using whatever method you choose. Since we need to move all of the namespaces from existing 2010 CAS pools to the new 2013 CAS pool, I presume the 2013 CAS proxies all the mailbox data retrieval to one specific 2010 CAS since there is no "legacy" namespace to use for a load balanced pool of Exchange 2010 CASs.
If that is accurate, what happens from a client perspective when that single 2010 CAS or the 2010 Mailbox server holding the database (assuming they are deployed on separate servers) goes down/is taken offline? Does the 2013 server pick another 2010 CAS to use and it is 100% seamless to the end user being proxied through the 2013 CAS?
Sorry for dragging 2010 coexistence into this discussion, I just haven't seen a write up as detailed as the one in this article that explains what happens to the connections being proxied to legacy versions of Exchange.
I am a little confused about how this works with coexistence with Exchange 2010. Lets say you have everything working to the Exchange 2013 CAS using whatever method you choose. Since we need to move all of the namespaces from existing 2010 CAS pools to the new 2013 CAS pool, I presume the 2013 CAS proxies all the mailbox data retrieval to one specific 2010 CAS since there is no "legacy" namespace to use for a load balanced pool of Exchange 2010 CASs.
If that is accurate, what happens from a client perspective when that single 2010 CAS or the 2010 Mailbox server holding the database (assuming they are deployed on separate servers) goes down/is taken offline? Does the 2013 server pick another 2010 CAS to use and it is 100% seamless to the end user being proxied through the 2013 CAS?
Sorry for dragging 2010 coexistence into this discussion, I just haven't seen a write up as detailed as the one in this article that explains what happens to the connections being proxied to legacy versions of Exchange.