Home

Office 365 \ Exchange 2010 Hybrid upgrade

%3CLINGO-SUB%20id%3D%22lingo-sub-744381%22%20slang%3D%22en-US%22%3EOffice%20365%20%5C%20Exchange%202010%20Hybrid%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-744381%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20who%20can%20help%20us%20solve%20the%20following%20problem%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESituation%3C%2FP%3E%3CP%3EExchange%202010%20SP3%20on-prem%20in%20DOMAIN1.COM%2C%20with%20name%20MAIL.DOMAIN1.COM.%20Users%20have%20an%20email%20address%20ending%20on%26nbsp%3B%40DOMAIN2.COM.%3C%2FP%3E%3CP%3EOffice365%20configured%20for%20DOMAIN2.COM%20users.%3C%2FP%3E%3CP%3EWe've%20run%20the%20Hybrid%20Configuration%20Wizard%20to%20connect%20both%20systems.%20When%20configuring%20the%20connectors%2C%20we%20receive%20an%20error%20that%20Office365%20cannot%20created%20a%20TLS%20connection%20between%20O365%20DOMAIN2.COM%20and%20on-prem%20DOMAIN1.COM%20because%20the%20certificate%20handles%20mail.domain1.com.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20users%20are%20already%20migrated.%20But%20they%20don't%20always%20receive%20emails%20from%20on-prem%20users%2C%20and%20online%20users%20cannot%20send%20mails%20to%20on-prem%20users.%20When%20we%20trace%20the%20messages%20we%20see%20that%20messages%20are%20sent%20to%20mail.domain1.com.%20So%20that%20means%20that%20mail%20are%20leaving%20Office365%2C%20but%20they%20are%20not%20received%20at%20the%20on-prem%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20can%20we%20do%20to%20solve%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-744381%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-746697%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20%5C%20Exchange%202010%20Hybrid%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-746697%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3110%22%20target%3D%22_blank%22%3E%40Johan%20Pauly%3C%2FA%3E%26nbsp%3B%20-%20hi%20Johan.%20What%20are%20the%20mx%20records%20pointed%20to%20for%20each%20domain%3F%20(onprem%20or%20o365%3F)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHow%20many%20users%20need%20to%20be%20migrated%20to%20domain2.com%3F%26nbsp%3B%20Also%20can%20you%20confirm%20you%20are%20using%202%20separate%20o365%20tenants%20or%20is%20this%20a%20single%20tenant%20with%20multiple%20domains%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20believe%20if%20it%20is%20a%20low%20number%2C%20the%20best%20method%20would%20be%20to%20create%20empty%20mailboxes%20for%20them%20in%20o365%2C%20cutover%20the%20mx%20records%2C%20and%20wait%20for%20mailflow%20to%20go%20to%20their%20o365%20accounts%20(TTL%201hr%3F)%3C%2FP%3E%0A%3CP%3EThen%26nbsp%3B%20simply%20export%20the%20mailboxes%20to%20pst%20and%20perform%20a%20network%20upload%20to%20their%20corresponding%20mailboxes%20manually.%20This%20may%20not%20be%20viable%20if%20your%20user%20count%20is%20in%20the%20thousands%2C%20but%20for%20a%20small%20to%20midsize%20org%20it%20should%20avoid%20the%20complexities%20of%20connecting%20your%20onprem%20exchange%20organization%20to%20more%20than%20one%20o365%20tenant.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Johan Pauly
Contributor

Hello, who can help us solve the following problem?

 

Situation

Exchange 2010 SP3 on-prem in DOMAIN1.COM, with name MAIL.DOMAIN1.COM. Users have an email address ending on @DOMAIN2.COM.

Office365 configured for DOMAIN2.COM users.

We've run the Hybrid Configuration Wizard to connect both systems. When configuring the connectors, we receive an error that Office365 cannot created a TLS connection between O365 DOMAIN2.COM and on-prem DOMAIN1.COM because the certificate handles mail.domain1.com.

 

Some users are already migrated. But they don't always receive emails from on-prem users, and online users cannot send mails to on-prem users. When we trace the messages we see that messages are sent to mail.domain1.com. So that means that mail are leaving Office365, but they are not received at the on-prem server.

 

What can we do to solve this?

1 Reply

@Johan Pauly  - hi Johan. What are the mx records pointed to for each domain? (onprem or o365?)

 

How many users need to be migrated to domain2.com?  Also can you confirm you are using 2 separate o365 tenants or is this a single tenant with multiple domains?

 

I believe if it is a low number, the best method would be to create empty mailboxes for them in o365, cutover the mx records, and wait for mailflow to go to their o365 accounts (TTL 1hr?)

Then  simply export the mailboxes to pst and perform a network upload to their corresponding mailboxes manually. This may not be viable if your user count is in the thousands, but for a small to midsize org it should avoid the complexities of connecting your onprem exchange organization to more than one o365 tenant.