The purpose of this post is to have access to Microsoft best practice, preferred architecture and published guidelines specific for Exchange Server 2013. The three presentations and other referenced articles share a mutual theme. One of them answering a common question of whether to deploy multi-role servers or to split the roles.
- Exchange 2013 ABC´s: Architecture, Best Practices and Client Access (Michael Van Horenbeeck)
- Exchange Server 2013 Architecture (Ross Smith IV at MEC 2014)
- Re: Server design … “Do not deploy dedicated server roles. It’s unnecessary.” (presentation time 1:11 / slide 38)
- Re: Disk speed … “7200 RPM disks are what we want you to deploy on. There is no need to deploy on any other type of disks. Take advantage of the capacity that we have built into the system.”
- Ready, set, deploy: Exchange Server 2013 (Brian Day at MEC 2014)
- Released: Exchange 2013 Server Role Requirements Calculator
- “Like with Exchange 2010, the recommendation in Exchange 2013 is to deploy multi-role servers. There are very few reasons you would need to deploy dedicated Client Access servers (CAS).”
- Robert’s Rules of Exchange: Multi-Role Servers
- “There are very few cases where the multi-role servers are not the appropriate choice”
- Exchange Server 2013 site resiliency- DAG design and load balancer placement
- “Note: You MUST have a multirole server on the DR site to have proper mail flow during DR situations.”
Remember, keep your deployments simple; as that is the message reiterated by the Exchange Server team and Microsoft.