Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 22:55 UTC Customize Public modeDiscuss ChangeIntel on Discord

AD domain controller upgrade requirements

This page's changes and edits · All guidance changes

Microsoft's edit ·

edit pass: upgrade-domain-controllers

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit d1f9ff7 · +3 −3 lines · also on GitHub

⋯ 47 unchanged lines
4848 | ----- | ----- |
4949 |Install a new forest.|Local admin on the target server|
5050 |Install a new domain in an existing forest.|Enterprise admins|
51 −|Install an additional DC in an existing domain.|Domain admins|
51 +|Install another DC in an existing domain.|Domain admins|
5252 |Run `adprep /forestprep`.|Schema admins, enterprise admins, and domain admins|
5353 |Run `adprep /domainprep`.|Domain admins|
5454 |Run `adprep /domainprep /gpprep.`|Domain admins|
⋯ 13 unchanged lines
6868
6969 ## Functional-level features and requirements
7070
71 −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 DCs running an older forest functional level than the operating system supports, the installation is blocked. Those DCs must be removed and the forest functional level raised to a version that's supported prior to adding newer Windows Server DCs to your forest. For more information about supported functional levels, see [Forest and domain functional levels](../active-directory-functional-levels.md).
71 +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 DCs running an older forest functional level than the operating system supports, the installation is blocked. Those DCs must be removed and the forest functional level raised to a version that's supported before you add newer Windows Server DCs to your forest. For more information about supported functional levels, see [Forest and domain functional levels](../active-directory-functional-levels.md).
7272
7373 > [!NOTE]
7474 > No new forest or domain functional levels have been added since Windows Server 2016. Later operating system versions can and should be used for domain controllers. They use Windows Server 2016 as the most recent functional levels.
⋯ 49 unchanged lines
124124 ![Screenshot of the Deployment Configuration page of the Active Directory Domain Services Configuration Wizard showing the Add a domain controller to an existing forest option selected.](media/Upgrade-Domain-Controllers-to-Windows-Server-2016/upgrade5.png)
125125
126126 1. On the **Domain Controller options** screen, enter the **Directory Services Restore Mode (DSRM)** password and select **Next**.
127 −1. For the remainder of the screens, select **Next**.
127 +1. For the rest of the screens, select **Next**.
128128 1. On the **Prerequisite Check** screen, select **Install**. After the restart has completed, sign in again.
129129 1. On the earlier version of Windows Server, in **Server Manager**, under **Tools**, select **Active Directory Module for Windows PowerShell**.
130130
⋯ 24 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Oct 22:55 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current