Moving Exchange 2010 SP3 from Server 2008R2 to new Server 2019 VM

%3CLINGO-SUB%20id%3D%22lingo-sub-1063455%22%20slang%3D%22en-US%22%3EMoving%20Exchange%202010%20SP3%20from%20Server%202008R2%20to%20new%20Server%202019%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1063455%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%2C%20lots%20going%20on%20in%20that%20title%2C%20so%20here%20we%20go.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20a%20small%20shop%20of%20%26lt%3B100%20people%20and%20a%20few%20physical%20servers%20(DC%20the%20only%202012%20server.%20Everything%20else%20still%202008r2).%20We%20are%20getting%20ready%20to%20pull%20the%20trigger%20on%20a%20hardware%20refresh%20for%20our%20entire%20infrastructure%20moving%20almost%20entirely%20to%20virtualized%20environment.%20My%20plan%20is%20to%20first%20get%20the%20new%202019%20DC%20stood%20up%20correctly%2C%20then%20tackle%20the%20rest.%20Exchange%20is%20one%20of%20those%20pieces.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20EXC%202010%20SP3%20running%20on%20Server%202008r2%20in%20a%20hybrid%20environment%20where%20on-prem%20is%20almost%20only%20for%20management%20(a%20couple%20of%20local%20mailboxes%20for%20things%20like%20network%20scanner%20and%20such%20that%20I'm%20working%20to%20move%20online).%20All%20regular%20user%20mailboxes%20are%20in%20Exchange%20Online.%20My%20goal%20is%20to%20setup%20the%20new%20EXC%20server%20in%20a%20Server%202019%20VM%2C%20then%20install%20Exchange%20(2016%3F%202019%3F)%20and%20migrate%2Fmove%20mailboxes%20and%20settings%20from%20the%20old%20box%20to%20the%20new%20VM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOf%20course%2C%20that%20brings%20a%20list%20of%20questions%3A%3C%2FP%3E%3CP%3E-%20should%20I%20upgrade%20the%20current%20EXC%202010%20install%20to%202013%20or%202016%20to%20make%20that%20migration%2Fmove%20easier%20or%20is%20that%20an%20unnecessary%20step%20(because%20of%20the%20current%20environment%20config%2C%20size%2C%20etc)%3F%20I%20know%20that%20EX2010%20and%20EX2019%20can't%20live%20together%2C%20so%20I%20was%20leaning%20toward%20upgrading%20first%20to%202016%20then%20migrating%20to%20the%20new%202019%20server.%3C%2FP%3E%3CP%3E-%20I%20thought%20I%20read%20somewhere%20that%20if%20all%20of%20my%20mailboxes%20were%20in%20Exchange%20Online%20the%20EX2016%20license%20has%20a%20hybrid%20model%2Foption%20that%20is%20%22free.%22%20Is%20that%20correct%20and%20applicable%3F%20Does%20the%20same%20thing%20apply%20to%20ED2019%20with%20only%20mailboxes%20online%3F%3C%2FP%3E%3CP%3E-%20I%20found%20the%20Exchange%20Deployment%20Wizard%2C%20but%20there%20is%20no%202019%20option.%20Is%20that%20out%20there%20somewhere%20or%20even%20necessary%20to%20go%20from%20'16-'19%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20short%2C%20my%20plan%20currently%20looks%20like%20this%3A%3C%2FP%3E%3CP%3E-%20upgrade%20EX2010%20to%20EX2016%20(even%20now%20before%20the%20new%20hardware%20arrives)%26nbsp%3B%3C%2FP%3E%3CP%3E-%20setup%20new%202019%20DC%20(and%20demote%20old%202012%20DC)%3C%2FP%3E%3CP%3E-%20install%20new%202019%20Server%20VM%3C%2FP%3E%3CP%3E-%20install%20EX2019%20into%20new%202019VM%3C%2FP%3E%3CP%3E-%20migrate%20EX2016%20setup%2Fdata%20to%20new%20EX2019%3C%2FP%3E%3CP%3E-%20remove%20EX2016%20server%3C%2FP%3E%3CP%3E*somewhere%20in%20that%20process%20setting%20up%20the%20hybrid%20settings%20on%20the%20new%20EX2016%20install%20and%20eventually%20the%20new%20EX2019%20box%20I%20assume%20has%20to%20happen%20or%20does%20that%20migrate%20well%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20all!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1063455%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%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071423%22%20slang%3D%22en-US%22%3ERe%3A%20Moving%20Exchange%202010%20SP3%20from%20Server%202008R2%20to%20new%20Server%202019%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071423%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F427234%22%20target%3D%22_blank%22%3E%4010toes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYour%20plan%20of%20action%20to%20tackle%20this%20looks%20good%20and%20it%20will%20get%20the%20job%20done!%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3Eupgrade%20EX2010%20to%20EX2016%20(even%20now%20before%20the%20new%20hardware%20arrives)%26nbsp%3B%3C%2FP%3E%3CP%3E-%20setup%20new%202019%20DC%20(and%20demote%20old%202012%20DC)%20-%3CU%3E%3CSTRONG%3E%20Dont%20forget%20to%20prep%20the%20AD%20and%20Schema%20for%20Exchange%202016%2F2019%3C%2FSTRONG%3E%3C%2FU%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20install%20new%202019%20Server%20VM%3C%2FP%3E%3CP%3E-%20install%20EX2019%20into%20new%202019VM%3C%2FP%3E%3CP%3E-%20migrate%20EX2016%20setup%2Fdata%20to%20new%20EX2019%3C%2FP%3E%3CP%3E-%20remove%20EX2016%20server%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20you%20are%20in%20a%20hybrid%20with%20all%20mailboxes%20located%20in%20Exchange%20Online%20%2C%20I%20think%20your%20Exchange%20VM%20doesnt%20have%20to%20be%20very%20%22big%22%20performance%20wise.%20That%20is%20of%20course%2C%20if%20your%20MX%20records%20are%20pointed%20to%20Exchange%20Online%20and%20all%20the%20virtual%20directories%20(%20Autodiscover%20etc%20)%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20got%20pretty%20much%20everything%20in%20the%20cloud%20then%20this%20will%20be%20a%20very%20stragith%20forward%20migration%20to%20Exchange%202016%2F2019%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EJust%20dont%20forget%20to%20prep%20the%20AD%20and%20Schema%2C%20and%20also%20to%20re-do%20the%20Hybrid%20Config%20for%20the%20new%20Exchange%20Server.%20And%20set%20up%20the%20send%2FReceive%20connectors.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20recommend%20a%20new%20SAN%20Cert%20with%20the%20new%20VMs%20FQDN%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20goes%20well!%26nbsp%3B%3CBR%20%2F%3ELet%20me%20know%20if%20you%20have%20futher%20questions!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20Regards%3CBR%20%2F%3EOliwer%20sj%C3%B6berg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071981%22%20slang%3D%22en-US%22%3ERe%3A%20Moving%20Exchange%202010%20SP3%20from%20Server%202008R2%20to%20new%20Server%202019%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071981%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F345947%22%20target%3D%22_blank%22%3E%40oliwer_sjoberg%3C%2FA%3E%26nbsp%3Bthanks%20very%20much%20for%20the%20reply.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20what%20I've%20read%2C%20there%20is%20no%20longer%20a%20%22free%20hybrid%20license%20key%22%20for%20EX2019%20only%202016%2C%20correct%3F%20That%20means%20I'll%20be%20setting%20up%20EX2016%20on%20the%20new%20Server%202019%20VM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20correct%20to%20think%20that%20I%20cannot%20(or%20should%20not)%20%22upgrade%22%20the%20existing%20EXC2010%20server%20to%202016%20in%20place%3F%20Since%20it%20doesn't%20look%20like%20I'll%20be%20going%20to%20EX2019%2C%20does%20it%20make%20sense%20to%20even%20worry%20about%20updating%20the%20existing%20EX2010%20install%20at%20all%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20prepping%20the%20AD%20ad%20schema%20for%202016%20adversely%20effect%20the%20existing%202010%20install%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1072890%22%20slang%3D%22en-US%22%3ERe%3A%20Moving%20Exchange%202010%20SP3%20from%20Server%202008R2%20to%20new%20Server%202019%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072890%22%20slang%3D%22en-US%22%3EDon't%20upgrade%20in%20place%20-%20it's%20not%20supported.%3CBR%20%2F%3E%3CBR%20%2F%3EDon't%20go%20Exchange%202019%2C%20you%20just%20need%20Exchange%202016%20for%20hybrid%20at%20no%20Exchange%20Server%20cost%20(OS%20license%20still%20needed)%20-%20but%20this%20is%20not%20true%20for%20Exchange%202019%20for%20which%20you%20can%20only%20buy%20on%20Volume%20Licence%20and%20is%20not%20free%20to%20use%20for%20hybrid%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1073246%22%20slang%3D%22en-US%22%3ERe%3A%20Moving%20Exchange%202010%20SP3%20from%20Server%202008R2%20to%20new%20Server%202019%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073246%22%20slang%3D%22en-US%22%3EOk%20since%20I'm%20going%20ex2016%20on%20the%20new%202019%20VM%20with%20the%20free%20hybrid%20license%2C%20do%20I%20need%20to%20do%20anything%20with%20the%20existing%20ex2010%20server%20(latest%20CU%2C%20upgrade%20to%20ex2013%2C%20etc)%20before%20setting%20up%20the%20new%20server%2C%20or%20is%20that%20just%20wasted%20effort%20since%20it's%20going%20away%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20again%20all!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1073527%22%20slang%3D%22en-US%22%3ERe%3A%20Moving%20Exchange%202010%20SP3%20from%20Server%202008R2%20to%20new%20Server%202019%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073527%22%20slang%3D%22en-US%22%3EUpgrade%20it%20-%20no.%20But%20on%20latest%20service%20pack%2Froll%20up%20-%20that%20is%20required%20before%20you%20add%20Exchange%20Server%202016%20to%20ensure%20it%20keeps%20working.%3C%2FLINGO-BODY%3E
Occasional Contributor

I know, lots going on in that title, so here we go.

 

We're a small shop of <100 people and a few physical servers (DC the only 2012 server. Everything else still 2008r2). We are getting ready to pull the trigger on a hardware refresh for our entire infrastructure moving almost entirely to virtualized environment. My plan is to first get the new 2019 DC stood up correctly, then tackle the rest. Exchange is one of those pieces.

 

We have EXC 2010 SP3 running on Server 2008r2 in a hybrid environment where on-prem is almost only for management (a couple of local mailboxes for things like network scanner and such that I'm working to move online). All regular user mailboxes are in Exchange Online. My goal is to setup the new EXC server in a Server 2019 VM, then install Exchange (2016? 2019?) and migrate/move mailboxes and settings from the old box to the new VM.

 

Of course, that brings a list of questions:

- should I upgrade the current EXC 2010 install to 2013 or 2016 to make that migration/move easier or is that an unnecessary step (because of the current environment config, size, etc)? I know that EX2010 and EX2019 can't live together, so I was leaning toward upgrading first to 2016 then migrating to the new 2019 server.

- I thought I read somewhere that if all of my mailboxes were in Exchange Online the EX2016 license has a hybrid model/option that is "free." Is that correct and applicable? Does the same thing apply to ED2019 with only mailboxes online?

- I found the Exchange Deployment Wizard, but there is no 2019 option. Is that out there somewhere or even necessary to go from '16-'19?

 

In short, my plan currently looks like this:

- upgrade EX2010 to EX2016 (even now before the new hardware arrives) 

- setup new 2019 DC (and demote old 2012 DC)

- install new 2019 Server VM

- install EX2019 into new 2019VM

- migrate EX2016 setup/data to new EX2019

- remove EX2016 server

*somewhere in that process setting up the hybrid settings on the new EX2016 install and eventually the new EX2019 box I assume has to happen or does that migrate well?

 

Thanks all!

5 Replies

Hello! @10toes 

 

Your plan of action to tackle this looks good and it will get the job done! 

upgrade EX2010 to EX2016 (even now before the new hardware arrives) 

- setup new 2019 DC (and demote old 2012 DC) - Dont forget to prep the AD and Schema for Exchange 2016/2019 

- install new 2019 Server VM

- install EX2019 into new 2019VM

- migrate EX2016 setup/data to new EX2019

- remove EX2016 server

 

Since you are in a hybrid with all mailboxes located in Exchange Online , I think your Exchange VM doesnt have to be very "big" performance wise. That is of course, if your MX records are pointed to Exchange Online and all the virtual directories ( Autodiscover etc ) 

If you got pretty much everything in the cloud then this will be a very stragith forward migration to Exchange 2016/2019 


Just dont forget to prep the AD and Schema, and also to re-do the Hybrid Config for the new Exchange Server. And set up the send/Receive connectors. 

 

Also recommend a new SAN Cert with the new VMs FQDN

 

Hope this goes well! 
Let me know if you have futher questions! 

 

Kind Regards
Oliwer sjöberg

@oliwer_sjoberg thanks very much for the reply.

 

From what I've read, there is no longer a "free hybrid license key" for EX2019 only 2016, correct? That means I'll be setting up EX2016 on the new Server 2019 VM.

 

Am I correct to think that I cannot (or should not) "upgrade" the existing EXC2010 server to 2016 in place? Since it doesn't look like I'll be going to EX2019, does it make sense to even worry about updating the existing EX2010 install at all?

 

Will prepping the AD ad schema for 2016 adversely effect the existing 2010 install?

Don't upgrade in place - it's not supported.

Don't go Exchange 2019, you just need Exchange 2016 for hybrid at no Exchange Server cost (OS license still needed) - but this is not true for Exchange 2019 for which you can only buy on Volume Licence and is not free to use for hybrid
Ok since I'm going ex2016 on the new 2019 VM with the free hybrid license, do I need to do anything with the existing ex2010 server (latest CU, upgrade to ex2013, etc) before setting up the new server, or is that just wasted effort since it's going away?

Thanks again all!
Upgrade it - no. But on latest service pack/roll up - that is required before you add Exchange Server 2016 to ensure it keeps working.