Comments on: Notes from the Field: Upgrading to Exchange 2019

By: Alex

Alex — Mon, 07 Aug 2023 15:07:27 +0000

In reply to Alex.

the funny thing is that i was able to migrate small mailboxes before adding ip addresses of all exchange servers in all default connectors remote ip.

how is that possible? how did i manage to migrate several mailboxes until it halted the operation completely and nothing was passing anymore until i added the above.

more than 20GB went through between my posts =)

By: Alex

Alex — Mon, 07 Aug 2023 14:32:52 +0000

The Culprit

Check the default connector remote IP address ranges of old Exchange Servers

Many thanks!!!!!

By: Thomas

Thomas — Wed, 05 Jul 2023 07:24:57 +0000

In reply to DavidF. You can have 2016 and 2019 servers in the same LB application pool. The Exchange Server receiving the connection proxies the connection to the Exchange Server holding the active database copy of the mailbox. An Exchange 2019 server can proxy to Exchange 0216 (aka Down-Proxy), and an Exchange 2016 can proxy to Exchange 2019 (aka Up-Proxy). Exchange 2016 and 2019 servers must share the same Kerberos ASA account.

By: DavidF

DavidF — Tue, 02 May 2023 18:30:15 +0000

Any info on mixing Exchange 2016 and 2019 client access servers in a load balancer?

By: StevenB

StevenB — Thu, 05 Jan 2023 02:09:29 +0000

MAPI over HTTP was added to Exchange 2013 SP1, so you could/should enable that