Merge pull request #7628 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-30 17:30 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.remote.json

@@ -884,6 +884,11 @@
       "source_path": "WindowsServerDocs/remote/remote-desktop-services/virtual-machine-recs.md",
       "redirect_url": "/windows-server/remote/remote-desktop-services/session-host-virtual-machine-sizing-guidelines",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "WindowsServerDocs/remote/remote-desktop-services/remote-desktop-services-overview.md",
+      "redirect_url": "/windows-server/remote/remote-desktop-services/overview",
+      "redirect_document_id": true
     }
   ]
 }

WindowsServerDocs/administration/windows-commands/nslookup-set-retry.md

@@ -11,7 +11,7 @@ ms.date: 10/16/2017
 
 
 
-If a reply isn't received within a certain amount of time, the time-out period is doubled, and the request is resent. This command sets the number of times a request is resent to a server for information, before giving up.
+This command sets the number of times a request is resent to a server for information, before giving up.
 
 > [!NOTE]
 > To change the length of time before the request times out, use the [nslookup set timeout](nslookup-set-timeout.md) command.
@@ -26,7 +26,7 @@ set retry=<number>
 
 | Parameter | Description |
 | ---------- | ---------- |
-| `<number>` | Specifies the new value for the number of retries. The default number of retries is **4**. |
+| `<number>` | Specifies the new value for the number of retries. The default number of retries is **1**. |
 | /? | Displays help at the command prompt. |
 | /help | Displays help at the command prompt. |
 

WindowsServerDocs/administration/windows-commands/nslookup-set-timeout.md

@@ -11,7 +11,7 @@ ms.date: 10/16/2017
 
 
 
-Changes the initial number of seconds to wait for a reply to a lookup request. If a reply isn't received within the specified amount of time, the time-out period is doubled, and the request is resent. Use the [nslookup set retry](nslookup-set-retry.md) command to determine the number of times to try to send the request.
+Changes the number of seconds to wait for a reply to a lookup request. Use the [nslookup set retry](nslookup-set-retry.md) command to determine the number of times to try to send the request.
 
 ## Syntax
 
@@ -23,16 +23,16 @@ set timeout=<number>
 
 | Parameter | Description |
 | ---------- | ---------- |
-| `<number>` | Specifies the number of seconds to wait for a reply. The default number of seconds to wait is **5**. |
+| `<number>` | Specifies the number of seconds to wait for a reply. The default number of seconds to wait is **2**. |
 | /? | Displays help at the command prompt. |
 | /help | Displays help at the command prompt. |
 
 ### Examples
 
-To set the timeout for getting a response to 2 seconds:
+To set the timeout for getting a response to 5 seconds:
 
 ```
-set timeout=2
+set timeout=5
 ```
 
 ## Related links

WindowsServerDocs/identity/ad-ds/active-directory-functional-levels.md

@@ -1,24 +1,43 @@
 ---
 title: Active Directory Domain Services Functional Levels
-description: Learn more about the different Active Directory domain and forest functional levels in Windows Server.
+description: Discover the capabilities of Active Directory Domain Services functional levels and learn how they impact domain controllers and Windows Server compatibility.
+#customer intent: As an IT admin, I want to understand the functional levels of Active Directory Domain Services so that I can determine the capabilities available in my environment.
 ms.topic: concept-article
 ms.author: roharwoo
 author: robinharwood
-ms.date: 10/03/2025
+ms.date: 10/30/2025
 ---
+
 # Active Directory Domain Services functional levels
 
 Functional levels determine the available Active Directory Domain Services (AD DS) domain or forest capabilities. They also determine which Windows Server operating systems you can run on domain controllers in the domain or forest. However, functional levels don't affect which operating systems you can run on workstations and member servers joined to the domain or forest. This article describes which functioning levels are compatible with which versions of Windows Server.
 
-When you deploy AD DS, set the domain and forest functional levels to the highest value that your environment can support in order to use as many AD DS features as possible. When you deploy a new forest, you need to set both the forest and domain functional levels. You can set the domain functional level to a value that's higher than the forest functional level, but you can't set the domain functional level to a value that's lower than the forest functional level.
+When you deploy AD DS, set the domain and forest functional levels to the highest value that your environment can support in order to use as many AD DS features as possible. When you deploy a new forest, you need to set both the forest and domain functional levels. You can set a domain functional level higher than the forest functional level. You can't set a domain functional level lower than the forest functional level.
+
+## Windows Server functional level interoperability
+
+The following interoperability matrix summarizes which Windows Server versions you can run as domain controllers for each currently supported AD DS forest and domain functional level.
 
-## Windows Server 2025 functional levels
+| Windows Server version (DC) | Windows Server 2025 functional level | Windows Server 2016 functional level | Windows Server 2012 R2 functional level |
+|-----------------------------|--------------------------------------|--------------------------------------|-----------------------------------------|
+| Windows Server 2025         | ✅ Supported                         | ✅ Supported                         | ❌ Not supported                        |
+| Windows Server 2022         | ❌ Not supported                     | ✅ Supported                         | ✅ Supported                            |
+| Windows Server 2019         | ❌ Not supported                     | ✅ Supported                         | ✅ Supported                            |
+| Windows Server 2016         | ❌ Not supported                     | ✅ Supported                         | ✅ Supported                            |
+| Windows Server 2012 R2      | ❌ Not supported                     | ❌ Not supported                     | ✅ Supported                            |
+
+✅ Supported means you can run a domain controller with that Windows Server release at the specified forest and domain functional level; ❌ Not supported means you cannot.
+
+> [!NOTE]
+> Windows Server 2019 and Windows Server 2022 use Windows Server 2016 as the most recent functional level. For earlier functional levels (for example Windows Server 2008 R2), see [Understanding Active Directory Domain Services (AD DS) Functional Levels](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754918(v=ws.10)).
+
+### Windows Server 2025 functional levels
 
 You can use the following operating systems as domain controllers (DCs) with the Windows Server 2025 forest and domain functional level.
 
 - Windows Server 2025
 
-### Windows Server 2025 forest and domain functional level features
+#### Windows Server 2025 forest and domain functional level features
 
 The Windows Server 2025 domain functional level includes all features available in earlier domain functional levels, but also has the following new features:
 
@@ -29,7 +48,7 @@ To learn more about new features, see [What's new in Windows Server 2025](../../
 > [!NOTE]
 > Windows Server 2019 and Windows Server 2022 use Windows Server 2016 as the most recent functional levels.
 
-## Windows Server 2016 functional levels
+### Windows Server 2016 functional levels
 
 You can use the following operating systems as domain controllers (DCs) with the Windows Server 2016 forest and domain functional level.
 
@@ -39,9 +58,9 @@ You can use the following operating systems as domain controllers (DCs) with the
 - Windows Server 2016
 
 > [!NOTE]
-> Domains must use DFSR as the engine to replicate SYSVOL. To learn more about migrating to DFSR, see [Streamlined Migration of FRS to DFSR SYSVOL](https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405). Windows Server 2016 is the last Windows Server release that supports the File Replication Service (FRS). See [Windows Server version 1709 no longer supports FRS](/troubleshoot/windows-server/networking/windows-server-version-1709-no-longer-supports-frs) for information on how to work around this issue.
+> Domains must use DFSR as the engine to replicate SYSVOL. To learn more about migrating to DFSR, see [Streamlined Migration of FRS to DFSR SYSVOL](https://techcommunity.microsoft.com/blog/filecab/streamlined-migration-of-frs-to-dfsr-sysvol/425405). Windows Server 2016 is the last Windows Server release that supports the File Replication Service (FRS). See [Windows Server version 1709 no longer supports FRS](/troubleshoot/windows-server/networking/windows-server-version-1709-no-longer-supports-frs) for information on how to work around this issue.
 
-### Windows Server 2016 forest and domain functional level features
+#### Windows Server 2016 forest and domain functional level features
 
 All default Active Directory features in earlier forest functional levels are available, plus the following features:
 
@@ -55,7 +74,7 @@ All default Active Directory features in earlier domain functional levels are av
 
     For more information, see [What's New in Kerberos Authentication](../../get-started/whats-new-in-windows-server-2016.md#kerberos-authentication).
 
-## Windows Server 2012 R2 functional levels
+### Windows Server 2012 R2 functional levels
 
 You can use the following operating systems as domain controllers (DCs) with the Windows Server 2012 R2 forest and domain functional level.
 
@@ -64,15 +83,15 @@ You can use the following operating systems as domain controllers (DCs) with the
 - Windows Server 2016
 - Windows Server 2012 R2
 
-### Windows Server 2012 R2 forest and domain functional level features
+#### Windows Server 2012 R2 forest and domain functional level features
 
 All default Active Directory features, all features from the Windows Server 2012 domain functional level, plus the following features:
 
 - DC-side protections for Protected Users. When Protected Users authenticate to a Windows Server 2012 R2 domain, they're no longer able to:
 
   - Authenticate with NTLM authentication.
 
-  - Use DES or RC4 cipher suites in Kerberos pre-authentication.
+  - Use DES or RC4 cipher suites in Kerberos preauthentication.
 
   - Be delegated with unconstrained or constrained delegation.
 
@@ -86,9 +105,9 @@ All default Active Directory features, all features from the Windows Server 2012
 
   - A new forest-based Active Directory object to be used to classify accounts for authentication policies or for authentication isolation. The new object can create a relationship between user, managed service, and computer accounts.
 
-## Functional and domain levels in previous versions of Windows Server
+### Functional and domain levels in previous versions of Windows Server
 
-If you want to identify functional levels for a previous version of Windows Server, see [Understanding Active Directory Domain Services (AD DS) Functional Levels](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754918(v=ws.10)).
+If you want to identify functional levels for a previous version of Windows Server, such as Windows Server 2008 R2, see [Understanding Active Directory Domain Services (AD DS) Functional Levels](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754918(v=ws.10)).
 
 ## Related content
 
@@ -97,5 +116,3 @@ If you want to identify functional levels for a previous version of Windows Serv
 - Use the PowerShell command [Set-ADDomainMode](/powershell/module/activedirectory/set-addomainmode) to raise the domain functional level.
 
 - To learn more about raising the domain and forest functional levels, see [How to raise Active Directory domain and forest functional levels](/troubleshoot/windows-server/active-directory/raise-active-directory-domain-forest-functional-levels).
-
-

WindowsServerDocs/remote/remote-desktop-services/TOC.yml

@@ -4,7 +4,7 @@
   - name: Get started
     items:
     - name: Remote Desktop Services overview
-      href: remote-desktop-services-overview.md
+      href: overview.md
     - name: Create virtual machines for Remote Desktop
       href: Create-virtual-machines-for-Remote-Desktop.md
     - name: Supported configurations for RDS