AD domain and forest functional levels
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit ece93ed · +5 −2 lines · also on GitHub
⋯ 69 unchanged lines
7070
7171
1. Open PowerShell as an administrator.
7272
73
−1. Run the following command to view the current domain functional level, replacing `<domain>` with the domain name.
73
+1. Run the following command to view the current domain functional levels of all domains in the forest.
7474
7575
```powershell
76
− Get-ADDomain -Identity <domain> | Select-Object DomainMode
76
+ Get-ADForest | Select-Object -ExpandProperty Domains | ForEach-Object { Get-ADDomain $_ } | Select-Object Name, DomainMode
7777
```
7878
7979
1. Run the following command to view the current forest functional level, replacing `<forest>` with the forest name.
⋯ 12 unchanged lines
9292
9393
> [!WARNING]
9494
> Changes to the domain and forest functional levels are irreversible. In order to undo the change, you must perform a forest recovery to revert to an earlier point of time.
95
+
96
+> [!IMPORTANT]
97
+> If all domain controllers in all domains in the forest are running Windows Server 2025, it isn't necessary to raise individual domain functional levels manually as raising the forest functional level to Windows Server 2025 automatically raises the domain functional level of all domains in the forest to Windows Server 2025.
9598
9699
### [Desktop](#tab/desktop)
97100
⋯ 53 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 10 Oct 02:30 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.