AD domain controller upgrade requirements
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 86e17e5 · +3 −3 lines · also on GitHub
⋯ 17 unchanged lines
1818
1919
The recommended way to upgrade a domain is to promote new servers to domain controllers (DCs) that run a newer version of Windows Server and demote the older domain controllers as needed. This method is preferable to upgrading the operating system of an existing domain controller, also known as an in-place upgrade. This list covers general steps to follow before you promote a server to a domain controller that runs a newer version of Windows Server:
2020
21
−1. Verify the target server meets the [system requirements](../../../get-started/hardware-requirements).
21
+1. Verify the target server meets the [system requirements](../../../get-started/hardware-requirements.md).
2222
1. Verify application compatibility.
2323
1. Review recommendations for moving to a newer version of Windows Server.
2424
1. Verify security settings.
⋯ 40 unchanged lines
6565
6666
## Functional level features and requirements
6767
68
−Windows Server 2019 or later requires a Windows Server 2008 forest functional level as a minimum. Windows Server 2016 requires a Windows Server 2003 forest functional level as a minimum. If the forest contains domain controllers running an older forest functional level than the operating system supports, the installation is blocked. Those domain controllers must be removed and the forest functional level raised to a version that is supported prior to adding newer Windows Server domain controllers to your forest. See [Forest and domain functional levels](../active-directory-functional-levels) for more information about supported functional levels.
68
+Windows Server 2019 or later requires a Windows Server 2008 forest functional level as a minimum. Windows Server 2016 requires a Windows Server 2003 forest functional level as a minimum. If the forest contains domain controllers running an older forest functional level than the operating system supports, the installation is blocked. Those domain controllers must be removed and the forest functional level raised to a version that is supported prior to adding newer Windows Server domain controllers to your forest. See [Forest and domain functional levels](../active-directory-functional-levels.md) for more information about supported functional levels.
6969
7070
### Rolling back functional levels
7171
⋯ 67 unchanged lines
139139
140140
141141
1. Demote and remove the earlier Windows Server domain controller. For information on demoting a DC, see [Demoting Domain Controllers and Domains](../../ad-ds/deploy/Demoting-Domain-Controllers-and-Domains--Level-200-.md)
142
−1. Once the server is demoted and removed you can [raise the forest functional and domain functional levels](../../raise-active-directory-domain-forest-functional-levels) to the latest version of Windows Server.
142
+1. Once the server is demoted and removed you can [raise the forest functional and domain functional levels](/troubleshoot/windows-server/identity/raise-active-directory-domain-forest-functional-levels) to the latest version of Windows Server.
143143
144144
## Next Steps
145145
⋯ 3 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 9 Oct 23:52 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.