<div>
Your best bet is to build new servers and migrate each boxes services to the corresponding new server...<br>I do not think you can migrate to exchange 2019 from 2010, and you will have to go to 2016 first.<br>Sql is a dump on old server and restore on the new, but you also have to determine if you have old legacy apps that won't work with newer SQL..<br>You have a large job to do, and you are already several years behind in doing it.<br>File and print servers are easy to migrate, and AD is best done by adding new AD servers and after everything syncs demoting the old.<br>This could easily be a year long project for one person...<br><br>
</div>


<div>
Yes, I would fully agree with Scott, some work to do...<br><br>1.) I would start to upgrade the AD first. So add new servers as AD Servers and move FSMO roles.<br>Also move all AD related services like DNS, DHCP etc. <br>Leave the new DCs alone as possibly, so no other apps if you can avoid this. <br>Take care about Exchange as Exchange needs a Global Catalog DC.<br>Then remove the older DCs... <br><br>2a.) As far as possible and not already done, neutralize your SQL Servers to always use an SQL Server Alias Name instead of a server names. This makes it easy to test the applications with newer SQL Server versions as you can switch the Server just by pointing the alias name on the SQL Client to the new SQL instance (and also back).<br>But this would also include, that the application uses the alias name in their connections strings.<br><br>2b.) If the SQL only hosts tables, it may be easy (backup old / restore on new). If they use stored procedures, it may fail or you have to correct some items. You may have a look into the application description, which version they support. <br>If you go not have compatibility information, you may just try to copy the databases to the new instance and see, if the application works. Ther also also compatibility level, which may allow to run an older DB on newer server.<br>If it doesn't work, you may either provide several different versions of SQL or install several instances side by site on one machine. <br>Be aware, that applications using SQL servers are using SQL scripts for setup and maintenance, even if the application runs, updates may fail.<br>Also be aware, if the applications are using SQL Server functionalities like reporting services, analysis services etc.<br><br>3.) Exchange will be a step by step migration as for newer servers, you have to raise the domain functional level. You have to make sure, that you eleminate first all other DCs, Apps etc. what relies on an older domain funtional level.<br>Also there are upgrade pathes for Exchange, so &nbsp;you can not simply jump over several versions. You will need intermediate instances. So several single migrations. The way is usually installing a newer version into the Exchange organisation, move all mailboxes, public folders to free up the old instance and remove the old version. <br>As there are several steps connected with Exchnage you should follow a common migration guideline for each upgrade step.<br>As a preparation: Get rid of large mailboxes, old content etc, so cleanup is the first step. <br><br>4.) Application servers may be the last ones, check if there are compatibility prerequisites and dependencies. <br>Most of application doesn't have too much problems to run on newer OS, but you have to verify it. <br>A general test will be always to try to install such applications on a newer OS just to see what happens. But this may not show up all issues, so there is a need of deeper analysis and / or information from the manufacturer. <br>Be aware, that some older functionalities are disabled by default on newer OS or possibly also not available anymore.<br>Be aware, that some older MS App Server doesn't run on newer OS. Also read the documentation.<br><br>Be also aware in general about dependencies according SMB1, TLS or similar as newer OS may disbale them by default. <br><br>5.) File services depends a little bit from the construction. As there are also newer DFS implementations, you may decide to seperate (if not already done) all files to dedicated disc. The disc as it doesn't need a migration as far as the infrastructure (storage) doesn't change. To have them separated allows to migrate File Servers isolated from their underlying storage. <br><br>First step:<br>Create a migration plan, where you define all your applications and servies including dependencies, relations, prerequisites and needed OS roles, possibly permissions. Define the successor for each app / service and see how you can translate the dependencies to the new OS.&nbsp;<br><br>
</div>


<div>
is virtualization a consideration, an option?<br />
What are your plans for SQL, exchange?<br />
The OS transitions depending on what service, software they are running.<br />
<br />
DCs transition to 2012 to then migrate sysvol from ntfrs to dfs-R.<br />
<br />
Are these in a single location, or multiple locations?
</div>


<div>
<blockquote>all exchange 2010 on 2003 and 2008 to exchange 2019 on server 2019</blockquote><br>exchange 2010 and 2019 can't coexist so you will need to go to either 2013 or 2016 first, decommission 2010 <em>then</em> you can migrate to exchange 2019<br><br>exchange 2010 also doesn't support windows 2019 domain controllers so need to factor that in your planning<br><br>if you have 2003 domain controllers, you need to get rid of those before making 2019 domain controllers since they can't coexist; also to promote a 2019 domain controller, need to be at DFSR which means raising your functional levels to (at least) 2008 as a first step. &nbsp;2003 and 2016 can co-exist as domain controllers (2016 is the last to support legacy FRS) so you can include that as part of your migration<br><br>
</div>


<div>
Note that migrate to Exchange 2019 is not useful. Your path will be easier if you plan to migrate to Exchange 2016 on Windows 2016 (only one move/migration). Unfortunately, Exchange 2016 is not supported on Windows 2019.<br><br>The expiration policy is the same for Exchange 2016 and 2019:<a href="https://www.silversands.co.uk/blog/exchange-server-currently-supported/#:~:text=Exchange%202016%20%E2%80%93%20Extended%20support%20will%20be%20from,14th%20of%20October%202025.%20How%20Can%20Silversands%20Help%3F" rel="ugc"></a><br><a href="https://www.silversands.co.uk/blog/exchange-server-currently-supported/#:~:text=Exchange%202016%20%E2%80%93%20Extended%20support%20will%20be%20from,14th%20of%20October%202025.%20How%20Can%20Silversands%20Help%3F" rel="ugc">Exchange Server. What’s currently supported? - Silversands</a>&nbsp; (end of all support &nbsp;14th of October 2025).<br><br>Exchange 2016 can be virtualized easily and supported. Exchange 2019 needs 128 GB of memory!<br>You can have a free license for Exchange 2016 when you hybrid with Exchange Online, but not with Exchange 2019.
</div>


<div>
Bambi explained to you the details "go-to actions".<br>Related to exchange 2019, it's "recommended to have 128 Gb on RAM" but that's a "recommendation" I am able to work with a regular virtualization exchange server with 32 Gb with no problems at all. 128 Gb is not "a must" it's just a recommendation.<br><br>Related to move all domain controllers to 2019, exchange 2019 becomes the only option available for you.
</div>


<div>
128GB might related to a Windows server in GUI versus Core.<br />
<br />
Exchange recommended spec.<br />
<a href="https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019" rel="ugc">https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019</a>
</div>


<div>
<blockquote>Related to exchange 2019, it's "recommended to have 128 Gb on RAM" but that's a "recommendation" &nbsp;I am able to work with a regular virtualization exchange server with 32 Gb with no problems at al &nbsp;</blockquote>Don't compare a lab with a production environment. I use Exchange 2016 VM with only 8 GB in my lab.<br><br>Will you seriously say to a customer to use an Exchange 2019 with 32 GB for his production with the following recommendation from Microsoft?<table><tbody><tr><td>Memory</td><td><br></td><td>Varies by Exchange server role:<ul><li><strong>Mailbox</strong>: 128 GB <strong><u>minimum</u></strong> recommended</li></ul></td></tr></tbody></table><blockquote>Related to move all domain controllers to 2019, exchange 2019 becomes the only option available for you.&nbsp;</blockquote>That is not true :<br><table><thead><tr><th>Operating system environment</th><th>Exchange 2019</th><th>Exchange 2016 CU12 and later</th><th>Exchange 2016 CU7 and later</th><th>Exchange 2016 CU3 to CU6</th><th>Exchange 2016 CU2 and earlier</th><th>Exchange 2013 SP1 and later</th><th>Exchange 2010 SP3 RU22 or later</th><th>Exchange 2010 SP3 RU5 - RU21</th></tr></thead><tbody><tr><td>Windows Server 2019 Active Directory servers</td><td>Supported</td><td><strong><u>Supported</u></strong></td><td>Not supported</td><td>Not supported</td><td>Not supported</td><td>Not supported</td><td>Not supported</td><td>Not supported</td></tr></tbody></table>Exchange 2016 supports AD DS 2019 since the CU12 !<br><a href="https://docs.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2016" rel="ugc">Exchange Server supportability matrix | Microsoft Docs</a>&nbsp;<br><br>
</div>


<div>
I would like to know after Migrating server from 2003 to 2019 domain level and transfer Fsmo roles what is next step in upgrade in place &nbsp;servers 2008 to server 2019 which is already joined old domain of windows server 2003 &nbsp;as member domain and also has sql server installed and exchange installed so do the upgrade will be while joined old domain and then rejoin new one or upgrade has to be occured after disjoin servers from old domain and then join it to new one after upgrade<br>I appreciate to have like action plan or checklist that will explain the concept and procedures in details&nbsp;
</div>


<div>
You didn't say you were replacing the domain, you only said you were replacing the controllers...<br>You don't need a new domain. And you cannot in place upgrade a server with exchange on it, it will break...<br>Creating a new domain is a totally different animal then just upgrading the systems in the old domain...<br><br>
</div>


<div>
If you upgrade Domain controller in the existing forest, you should first update to Windows 2016 domain controllers, because Exchange 2010 cannot work with Windows 2019 domain controllers.<br><br>But if you have only domain controllers 2008 R2 SP1 or more, you can first migrate Exchange 2010 to new Exchange 2016 servers, and after you can migrate domain controllers 2008 R2 to 2019 (using preferably new machines).<br><br>The easiest way to have domain controllers in the right version is to promote new domain controllers on new Windows version and un-promote old servers in old versions.&nbsp;
</div>


<div>
&gt; I appreciate to have like action plan or checklist that will explain the concept and procedures in details &nbsp;<br>It sound a little bit like "tomorrow, I want to patch all my 100 servers"...<br>You can not expect to get something like an action plan for the migration of 100 servers. Neither the question is serious nor any answer of any expert can be here... You can collects hints and tipps here, but the plan you have to make yourself.<br>Alone the conceptual evaluation is a job over several weeks which needs a deep analysis of everything you have. Even you make a technology jump over 16 years.<br>You have to inspect every single application with all their dependencies. Alone the exchange discussions shows, that you can not just start to run straigt away and just click setup.exe to patch to the newest version.You have all the time aware about all current version, which are the prerequisites for the infrastructure. All AD integrated applications (like exchange, but also others) have dependencies for DC support, Domain functional level support etc. and other applications at least for OS Support. And all these questions have to be clarified before you start to update any of you servers. Beside this, newer server have also higher ressource needs what means, you have to calculate some hardware as well.<br>And possibly there are also some infrastructural devices, which need to be able to support newer functionality. You would not be the first one, who went to their bosses to say "hey boss, I guess we have to order a few hundred new printers, and a truck for the garbage" as they will not work with newer OS as no fitting drivers are available. <br><br>Out of this evaluation, you have to create a migration concept, which also defines, which machines can be upgraded / migrated in witch order and which prestages you need to keep up the bridge between the old and the new world.<br>&nbsp;<br>I guess, if you do it alone, you can calculate, that you do not do anything else in the next 12 month than migrating servers under the precondition that your infrastructure between and beside your servers will not double or triple the time. <br><br>You should aware, that you are opening the real big box with a lot of mistakes you can do and sometimes there is no way back.&nbsp; &nbsp;&nbsp;
</div>


arnold

<div>
we have migration for &nbsp;whole domain from 2008 to 2019 &nbsp;and this is for domain controllers that have Fsmo roles and windows features and &nbsp; upgrade for windows member domain &nbsp;that have applications only and&nbsp; that joined to domain 2008 to 2019 and those member domains have server 2008 and applications as sql 2008 and exchange 2010 that will be upgraded to server 2019 with exchange 2019 and sql 2019
</div>


<div>
Hi <a href="https://www.experts-exchange.com/members/DEMAN-BARCELOMVP-Thierry.html" rel="ugc">DEMAN-BARCELO (MVP)&nbsp;</a>&nbsp;<br>could you please to let me know more details known that<br>we have migration plan &nbsp;for &nbsp;whole domain from 2008 to 2019 &nbsp;and this is for domain controllers that have Fsmo roles and windows features and &nbsp; upgrade for windows member domain &nbsp;that have applications only and &nbsp;that joined to domain 2008 to 2019 and those member domains have server 2008 and applications as sql 2008 and exchange 2010 that will be upgraded to server 2019 with exchange 2019 and sql 2019<br>do you mean that application has to be upgraded first while joined old domain on old server and then upgrade to new server and rejoin new domain &nbsp;as sometimes upgrade of apps will need specific requirements for server version
</div>


<div>
With open license purchases you are able to also use 2016 servers for your transitioning.<br>If your domain controllers are 2008 and not 2008 R2 ( which are different systems), you will need to add at least one 2012 r2 or 2016 server and migrate all domain roles to it. You will need this to do any migration work on the exchange. You will also need an exchange 2016 server as you cannot migrate from exchange 2010 to 2019 directly...<br>Virtualization will be your friend here as you can spin up several 2016 servers for the transition.<br>After ad and exchange are on newer servers, then you can finish the transition to 2019...<br>This is the pain you have to put up with for letting the systems get so out of date...<br><br>
</div>


<div>
Hi AA,<br>I explained the constraints of applications as Exchange and Domain controller roles, because it is generally the more complicated.<br>Now, other servers member of Active Directory, as SQL/Server have generally less constraints.<br>SQL is dependent of the server hosting SQL, but not of the version of domain controller (or level of functionality).<br>Nearly all other applications/servers are less dependent of the version of the domain controller.<br>As members, you could have servers since Windows 2000 to Windows 2019.<br>But, if you used roles as ADFS, AD CA(Authority), you can also have so points to verify or update.<br><br>As others, I don't understand why you speak of "new domain". The best and easiest migration are done keeping existing domains/Forests.<br><br>As indicated by Scott or Bembi, once you have migrated or defined a migration plan for Exchange and Domain controllers, other applications/servers should be migrated/upgraded with the appropriate method independantly.
</div>


<div>
OP, it sounds like you need professional assistance. This is a huge job, and from your questions, you have little or no understanding how to do most of it. Just to do the discovery, inventory, dependency checking, and planning could easily take a consultant many weeks, depending on how complicated the environment is. Heck, I have taken weeks to plan a single server migration. Today we're doing an upgrade that has taken us maybe 5 years or more to get done because of lack of vendor support.
</div>


<div>
Hi deman<br>I mean by by domain that it will be server 2019 domain as additional and then promoted<br>but the question here what about servers that are just join domain (server 2008) &nbsp;with no role other than apps connected to database as we need them to be &nbsp;joined server 2019 domain after transfer roles without having issues with application or sql database installed on same server in old state.<br><br>waiting for more advice
</div>


<div>
Still not sure why you are creating a new domain...<br>Are you required to do so, or do you just think you need to?<br><br>
</div>


<div>
Hi AA,<blockquote>that about servers that are just join domain (server 2008) &nbsp;with no role other than apps connected to database as we need them to be &nbsp;joined server 2019 domain after transfer roles</blockquote><br>Usually, you have nothing to do for Windows servers that were joined in the 2008 domain, when new 2019 domain controllers will be promoted, and old 2008 domain controllers un-promote. All servers stay members of the same domain.<br>BUT, you just have to verify that each application in a given version (SQL, ...) is compatible with the 2019 DCs, and with what levels of functionality (Forest/Domain).
</div>


<div>
what about windows &nbsp;member servers 2008 that need to be upgraded to windows server 2019 so to need to be &nbsp;up to date &nbsp;to server 2019 just run upgrade option and everything remain same or need additional work&nbsp;
</div>


<div>
Domain members should ideally have their workloads migrated to new VMs. Yes, that is real work.<br><br>You cannot directly migrate from 2008 R2 to 2019 by doing in-place upgrades. You would first need to upgrade to 2012 R2, and then again from 2012 R2 to 2019.<br><a href="https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-overview" rel="ugc">https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-overview</a>
</div>


<div>
yes I mean by upgrading not directly to 2019 but through 2012 &nbsp;as I want just to be informed regarding to upgrade process for servers member servers joined &nbsp;domain level&nbsp; 2008 ( old situation before upgrade) and after upgrade is it will be automatically recognized raise of domain controller t o 2019 or need disjoining and rejoining domain with local admin&nbsp; to domain level 2019 after promoting servers and do apps will work normally or need to be reinstalled and database need to be restored as in fresh installation .as what do you mean to new vms if it will be overwrite by upgrade option .
</div>


<div>
I really want to warn you that in place upgrades are not the best choice...<br>I can guarantee you will have problems down the road that you might have avoided with migration over upgrades...
</div>


<div>
OP, It will really help if you use periods to separate your ideas into sentences. Your question(s) are very hard to understand, because they're a paragraph long single sentence.
</div>


<div>
<blockquote>what about windows &nbsp;member servers 2008 that need to be upgraded to windows server 2019 so to need to be &nbsp;up to date &nbsp;to server 2019 just run upgrade option and everything remain same or need additional work &nbsp;</blockquote>If the upgrade fails at any step, it is complicated and some time impossible to rollback!&nbsp;
</div>


<div>
&nbsp;I want just to be informed regarding to &nbsp;domain controller Fsmo roles migration from 2008 to 2019 and upgrade process for servers member servers joined &nbsp;domain level &nbsp;2008 ( old situation before upgrade). and after upgrade is it will be automatically recognized raise of domain controller to 2019 or need disjoining and rejoining domain with local admin &nbsp;to domain level 2019 after promoting servers.<br>&nbsp;do apps will work normally or need to be reinstalled and database need to be restored as in fresh installation .as what do you mean to new vms if it will be overwrite by upgrade option .<br>do we need to clone domain controller in seperate test environment and all member servers to secure deployment without touching production and when all goes well we convert testing into Production and decomission production<br><br><br>kindly I need all inputs of all Migration consultants &nbsp;from experts -exchange that have action plan and exact procedures just to double check
</div>


<div>
You can join and elevate a windows server 2019 to a 2008 level domain/forest with the step you already taken where sysvol replication is handled by DFS-R.<br />
Transferring FSMO roles to the new DC 2019 is also available.<br />
Raising the AD/FOREST functional level to 2019 should only be done when you are ready to decomission the 2008 DC and any other DC you may have that is not windows server 2019.<br />
Forest and Domain functional level do not automatically rise, you have to go through AD sites and Services to raise the functional levels.<br />
The only application I've seen discussed in this forum that is incompatible with a windows 2019 DC is exchange pre 2016 version.<br />
I've not heard of SQL servers being reliant on the AD functional level.<br />
<br />
What is your environment made of as it is easier to address the situation based on what makes up your environment versus trying to provide all the possible variances where an issue might arise?<br />
<br />
i.e. when you upgrade to 2019 AD DC, <br />
application A, if you use could have an issue<br />
Application C, runs into a bucksaw,.<br />
<br />
Do you have workstations that are older than windows 7?<br />
Do you have multi-function printers with scan to folder setup?<br />
smbv1 is a vulnerable protocol and is disabled by default on windows server 2019.<br />
It can be enabled, or the common recomendation is to setup ( a VM that lacks internet access, no default gateway ) and have it be the target for these scan to folder server host while using DFS-REplication/DFS share to publish the data for the users.<br />
<br />
<br />
After typing all that, rechecked and I think you're still in the process and the scope of your question is from 2003 through 2008.<br />
<br />
You can not go to 2019 unless the forest/domain functional level is at 2008.<br />
The functional level means no windows server OS version lower than that can be a DC in the environemtn.<br />
Since Server 2016 I think NTFRS is unavailable, but is definately unavailable in server 2019 which requires the migration of sysvol replication from NTFRS to DFS-R.<br />
The GPO/GPP handling updates.<br />
<br />
I think given the assortment of information provided to the general question you posed.<br />
It might be better if you now drill down to specific issues of concern or that might be at issue and open a question to address the specific items individual to avoid commingling/conflicting guidance....
</div>


<div>
Hi arnold<br>I have some concerns and this is one of them and after I can put other concerns in bullets<br>what about cloning domain controller and then do the work during business hours and after cloning member servers and go one by one and then reconnect them to production known that I am using Hyperv do this will affect issues or it is normal for testing out of production environments.please explain
</div>


<div>
<div class="content wysiwyg-content fr-view">
Hi experts<br>I have couple of servers 50 servers as 2003 and 50 others as 2008<br>Most of servers have -( &nbsp;windows server 2003 and installed on it &nbsp; server exchange 2010 and &nbsp;Microsoft &nbsp;sql &nbsp;server 2005 and apps) and<br>&nbsp;( Microsoft &nbsp;sql &nbsp;server &nbsp; 2008 and windows servers &nbsp;sql 2012 and windows server 2008 and apps)<br><br>while servers 2003 has some apps installed on Microsoft &nbsp;sql &nbsp;server sql server 2005 and act as additional domain controller while server 2008 has Fsmo roles, &nbsp;Group policy management ,DFs,File server,Vpn and remote connectivity and terminal servers and Active directory,Dhcp.Dns.Nps,Printer server and HA roles.<br><br>Goal to upgrade to windows server 2016 &nbsp;and Migrate all &nbsp;windows servers &nbsp;2003,2008 to windows server 2019 as &nbsp;windows servers 2008 include all Fsm roles,as well &nbsp;(all exchange 2010 on 2003 and 2008 to exchange 2019 on server 2019 )and (all (windows server 2005 ,on server 2003 to &nbsp;Ms sql server 2019 on windows server 2019 ) and( Ms sql &nbsp;2008 and Ms sql 2012 on windows server 2008) to &nbsp;----&gt; &nbsp;( MSSQL SERVER 2019 on windows servers 2019)&nbsp;
</div>
</div>



Hi experts
I have couple of servers 50 servers as 2003 and 50 others as 2008
Most of servers have -(  windows server 2003 and installed on it   server exchange 2010 and  Microsoft  sql  server 2005 and apps) and
 ( Microsoft  sql  server   2008 and windows servers  sql 2012 and windows server 2008 and apps)
while servers 2003 has some apps installed on Microsoft  sql  server sql server 2005 and act as additional domain controller while server 2008 has Fsmo roles,  Group policy management ,DFs,File server,Vpn and remote connectivity and terminal servers and Active directory,Dhcp.Dns.Nps,Printer server and HA roles.
Goal to upgrade to windows server 2016  and Migrate all  windows servers  2003,2008 to windows server 2019 as  windows servers 2008 include all Fsm roles,as well  (all exchange 2010 on 2003 and 2008 to exchange 2019 on server 2019 )and (all (windows server 2005 ,on server 2003 to  Ms sql server 2019 on windows server 2019 ) and( Ms sql  2008 and Ms sql 2012 on windows server 2008) to  ---->  ( MSSQL SERVER 2019 on windows servers 2019) 

need to migrate and upgrade servers from 2003 and 2008 to  2016  2019

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2019

Server Migration

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.