Upgrade from 2013 to 2016 update#

SharePoint 2013 was Microsoft’s next SharePoint version loaded with some great features after capturing the imagination of users with SharePoint 2010. Exchange Web ServiceĮxchange Web Service Client -> Exchange 2016 -> Authenticates -> Determines mailbox location -> Proxies Connection -> Exchange 2013/2016 Mailbox.Migration from an older version to a new one is driven by the charm of new features added in the newer versions. Active Sync ProtocolĪctive Sync Client -> Exchange 2016 -> Authenticates -> Determines mailbox location -> Proxies Connection -> Exchange 2013/2016 Mailbox. OWA Client -> Exchange 2016 -> authenticates -> Proxies/redirect Connection -> Exchange 2013/2016 Mailbox. Outlook -> Exchange 2016 -> Authenticates -> Determines the mailbox location -> Retrieves the configuration details of Mailbox Exchange 2013 or Exchange 2016 depending on the target mailbox location -> share to the connection URL to the Outlook -> Exchange 2016 -> Authenticates -> Determines mailbox location -> Proxies Connection -> Exchange 2013/2016 Mailbox. Outlook -> Exchange 2016 -> Authenticates -> Determines the mailbox location -> Retrieves the configuration details of Mailbox Exchange 2013 or Exchange 2016 depending on the target mailbox location. The points below outline how various protocols are proxied from Exchange 2013 to Exchange 2016: Autodiscover Exchange 2016 and Exchange 2013 Co-existance. SMTP traffic to Exchange Server 2016 based on the mailbox server location.įigure 2. Load balancers can also be configured to route If the Exchange Server CAS connection is managed using the load balancer then no DNS changes are required as the load balancer can be configured to redirect all the new connections to Exchange 2016 server. If the target mailbox is on an Exchange ServerĢ013 host then Exchange Server 2016 CAS service redirects the request to the Exchange Server 2013 mailbox server. This allows all the clients to connect to Exchange Server 2016, and if the user mailbox is on Exchange 2016, then the CAS service directly proxies the connection to the user’s mailbox. The Exchange Server 2016 servers need configured to work with the URL’s and that are in use on Exchange Same URL for all the client connections.įigure 2 shows a typical deployment model for Exchange Server 2013 and Exchange Server 2016 coexistence. This configuration helps the coexistence between Exchange Server 2013 and Exchange Server 2016 as it uses the Current Exchange 2013 organizations before introduction Exchange 2016 Exchange Organizations after introducing Exchange 2016Īs servers running Exchange 2016 Server are introduced into an organization the same CAS URLs and name space from Exchange 2013 can be used. There are various protocols that clients use to connect to the Exchange server. A correctly configured load balancer setup As a result, it is essential to configure the previous and new Exchange systems to coexist.

When organizations are migrating from Exchange 2013 to Exchange 2016, it may take some time to complete the project. Configuring the Load Balancer when Migrating from Exchange 2013 to Exchange 2016

Load balancers have various mechanism to check the health and availability of target CAS servers and establishes the connection to the most suitable one at any given time. It helps establish the connection from the client to the Exchange Client Access Server (CAS) servers, which run the client connection service, and distributes the clientĬonnection load across the multiple backend Exchange servers. The load balancer setup plays a vital role in client connections to Exchange Server. To CU 10 then you must do this before introducing Exchange Server 2016 if you want them to work together. If you have not updated your Exchange Server 2013 infrastructure

Upgrade from 2013 to 2016 update#

To do this Microsoft Exchange Server 2013 must be running Cumulative Update 10 (CU10) or later. When performing this migration both versions of Exchange Server will need to coexist on the network.