In our company we are planning to do Windows 2008 R2 migration due to End of Support it reached. We're not that fans of living on edge but this time it appear to be wiser target to Windows Server 2019, not 2016 (so we'll live with for years further).
While reading on this topic and looking for best practice approaches I can see many people recommend to do step-by-step migration (2008R2 -> 2012 -> 2016 -> 2019), but in our case it appears to be very lengthy and error-prone way, isn't it? At the same time, looks like we can do that in one giant step (2008R2 -> 2019) so I would like to ask your advice, is it true?
If you want to upgrade the actual servers by performing an in-place upgrade (which I highly advise against), you need to go through multiple steps.
But if you want to add new 2019 Domain Controllers to replace the existing ones, then yes, you can definitely add 2019 DCs in a 2008R2 domain, after the standard preparatory steps (adprep).
Also make sure your SYSVOL uses DFS replication instead of FRS; which it should, but sometimes FRS just stays there because nobody bothered changing that after upgrading from 2003. FRS is not supported anymore and you can't add a 2019 DC in domain which still uses it.
Also, take extra care if you have non-Windows (or old Windows such as XP) devices that use Active Directory for authentication; they might be not compatible with 2019 DCs due to their stronger security settings.
According to Microsoft's Upgrade Scenario Planner, you must upgrade to Windows Server 2019 from Server 2008 R2 in three steps:
There's no way around this. Attempting to skip one of these steps will not work because the installer for the new version of Windows Server will refuse to run if the prior version is not supported for upgrade.
We upgraded over 100 virtual 2008R2 Servers with only two version changes. We had no issues with drivers because they were all VMs. There was no DC among the machines, we join 2019 DCs to the AD and remove the old ones after that. Maybe driver support issues could be a reason why the migration info from MS states that it needs to be a three step version upgrade. This is what we do with every server 2008R2: 1. Go offline 2. Upgrade 2008R2 to Server 2012R2 3. Upgrade 2012R2 to Server 2019 4. Go online 5. Get Updates for Server 2019