Microsoft
MicrosoftI’m not sure it's possible to migrate Active Directory directly from Windows Server 2008 R2 to Windows Server 2022.
Since a direct migration wasn’t feasible from 2012 to 2019, this article may not accurately represent a state-of-the-art Active Directory migration.
From my perspective, intermediate domain controller versions are inevitably required to transition from 2008 R2 to 2022.
Thierry Adrian | https://neoconsultin.io
You misunderstood the procedure.
This is not about upgrade "in-place" of Windows Server OS, this is about installing new Domain Controller servers with Windows Server 2022 OS, then promote them as Domain Controllers and migrate FSMO roles on them. And depromote old Domain Controller servers with 2008 R2 servers.
Then proceed to upgrading the Forest and domain functionning level to 2016.
"A new domain controller with Windows Server 2022(DC22) will be introduced and will be the new FSMO role holder for the domain. Once the FSMO role migration is complete, the domain controller running Windows Server 2008 R2 will be decommissioned. After that, the forest and domain functional levels will be raised to Windows Server 2016."
I have already done it and it works perfectly.
I wanna share an update regarding the Active Directory migration process we discussed previously.
It was not feasible to migrate from Active Directory 2012 to 2019 in a production environment. This was the observation.
However, I’ve successfully conducted a test migration from 2008R2 to 2022 in a freshly installed environment. The migration path from 2008R2 to 2022 appears to be valid.
This is particularly encouraging, as the test has proven to be conclusive and suggests that the process is viable under the right conditions.
I'm not talking about in situ updates either.
Migration with the same method is not feasible from 2012 to 2019 and may therefore be feasible from 2008 R2 to 2022.
All this could be interesting in any case if you can share the detail around the adprep phase and the enactment of 2022 as a domain controller.
I'll test, maybe I've missed some techniques in the Active Directory migration path.
