In a previous article, I discussed the new server role architecture in Exchange 2013. This article continues the series by discussing the Client Access server role.
While this Exchange server role sh...
Updated Nov 09, 2023
Version 3.0
Blog Post
Ross
In the article you mentioned that it’s no longer required to deploy split-brain DNS, and the fact that the Exchange 2013 RPC namespace has been moved back to the 2013 mailbox server. I guess I do not understand how I can move away from using split-brain DNS? From my understanding the Outlook 2010/2013 clients still need to look up the "internet protocol namespace" and this namespace will point to a VIP that’s load balancing a pool of 2013 CAS servers.
Lastly I understand the Outlook 20102013 clients will connect using HTTPS to the 2013 CAS server, and the RPC client access has been moved back to the 2013 mailbox role. However the outlook client needs to connect to the 2013 CAS server first, then the 2013 CAS will proxy HTTPS to the 2013 mailbox server that has the active copy of the DB. Knowing this, I do not understand how this removes the requirement of the outlook client's not having to connect to load balancer or internal firewall? If the Outlook client is required to connect to a 2013 CAS first, then wouldn’t this mean the Outlook clients still needs to leverage the load balancer for HA purposes?
Thank you