![]() Simplified deployment with the Mailbox server running Client Access services and Edge Transport server roles. Using minimal server roles, Exchange 20 delivers: ![]() Compare this to Exchange 2010, where Client Access, Mailbox, Hub Transport, and Unified Messages ran on separate servers. When this is combined with the availability of third-party load-balancing solutions (both hardware and software), there are multiple options for implementing load balancing in your Exchange organization.Įxchange architecture changes introduced in Exchange 2013 brought about the Mailbox server and Client Access server roles. ![]() Load balancing in Exchange 2016 and later build on the Microsoft high availability and network resiliency platform delivered in Exchange 2013.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |