Exchange Hybrid Namespaces

%3CLINGO-SUB%20id%3D%22lingo-sub-352641%22%20slang%3D%22en-US%22%3EExchange%20Hybrid%20Namespaces%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352641%22%20slang%3D%22en-US%22%3E%3CP%3EI%20read%20somewhere%20that%20you%20could%20do%20the%20following%20hybrid%20deployment.%3C%2FP%3E%3CP%3E1)%20Two%20dedicated%20Exchange%202016%20%22hybrid%20servers%22%20that%20are%20F5%20load%20balanced%3C%2FP%3E%3CP%3E2)%20Create%20a%20new%20namespace%20called%20hybrid.contoso.com.%20(Why%20would%20we%20need%20a%20new%20namespace%3F)%3C%2FP%3E%3CP%3E3)%20Create%20internal%20and%20external%20DNS%20A%20record%20for%20hybrid.contoso.com%20(same%20IP%20addresses%3F)%3C%2FP%3E%3CP%3E4)%20Publish%20hybrid.contoso.com%20through%20the%20F5%20load%20balancer.%20(Is%20this%20done%20on%20the%20external%20F5%20or%20both%20the%20internal%20and%20external%20F5.%20We%20also%20have%20BlueCoat%20device)%3C%2FP%3E%3CP%3E4)%20Point%20the%20existing%20autodiscover%20record%20to%20hybrid.contoso.com%20(external).%20(Again%20why%20would%20we%20do%20this%3F%20Will%20that%20mean%20clients%20need%20to%20be%20re-configured%3F).%20Can%20we%20just%20use%20a%20CNAME%20to%20redirect%20autodiscover%20to%20hybrid%3F%3C%2FP%3E%3CP%3E5)%20Point%20the%20existing%20EWS%20services%20to%20hybrid.contoso.com%20(external).%20(I%20supposed%20this%20is%20used%20for%20mailbox%20migration%20path%3F)%3C%2FP%3E%3CP%3E6)%20Create%20two%20A%20records%20called%20smtp1.contoso.com%20and%20smtp2.contoso.com%20and%20configure%20send%20and%20receive%20connectors%20in%20Exchange%20online%20to%20send%20contoso.com%20mails%20to%20these%20smart%20host%20addresses.%20(I%20don't%20know%20why%20this%20is%20needed%20cause%20we%20are%20enabling%20centralised%20transport%20and%20I%20though%20this%20would%20be%20created%20automatically)%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-352641%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

I read somewhere that you could do the following hybrid deployment.

1) Two dedicated Exchange 2016 "hybrid servers" that are F5 load balanced

2) Create a new namespace called hybrid.contoso.com. (Why would we need a new namespace?)

3) Create internal and external DNS A record for hybrid.contoso.com (same IP addresses?)

4) Publish hybrid.contoso.com through the F5 load balancer. (Is this done on the external F5 or both the internal and external F5. We also have BlueCoat device)

4) Point the existing autodiscover record to hybrid.contoso.com (external). (Again why would we do this? Will that mean clients need to be re-configured?). Can we just use a CNAME to redirect autodiscover to hybrid?

5) Point the existing EWS services to hybrid.contoso.com (external). (I supposed this is used for mailbox migration path?)

6) Create two A records called smtp1.contoso.com and smtp2.contoso.com and configure send and receive connectors in Exchange online to send contoso.com mails to these smart host addresses. (I don't know why this is needed cause we are enabling centralised transport and I though this would be created automatically)

Thank you.

0 Replies