The number of server roles in Exchange 20 shrinks from seven to two: the Mailbox server and the Edge Transport server. The reduced number of server roles for Exchange 2016 and Exchange 2019 simplifies Exchange implementation and hardware requirements. This standard protocol removes the need for affinity, which was previously required to avoid a new prompting for user credentials whenever load balancing redirected the connection to a different server. With the HTTP protocol in use, all native clients connect using HTTP and HTTPs in Exchange Server.

It's now enabled by default in Exchange 2016 and Exchange 2019. Exchange 2013 introduced MAPI over HTTP, although it wasn't enabled by default. Previously, Exchange 2007 and Exchange 2010 supported RPC over HTTP for Outlook Anywhere. Session affinity allows a persistent connection for messaging-enabled services so that a user doesn't have to reenter their username and password multiple times. The HTTP protocol standard introduced with Exchange 2013 means that session affinity is no longer required in Exchange 2016 and Exchange 2019. High availability by deploying load balancers to distribute client traffic. Mail flow managed in the transport pipeline, which is the collection of services, connections, queues, and components that route messages to the Transport service categorizer on the Mailbox server.

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.

M&b record exchange