hybrid exchange (2010) migrate to new exchange 2016 server in new (trusted) domain

%3CLINGO-SUB%20id%3D%22lingo-sub-1450889%22%20slang%3D%22en-US%22%3Ehybrid%20exchange%20(2010)%20migrate%20to%20new%20exchange%202016%20server%20in%20new%20(trusted)%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1450889%22%20slang%3D%22en-US%22%3E%3CP%3EScenario%3A%3CBR%20%2F%3EExchangeServer2010%20(hybrid)%20is%20a%20member%20of%20DomainA%20which%20has%20a%202way%20trust%20with%20DomainB.%3C%2FP%3E%3CP%3EExchangeServer2016%20(which%20is%20not%20yet%20in%20production)%20is%20a%20member%20of%20DomainB.%3C%2FP%3E%3CP%3EObjects%20of%20DomainA%20are%20synced%20by%20Azure%20AD%20Connect%20with%20Office365.%3C%2FP%3E%3CP%3EExchangeServer2010%20hosts%20on-premise%20mailboxes%20(both%20user%20and%20shared)%20and%20a%20set%20of%20remote-mailboxes%20(both%20user%20and%20shared).%26nbsp%3B%3CBR%20%2F%3EAll%20our%20email%20from%20outside%20our%20organisation%20flows%20into%20our%20ExchangeServer2010%20and%20decides%20if%20recipient%20is%20on-premise%20or%20in%20Exchange%20Online%20and%20sends%20it%20accordingly.%20so%20far%20so%20good.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWhat%20we%20want%3A%3C%2FP%3E%3CP%3EWe%20want%20to%20decomission%20ExchangeServer2010%20in%20DomainA%20and%20migrate%20all%20on-premise%20mailboxes%26nbsp%3B%20(and%20their%20user-objects)%20to%20ExchangeServe2016%20in%20DomainB.%3CBR%20%2F%3EBut%20also%2C%20we%20want%20to%20keep%20all%20user-objects%20with%20remote-mailboxes%20(both%20users%20and%20shared)%20in%20DomainA%20and%20keep%20them%20synced%20by%20Azure%20Ad%20Connect%20synced%20with%20Office365%20and%20manage%20their%20mailboxes%20in%20Office365.%3C%2FP%3E%3CP%3EWe%20want%20our%20future%20mail-flow%20like%20this%3A%3CBR%20%2F%3EHave%20mail%20from%20outside%20our%20organisation%20flow%20to%20ExchangeServer2016%20and%20decide%20if%20recipient%20exists%20on-premise%20and%20if%20not%20check%20with%20and%2For%20forward%20to%20Exchange%20Online.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20not%20sure%20how%20we%20can%20'divorce'%20our%20remote-mail%20users%20from%20ExchangeServer2010%20or%20if%20this%20is%20possible.%3C%2FP%3E%3CP%3EAnd%20we%20dont%20know%20how%20the%20last%20part%26nbsp%3Bin%20our%20future%20mailflow%20(decide%20if%20recipient%20exists%20on-premise%20and%20if%20not%20check%20with%20and%2For%20forward%20to%20Exchange%20Online)%26nbsp%3B%20is%20to%20be%20configured%20on%20ExchangeServe2016.%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20to%20anyone%20who%20can%20shed%20some%20light%20on%20our%20situation!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1450889%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Scenario:
ExchangeServer2010 (hybrid) is a member of DomainA which has a 2way trust with DomainB.

ExchangeServer2016 (which is not yet in production) is a member of DomainB.

Objects of DomainA are synced by Azure AD Connect with Office365.

ExchangeServer2010 hosts on-premise mailboxes (both user and shared) and a set of remote-mailboxes (both user and shared). 
All our email from outside our organisation flows into our ExchangeServer2010 and decides if recipient is on-premise or in Exchange Online and sends it accordingly. so far so good.


What we want:

We want to decomission ExchangeServer2010 in DomainA and migrate all on-premise mailboxes  (and their user-objects) to ExchangeServe2016 in DomainB.
But also, we want to keep all user-objects with remote-mailboxes (both users and shared) in DomainA and keep them synced by Azure Ad Connect synced with Office365 and manage their mailboxes in Office365.

We want our future mail-flow like this:
Have mail from outside our organisation flow to ExchangeServer2016 and decide if recipient exists on-premise and if not check with and/or forward to Exchange Online.

We are not sure how we can 'divorce' our remote-mail users from ExchangeServer2010 or if this is possible.

And we dont know how the last part in our future mailflow (decide if recipient exists on-premise and if not check with and/or forward to Exchange Online)  is to be configured on ExchangeServe2016.

Thank you to anyone who can shed some light on our situation!

0 Replies