Dear sir / madam, It is my understanding that Exchange 2010 CU22+ can exist in a 2019 AD environment[1], furthemore a 2008 R2 DC can be migrated directly to Server 2019[2] We're running SBS2011, we now have the hardware in place. so i would like to start the migration ASAP. Would it be feasible if i first stand up a new 2019 based DC (which would temporarily coexist with the SBS 2011 DC [feature level 2008 R2] and then - afterwards (within 21 days) - stand up a Server-2016 / Exchange-2016 (Hyper-V based) install to migrate Exchange 2010 to. (I already read that the CA can't be migrated directly to 2019 in a SBS 2011 migration scenario[3].) So am i missing anything else here, or can I first (without significant downtime like Exchange 2010 suddenly cutting out): Migrate from SBS 2011 to Server 2019 Standard as far as the DC/DNS/SMB roles are concerned, a bit like this manual: https://server-essentials.com/support/migrate-sbs-2011-to-windows-server-2019 and second (within 21 days) : Migrate the Exchange role to Server 2016 / Exchange 2016. https://server-essentials.com/support/migrate-sbs2011-exchange-server-2010-to-exchange-server-2016
and third and finally (within 180 days), migrate to Exchange 2019: https://server-essentials.com/support/migrate-exchange-server-2016-to-exchange-server-2019-in-a-sbs-migration-scenario
Thanks for helping out! Regards, Ruben
Before you can migrate Exchange Server 2016 to Exchange Server 2019 the old SBS 2011 has to be demoted and Domain and Forest Functional needs to be raised to WindowsServer2012R2 as a minimum.
Alright, so you're saying that as long as I keep this in mind (and act accordingly) we'll be good as far as the high level migration plan is concerned, right?
Your browser doesn't have Flash, Silverlight or HTML5 support.