Exchange 2016 "hybrid server" in Exchange 2010 environment

%3CLINGO-SUB%20id%3D%22lingo-sub-310065%22%20slang%3D%22en-US%22%3EExchange%202016%20%22hybrid%20server%22%20in%20Exchange%202010%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-310065%22%20slang%3D%22en-US%22%3E%3CP%3ECurrent%20Exchange%20environment%3A%20Exchange%202010%20SP3%20RU%2024%3CBR%20%2F%3EFuture%20plans%3A%20set%20up%20hybrid%20environment%20with%20Exchange%20Online%2C%20migrate%20all%20mailboxes%20to%20EXO.%3CBR%20%2F%3EQuestion%3A%20how%20and%20when%20to%20add%20the%20Exchange%202016%20server%20that%20will%20be%20the%20onsite%20%22hybrid%20server%22%20after%20Exchange%202010%20EOL%20(January%202020).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EYes%2C%20I%20put%20%22hybrid%20server%22%20in%20quotes%2C%20knowing%20that%20this%20term%20has%20been%20criticized.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20the%20objective%20is%20to%20migrate%20all%20mailboxes%20to%20Exchange%20Online%20(EXO)%20but%20that%20migration%20may%20be%20completed%20quite%20close%20to%20Exchange%202010%20EOL.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegardless%2C%20it%20appears%20that%20we%20need%20to%20maintain%20at%20least%201%20on-premises%20Exchange%20server%20(yes%2C%20we%20use%20DirSync%2FAD%20Connect).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20suggestion%20was%20made%20verbally%20(by%20a%20Microsoft%20rep%20and%20also%20some%20FastTrack%20consultants)%20to%20add%20a%20Exchange%202016%20server%20as%20the%20on-premises%20%22hybrid%20server%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReasons%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20Hybird%20Configuration%20Wizard%20in%20Exchange%202016%20is%20supposedly%20improved%20(no%2C%20we%20have%20not%20yet%20run%20the%20HCW).%3C%2FLI%3E%3CLI%3EWe%20could%20use%20it%20to%20migrate%20the%20mailboxes%20(apparently%20lessening%20the%20load%20on%20the%20actual%20servers%20housing%20the%20on-prem%20mailboxes).%3C%2FLI%3E%3CLI%3EAs%20Exchange%202010%20EOL%20approaches%2C%20we'll%20have%20to%20configure%20an%20Exchange%202016%20server%20as%20the%20on-prem%20%22hybrid%20server%22%20regardless.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConcerns%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Exchange%20migrations%2C%20it%20is%20typical%20to%20point%20client%20access%20DNS%20records%20to%20the%20server(s)%20running%20the%20latest%20version%20of%20Exchange%20since%20later%20versions%20of%20Exchange%20can%20proxy%2Fredirect%20back%20to%20earlier%20versions%20of%20Exchange%20(for%20example%2C%20to%20access%20mailboxes%20that%20have%20not%20yet%20been%20migrated%20in%20a%20strictly%20on-premises%20migration%20-%20from%20one%20version%20of%20Exchange%20to%20another).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20this%20scenario%2C%20it%20is%20not%20our%20intent%20to%20migrate%20any%20mailboxes%20to%20Exchange%202016%20but%20rather%20directly%20to%20the%20Cloud%20(EXO).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3EIf%20we%20direct%20client%20access%20connections%20to%20the%20sole%20Exchange%202016%20server%2C%20we%20have%20a%20single%20point%20of%20failure.%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%2C%20if%20we%20do%20not%20intend%20to%20migrate%20any%20mailboxes%20to%20Exchange%202016%20on-prem%2C%20do%20we%20need%20to%20direct%20client%20access%20to%20the%20latest%20version%20of%20Exchange%20(2016%20in%20this%20case)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20been%20in%20this%20situation%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20so%2C%20how%20did%20you%20proceed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance%2C%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-310065%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-310066%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20%22hybrid%20server%22%20in%20Exchange%202010%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-310066%22%20slang%3D%22en-US%22%3EClarification%3A%20we%20currently%20have%202%20Exchange%202010%20servers%20in%20a%20DAG%20(with%20incoming%20client%20connections%20load-balanced).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-920156%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20%22hybrid%20server%22%20in%20Exchange%202010%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-920156%22%20slang%3D%22en-US%22%3EDid%20you%20ever%20find%20any%20answers%20to%20this%20question%3F%20Minus%20the%20dual%20server%2FDAG%20you%20have%20i%20have%20the%20exact%20same%20question.%20Single%20server%20that%20i%20can%20move%20all%20users%20to%20the%20cloud%20using%20a%20hybrid%20but%20when%20is%20the%20hybrid%20introduced%20and%20is%20the%202016%20server%20what%20is%20used%20for%20all%20the%20moves%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-920329%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20%22hybrid%20server%22%20in%20Exchange%202010%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-920329%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F73034%22%20target%3D%22_blank%22%3E%40David%20Machula%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20install%202%20Exchange%202016%20and%20have%20load%20balancing%20to%20them%20and%20move%20all%20pointers'%20DNS%2C%20Connectors%20and%20so%20on%20to%20them.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20best%20practice%20is%20that%20you%20always%20implement%20a%20migration%20strategy%20to%20avoid%20downtime%20regarding%20your%20architecture.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20advise%20that%20you%20implement%20Hybrid%20with%202%20Exchange%202016%20and%20then%20migrate%20all%20Mailboxes%20to%20Office%20365%20leaving%20the%20Exchange%202016%20to%20manage%20proposes.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3ENuno%20%C3%81rias%20Silva%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1033873%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20%22hybrid%20server%22%20in%20Exchange%202010%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1033873%22%20slang%3D%22en-US%22%3E%3CP%3EUsing%20the%20above%20configuration%20is%20it%20possible%20to%20add%20the%20Exchange%202016%20server%20as%20the%20hybrid%20and%20leave%20the%20DNS%20pointers%20directing%20to%20the%20Exchange%202010%20DAG%3F%20Run%20the%20HCW%2C%20migrate%20mailboxes%2C%20etc%20and%20then%20once%20everyone%20is%20in%20Exchange%20Online%20repoint%20to%20O365%3F%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F50%22%20target%3D%22_blank%22%3E%40Nuno%20Silva%3C%2FA%3E%20We're%20wondering%20if%20that's%20possible%20without%20repointing%20to%20the%20Exchange%202016%20server.%26nbsp%3B%20Thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1034316%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20%22hybrid%20server%22%20in%20Exchange%202010%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1034316%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F77013%22%20target%3D%22_blank%22%3E%40Mitch%20Sprague%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20you%20have%20an%20Exchange%20that%20is%20more%20recent%20in%20your%20infrastructure%20like%20your%20scenario%20(Exchange%202016%20with%202010)%20is%20advised%20to%20have%20the%20Hybrid%20in%20the%20most%20recent%20and%20have%20all%20pointers%20to%202016%20to%20avoid%20issues.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3ENuno%20%C3%81ria%20Silva%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Current Exchange environment: Exchange 2010 SP3 RU 24
Future plans: set up hybrid environment with Exchange Online, migrate all mailboxes to EXO.
Question: how and when to add the Exchange 2016 server that will be the onsite "hybrid server" after Exchange 2010 EOL (January 2020).

 

Yes, I put "hybrid server" in quotes, knowing that this term has been criticized.

 

So the objective is to migrate all mailboxes to Exchange Online (EXO) but that migration may be completed quite close to Exchange 2010 EOL.

 

Regardless, it appears that we need to maintain at least 1 on-premises Exchange server (yes, we use DirSync/AD Connect).

 

A suggestion was made verbally (by a Microsoft rep and also some FastTrack consultants) to add a Exchange 2016 server as the on-premises "hybrid server".

 

Reasons:

 

  • The Hybird Configuration Wizard in Exchange 2016 is supposedly improved (no, we have not yet run the HCW).
  • We could use it to migrate the mailboxes (apparently lessening the load on the actual servers housing the on-prem mailboxes).
  • As Exchange 2010 EOL approaches, we'll have to configure an Exchange 2016 server as the on-prem "hybrid server" regardless.

 

Concerns:

 

In Exchange migrations, it is typical to point client access DNS records to the server(s) running the latest version of Exchange since later versions of Exchange can proxy/redirect back to earlier versions of Exchange (for example, to access mailboxes that have not yet been migrated in a strictly on-premises migration - from one version of Exchange to another).

 

In this scenario, it is not our intent to migrate any mailboxes to Exchange 2016 but rather directly to the Cloud (EXO).

 

If we direct client access connections to the sole Exchange 2016 server, we have a single point of failure.

 

But, if we do not intend to migrate any mailboxes to Exchange 2016 on-prem, do we need to direct client access to the latest version of Exchange (2016 in this case)?

 

Has anyone been in this situation?

 

If so, how did you proceed?

 

Thank you in advance,

David

5 Replies
Highlighted
Clarification: we currently have 2 Exchange 2010 servers in a DAG (with incoming client connections load-balanced).
Highlighted
Did you ever find any answers to this question? Minus the dual server/DAG you have i have the exact same question. Single server that i can move all users to the cloud using a hybrid but when is the hybrid introduced and is the 2016 server what is used for all the moves?
Highlighted

Hi @David Machula,

 

You can install 2 Exchange 2016 and have load balancing to them and move all pointers' DNS, Connectors and so on to them.

 

The best practice is that you always implement a migration strategy to avoid downtime regarding your architecture.

 

I advise that you implement Hybrid with 2 Exchange 2016 and then migrate all Mailboxes to Office 365 leaving the Exchange 2016 to manage proposes. 

 

Best regards,

Nuno Árias Silva 

Highlighted

Using the above configuration is it possible to add the Exchange 2016 server as the hybrid and leave the DNS pointers directing to the Exchange 2010 DAG? Run the HCW, migrate mailboxes, etc and then once everyone is in Exchange Online repoint to O365?  @Nuno Silva We're wondering if that's possible without repointing to the Exchange 2016 server.  Thoughts?

Highlighted

Hi @Mitch Sprague,

 

When you have an Exchange that is more recent in your infrastructure like your scenario (Exchange 2016 with 2010) is advised to have the Hybrid in the most recent and have all pointers to 2016 to avoid issues.

 

Best regards,

Nuno Ária Silva