The best overall approach is to migrate directly to a Windows Server 2016 functional level—but only if you can ensure that every domain controller in your environment is or will soon be running Windows Server 2016 (or later) and that all integrated applications are compatible with the newer features.
There's not specific requirements but in my experience is better go to 2016
Step by Step;
- Deploy New Domain Controllers Running Server 2016: Introduce new DCs into your environment that run Windows Server 2016. This ensures you’re starting to build the infrastructure with the latest OS capabilities.
- Ensure AD Health and Replication: Use tools like
dcdiag
andrepadmin
to verify that new and existing domain controllers are replicating correctly. Clean replication is critical for a smooth transition. - Transfer FSMO Roles: Once the Server 2016 DCs are stable, transfer all Flexible Single Master Operation roles from your older controllers to the new ones.
- Demote and Remove Legacy Domain Controllers: Gradually demote and remove any Windows Server 2008 (or 2008 R2/2012, if present) domain controllers. This step is mandatory to raise the functional level to 2016.
- Raise the Domain and Forest Functional Level to 2016: After ensuring every DC is running Server 2016, raise both the Domain Functional Level and the Forest Functional Level to 2016.
😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!