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
@Skipster -
1. Split-Brain DNS. That really should have been a "may not need to deploy". In prior releases, there was only a single Outlook Anywhere namespace, thus if you wanted your clients to use OA internally and externally, you would have to do some sort of DNS trickery to get the desired result. With the ability to have separate OA namespaces for internal and external usage in Exchange 2013, DNS trickery is no longer required for that particular namespace. However, if you want to ensure users use a single OWA namespace, for example, and control the network pathway (internal vs. external) then you would still need deal with the DNS layer. So split-brain DNS is still a viable scenario depending on your requirements.
2. I never said load balancing is not required. In fact I have stated that load balancing is still required, it is that you do not need to perform session affinity at the load balancer anymore. You still want a load balancer for connection management policies like round-robin, least connection, etc.
Ross