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 functional level upgrade planning

This page's changes and edits · All guidance changes

Microsoft's edit ·

Updating to align with Active Directory Functional Levels

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit ea806f7 · +36 −30 lines · also on GitHub

⋯ 2 unchanged lines
33 title: Learn about upgrading your domain and forest functional levels in Active Directory Domain Services.
44 author: robinharwood
55 ms.author: wscontent
6 −ms.date: 05/29/2024
6 +ms.date: 07/15/2024
77 ms.topic: conceptual
88 ---
99
⋯ 1 unchanged line
1111
1212 >Applies to: Windows Server 2025 (preview), Windows Server 2022, Windows Server 2019, Windows Server 2016
1313
14 −Before you can raise domain and forest functional levels, you have to evaluate your current environment and identify the functional level requirement that best meets the needs of your organization. Assess your current environment by identifying the domains in your forest, the domain controllers that are located in each domain, the operating system and updates that each domain controller is running, and when you plan to upgrade the domain controllers. If you plan to retire a domain controller, make sure that you understand the full impact that doing so will have on your environment. In this article you learn about the process and prerequisites for upgrading your domain and forest functional levels in Active Directory Domain Services.
14 +In this article learn about the process for upgrading your domain and forest functional levels in Active Directory Domain Services.
1515
16 −The following circumstances might prevent you from upgrading Windows Server functional level:
16 +Before you can raise domain and forest functional levels, evaluate your current environment and identify your target functional level. Assess your current environment by identifying:
1717
18 −- Insufficient hardware
18 +- The domains in your forest
1919
20 −- A domain controller running an antivirus or backup programs that are incompatible with newer versions of Windows Server
20 +- The domain controllers that are located in each domain
2121
22 −- Use of a version-specific program that isn't compatible with newer versions of Windows Server
22 +- The operating system and updates that each domain controller is running
2323
24 −- The need to upgrade a program with the latest update
24 +- When you plan to upgrade the domain controllers.
2525
26 +If you plan to retire a domain controller, make sure that you understand the full impact that doing so will have on your environment.
27 +
28 +Consider the following items when assessing your current environment:
29 +
30 +- Your domain controllers meet or exceed the hardware requirements for the operating system that you plan to upgrade to. To learn more about hardware requirements, see [Perform a Feature Update of Windows Server](../../../get-started/perform-in-place-upgrade.md).
31 +
32 +- Your Active Directory domain is operational and free from replication errors. To learn more about replication errors, see [Diagnose Active Directory replication failures](/troubleshoot/windows-server/active-directory/diagnose-replication-failures).
33 +
34 +- Identify all your domain controllers hosting the Global Catalog (GC) and Flexible Single Master Operation (FSMO) roles. Create and verify backups of these Active Directory Domain Services domain controllers before making changes.
35 +
36 +- Check for any incompatible software or applications that might prevent you from upgrading to a newer version of Windows Server.
37 +
38 +- Check for removed features to make sure that none are being used. To learn more about removed features, see [Features removed or no longer developed starting with Windows Server 2025 (preview)](../../../get-started/removed-deprecated-features-windows-server-2025.md).
39 +
2640 Documenting this information can help you identify the steps to take to ensure that you have a fully functional Windows Server environment.
2741
28 −After you assess your current environment, you have to identify the functional level upgrade that applies to your organization. This article discusses the following options:
42 +After you assess your current environment, identify the target functional level upgrade. To learn more about the functional levels, see [Forest and Domain Functional Levels](../active-directory-functional-levels.md).
2943
44 +This article discusses the following upgrade options:
45 +
3046 - Upgrade to a Windows Server 2025 (preview) forest
47 +
3148 - Upgrade to a Windows Server 2016 forest
3249
3350 > [!IMPORTANT]
3451 > Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.
3552
36 −## Upgrading functional levels to Windows Server 2025
53 +## Upgrade functional levels to Windows Server 2025
3754
3855 In an environment consisting of only Windows Server 2025-based domain controllers, the functional levels default to Windows Server 2025. If your Active Directory Domain Services environment contains a mix of Windows Server releases, your functional levels might be set to a lower level.
3956
4057 To use all the forest-level and domain-level features in Windows Server 2025, you have to upgrade to the Windows Server 2025 forest and domain functional levels. To upgrade your domain controllers to Windows Server 2025, you must meet the following prerequisites:
4158
42 −- For new Active Directory forests, the minimum functional level that can be set is Windows Server 2016.
59 +- For new Active Directory forests, the minimum domain and forest functional level that can be set is Windows Server 2016.
4360
44 −- Existing domains must be at the 2016 functional level to promote a Windows Server 2025 domain controller.
61 +- Existing domains must be at the Windows Server 2016 domain and forest functional levels to promote a Windows Server 2025 domain controller.
4562
46 − You can upgrade the functional levels by using the following options:
63 +You can upgrade the functional levels by using the following options:
4764
48 −- Set up a new Active Directory domain with the new Domain Functional Level (DFL) and Forest Functional Level (FFL) when promoting the first Domain Controller for the new domain
65 +- Set up a new Active Directory domain with the new domain and forest functional levels when promoting the first Domain Controller for the new domain
4966
5067 - Introduce new Windows Server 2025 domain controllers into the forest, then retire or upgrade all domain controllers running an older version of Windows Server. After you've upgraded or retired all domain controllers running an older version of Windows Server, you can raise the domain and forest functional levels to Windows Server 2025.
5168
5269 - Perform a Feature Update of all existing domain controllers running an older version of Windows Server. To learn more about performing a Feature Update, see [Perform a Feature Update of Windows Server](../../../get-started/perform-in-place-upgrade.md). Then raise the domain and forest functional levels to Windows Server 2025.
5370
54 − > [!IMPORTANT]
55 − > A Windows Server 2025 domain controller can only be added to an existing domain that is running Windows Server 2016 Domain Functional Level or newer version. You must also ensure that all hardware and software requirements for Windows Server 2025 are met.
56 −
57 −## Upgrading functional levels in a Windows Server 2016 Active Directory forest
58 −
59 −In an environment that consisting of Windows Server 2016, 2019 and 2022-based domain controllers, the functional levels are set by default to the following level, and they remain at these levels until you raise them manually after an upgrade to Windows Server 2025 or later.
60 −
61 −- Windows Server 2016 domain functional level
71 +A Windows Server 2025 domain controller can only be added to an existing domain that is running Windows Server 2016 Domain Functional Level or newer version. You must also ensure that all hardware and software requirements for Windows Server 2025 are met.
6272
63 −- Windows Server 2016 forest functional level
73 +## Upgrade functional levels in a Windows Server 2016 Active Directory forest
6474
65 −> [!NOTE]
66 −> Windows Server 2019 and 2022 used Windows Server 2016 as the most recent functional levels.
75 +In an environment that consisting of Windows Server 2016, 2019 and 2022-based domain controllers, the functional levels are set by default to the Windows Server 2016 domain and forest functional level. The Windows Server 2016 domain and forest functional level is the most recent functional level for Windows Server 2019 and 2022. The functional level remains at these levels until you raise them manually after an upgrade to Windows Server 2025 or later.
6776
6877 To use all the forest-level and domain-level features in Windows Server 2016, you have to upgrade to the Windows Server 2016 forest and domain functional levels. To upgrade your domain controllers to Windows Server 2016, you must meet the following prerequisites:
6978
⋯ 3 unchanged lines
7382
7483 There are two upgrade options to choose from, as follows:
7584
76 −- Set up a new Active Directory domain with the new Domain Functional Level (DFL) and Forest Functional Level (FFL) when promoting the first Domain Controller for the new domain
85 +- Set up a new Active Directory domain with the new domain and forest functional levels when promoting the first Domain Controller for the new domain
7786
7887 - Introduce new Windows Server 2016, 2019 or 2022 domain controllers into the forest, then retire or upgrade all domain controllers running an older version of Windows Server. After you've upgraded or retired all domain controllers running an older version of Windows Server, you can raise the domain and forest functional levels to Windows Server 2016.
7988
8089 - Perform a Feature Update of all existing domain controllers running an older version of Windows Server. To learn more about performing a Feature Update, see [Perform a Feature Update of Windows Server](../../../get-started/perform-in-place-upgrade.md). Then raise the domain and forest functional levels to Windows Server 2016.
8190
82 − > [!IMPORTANT]
83 − > You must check for removed features prior to upgrade to make certain that none are being used. Also verify that all domain controllers are correctly replicated both before and after the upgrade. To learn more about removed features, see [Features Removed or Deprecated in Windows Server 2016](../../../get-started/removed-deprecated-features-windows-server-2016.md).
84 −
85 −## Upgrading functional levels in a previous versions of Windows Server
91 +## Upgrade functional levels in a previous version of Windows Server
8692
87 −If you are looking to identify functional levels for a previous version of Windows Server, see [Identifying your functional level upgrade](previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc754209(v=ws.10)).
93 +If you're looking to identify functional levels for a previous version of Windows Server, see [Identifying your functional level upgrade](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc754209(v=ws.10)).

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 10 Oct 07:36 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