![]() With Exchange 2016 an organization can choose between MAPI over HTTP, or, RPC over HTTP (although the former is now preferred). Unlike its predecessor, Exchange 2016 did not see a shift in client connectivity. ![]() This faster, leaner protocol allowed the Exchange Team to develop shorter failover times between servers. It introduced another virtual directory into the mix–the MAPI virtual directory–which would need to be load balanced as well. Service Pack 1 saw another shift in client connectivity as it introduced the option of MAPI over HTTP (although disabled by default). All client connections to Exchange 2013 were flipped to RPC over HTTP. This was a contrast to 2010 where a client session had to maintain a single path at all times. Ross Smith covers this in greater detail here.Įxchange 2013 also dropped support for traditional RPC connections. It no longer mattered which client access servers in a site were involved in the session. ![]() ![]() This allowed multiple requests from a single client to take different paths to its mailbox. For example, between Exchange 20, the requirement for session affinity was dropped. With each release of Exchange, we have seen a substantial shift in the way it required load balancers to be configured.
0 Comments
Leave a Reply. |