Forum Discussion
Dan_Snape
Sep 05, 2017Steel Contributor
Exchange 2010 and 2016 coexistence
We've just installed Exchange server 2016 in an existing Exchange server 2010 environment. We've had an issue where the Default receive connector on the HT servers has been configured to only receive...
- Sep 14, 2017To see what is happening get the message headers and post them to exrca.com. This will show things like 2010 mapi to 2010 transport (as I described above) and later the last hop being to 2010. As the mailbox is on 2010, the transport service must deliver it to a Hub Transport role. 2016 cannot deliver to a 2010 mailbox. 2016 can deliver to 2010 transport but only 2010 transport can deliver to 2010 mailbox (as transport to transport is not version dependant but transport to and from mailbox is version dependant)
Brian Reid
Sep 11, 2017MVP
"isn't running the HT server role, notifications that a message is waiting are load balanced among Hub Transport servers by using round robin,"
So nearly right! When a mailbox delivers to transport service it is ALWAYS version dependent. But when delivering cross AD site, it is NEVER version dependent.
That means, mailbox 2010 to transport server initially will stay 2010. But when then delivering to another AD site, or receiving from another AD site, the sending transport service will round robin across all the transport servers that are online in the target site.
Brian Reid
So nearly right! When a mailbox delivers to transport service it is ALWAYS version dependent. But when delivering cross AD site, it is NEVER version dependent.
That means, mailbox 2010 to transport server initially will stay 2010. But when then delivering to another AD site, or receiving from another AD site, the sending transport service will round robin across all the transport servers that are online in the target site.
Brian Reid
Courtney Piratzky
Jul 11, 2018Copper Contributor
This was exactly the answer I needed. Thanks so much Brian!!!