Exchange 2010 to Exchange 2019 Migration

%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3030640%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3EExchange%202010%20to%20Exchange%202019%20Migration%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3030640%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%3CP%3EOld%20installation%20getting%20around%20to%20upgrading.%20Here%20are%20my%20problems%5C%5Cthoughts%3F%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3ECurrent%20environment%20is%3A%20Single%202008R2%20server%2C%20AD%2C%20Exch%202010.%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3EMoving%20to%20Server%202019%20vm's.%20Have%20a%202019%20guest%20as%20a%20DC%20but%20forest%20level%20still%202008%20R2.%26nbsp%3BExch%202019%20requires%20level%20to%20be%202012%2B.%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3ESo%2C%20after%20I%20move%20the%20file%20share%20and%20SQL%20to%20their%20own%20guests%20(everything%20on%20single%20physical%20machine%20currently)%20plan%20is%20to%20demote%20current%20%22server2%22.%20Exchange%20likely%20will%20complain%20about%20no%20DC%20but%20then%20add%20as%20member%20of%20the%202019%20guest%20DC.%20Then%20bump%20the%20forest%20level%20to%202012%3F%20Then%20install%20Exch%202019%20to%20its%20own%20guest.%20Then%20move%20the%20mailboxes%20from%20the%202010%20store%20to%20the%202019%20store.%20Remove%20and%20uninstall%20Exch%202010.%20Then%20possibly%20bump%20the%20forest%20level%20to%20current%3F%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3EThoughts%5C%5Cissues%3A%20Will%20Exch%202010%20behave%20correctly%20while%20demoting%20%22server2%22%20and%20then%20adding%20the%20machine%20to%20the%20domain%3F%20Is%20it%20possible%20to%20go%20directly%20to%20Exch%202019%20from%20Exch%202010%20or%20do%20I%20have%20to%20create%20an%20Exch%202016%20as%20an%20interim%20step%3F%20I%20would%20really%20hate%20to%20export%20all%20the%20mailboxes%2C%20remove%20Exch%202010%2C%20bump%20the%20forest%2C%20install%20Exch%202019%2C%20and%20import%20the%20mailboxes.%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%2C%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2Flingo-body%26gt%3B%3CLINGO-LABS%20id%3D%22%5C%26quot%3Blingo-labs-3030640%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%3CLINGO-LABEL%3EExchange%202010%202008%20R2%20AD%26lt%3B%5C%2Flingo-label%26gt%3B%26lt%3B%5C%2Flingo-labs%26gt%3B%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3033363%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3ERe%3A%20Exchange%202010%20to%20Exchange%202019%20Migration%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3033363%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3ESo%20far%20so%20good%20migrating%20mailboxes.%20The%20only%20thing%20I%20forgot%20was%20to%20bump%20the%20mailbox%20limit%20so%20got%20some%20sync%20errors%20moving%20some%20mailboxes.%3CBR%20%2F%3E%3CBR%20%2F%3EThere%20is%20the%20next%20step%2C%20moving%20from%20Exch2016%20to%20Exch2019.%20%3A)%26lt%3B%5C%2Fimg%26gt%3B%26lt%3B%5C%2Flingo-body%26gt%3B%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3033139%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3ERe%3A%20Exchange%202010%20to%20Exchange%202019%20Migration%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3033139%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3EGood%20job%20!%3CBR%20%2F%3EEverything%20look%20good%3CBR%20%2F%3ELet%20me%20know%20%3Asmiling_face_with_smiling_eyes%3A%26lt%3B%5C%2Fimg%26gt%3B%26lt%3B%5C%2Flingo-body%26gt%3B%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3033133%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3ERe%3A%20Exchange%202010%20to%20Exchange%202019%20Migration%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3033133%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%40Thierry%20-%20Yes%2C%20found%20that%20out.%20So%20far%20what%20I've%20tested%20is%20the%20following.%3CBR%20%2F%3E%3CBR%20%2F%3ERemoved%20AD%20from%20existing%202008R2.%20Made%20existing%20%22server2%22%20a%20member.%20Promoted%20domain%20%26amp%3B%20forest%20to%202016.%20Still%20connects%20to%20OWA.%3CBR%20%2F%3E%3CBR%20%2F%3ECreated%20Server%202016%20guest%2C%20applied%20.NET%204.8%20%26amp%3B%20UCM%20%26amp%3B%20C%2B%2B%20req's%20as%20stated%20when%20attempted%20to%20install%20Exch2019.%20Exch2016%20required%20kb3206632%20as%20well.%20In%20the%20process%20of%20installing%20Exch2016CU21%20right%20now%20to%20test%20mailbox%20migration.%26lt%3B%5C%2Flingo-body%26gt%3B%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3032482%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3ERe%3A%20Exchange%202010%20to%20Exchange%202019%20Migration%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3032482%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3EFor%20your%20process%20you%20can't%20move%20directly%20from%20Exch%202010%20to%20Exch%202019.%3CBR%20%2F%3EYou%20need%20to%20add%20DC%20with%20the%20compatibility%20matrix%20of%20Exchange%202010%20like%20Windows%202016.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22%5C%26quot%3Bhttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%23supported-active-directory-environments%5C%26quot%3B%22%20target%3D%22%5C%26quot%3B_blank%5C%26quot%3B%22%20rel%3D%22%5C%26quot%3Bnoopener%20nofollow%20noopener%20noreferrer%22%20noreferrer%3D%22%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%23supported-active-directory-environments%26lt%3B%5C%2FA%26gt%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20you%20can%20add%20Exchange%202016%20server.%20Move%20the%20mailboxes%20on%20it.%20When%20is%20done%20remove%20the%20old%20DC%20then%20add%20Windows%202019%20DC%20and%20Exchange%202019%20server.%20Move%20the%20data%20from%20Exchange%202016%20to%202019.%20When%20is%20completed%20remove%20the%20temporary%20Windows%202016%20DC.%26lt%3B%5C%2Flingo-body%26gt%3B%3C%2FA%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E
New Contributor

Old installation getting around to upgrading. Here are my problems\thoughts?

 

Current environment is: Single 2008R2 server, AD, Exch 2010.

Moving to Server 2019 vm's. Have a 2019 guest as a DC but forest level still 2008 R2. Exch 2019 requires level to be 2012+.

 

So, after I move the file share and SQL to their own guests (everything on single physical machine currently) plan is to demote current "server2". Exchange likely will complain about no DC but then add as member of the 2019 guest DC. Then bump the forest level to 2012? Then install Exch 2019 to its own guest. Then move the mailboxes from the 2010 store to the 2019 store. Remove and uninstall Exch 2010. Then possibly bump the forest level to current?

 

Thoughts\issues: Will Exch 2010 behave correctly while demoting "server2" and then adding the machine to the domain? Is it possible to go directly to Exch 2019 from Exch 2010 or do I have to create an Exch 2016 as an interim step? I would really hate to export all the mailboxes, remove Exch 2010, bump the forest, install Exch 2019, and import the mailboxes.

 

Thanks in advance,

4 Replies
For your process you can't move directly from Exch 2010 to Exch 2019.
You need to add DC with the compatibility matrix of Exchange 2010 like Windows 2016.

https://docs.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019...

After you can add Exchange 2016 server. Move the mailboxes on it. When is done remove the old DC then add Windows 2019 DC and Exchange 2019 server. Move the data from Exchange 2016 to 2019. When is completed remove the temporary Windows 2016 DC.
@Thierry - Yes, found that out. So far what I've tested is the following.

Removed AD from existing 2008R2. Made existing "server2" a member. Promoted domain & forest to 2016. Still connects to OWA.

Created Server 2016 guest, applied .NET 4.8 & UCM & C++ req's as stated when attempted to install Exch2019. Exch2016 required kb3206632 as well. In the process of installing Exch2016CU21 right now to test mailbox migration.
Good job !
Everything look good
Let me know :smiling_face_with_smiling_eyes:
So far so good migrating mailboxes. The only thing I forgot was to bump the mailbox limit so got some sync errors moving some mailboxes.

There is the next step, moving from Exch2016 to Exch2019. :)