Merge pull request #7599 from MicrosoftDocs/main

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

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

.openpublishing.redirection.virtualization.json

@@ -1064,6 +1064,11 @@
       "source_path": "WindowsServerDocs/virtualization/hyper-v/best-practices-analyzer/Windows-Vista-should-be-configured-with-the-recommended-amount-of-memory.md",
       "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2016/virtualization/hyper-v/best-practices-analyzer/windows-vista-should-be-configured-with-the-recommended-amount-of-memory",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md",
+      "redirect_url": "/windows-server/virtualization/hyper-v/maximum-scale-limits",
+      "redirect_document_id": true
     }
   ]
 }

WindowsServerDocs/administration/performance-tuning/role/hyper-v-server/processor-performance.md

@@ -17,7 +17,7 @@ The virtual machine (VM) integration services include enlightened drivers for th
 
 ## Virtual processors
 
-Assess your workload to determine the processor requirements to avoid under or over provisioning. Use the results of your assessment to configure number of virtual processors required. Increase the number of virtual processors if the VM requires more processing resources under peak load. To learn more about the maximum configurable components in Hyper-V, see [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md).
+Assess your workload to determine the processor requirements to avoid under or over provisioning. Use the results of your assessment to configure number of virtual processors required. Increase the number of virtual processors if the VM requires more processing resources under peak load. To learn more about the maximum configurable components in Hyper-V, see [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/maximum-scale-limits.md).
 
 When using Simultaneous multithreading (SMT), we recommended using virtual processors in multiples of two. Most modern AMD and Intel based systems have SMT enabled, where enabled we recommended configuring virtual machines to have an even number of virtual processors. To learn more about SMT, see [Manage Hyper-V hypervisor scheduler types](../../../../virtualization/hyper-v/manage/manage-hyper-v-scheduler-types.md).
 
@@ -51,7 +51,7 @@ The following are best practices for configuring a *client version* of Windows i
 
 ## Virtual NUMA
 
-Hyper-V in Windows Server expands VM scale limits to enable virtualizing large scale-up workloads. When you create large VMs, memory from multiple NUMA nodes on the host system are typically used. In that type of VM configuration, if you don't allocate virtual processors and memory from the same NUMA node, workloads might have poor performance. Performance is negatively affected because workloads can't take advantage of the NUMA optimizations. To learn more about the maximum configurable components in Hyper-V, see [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md).
+Hyper-V in Windows Server expands VM scale limits to enable virtualizing large scale-up workloads. When you create large VMs, memory from multiple NUMA nodes on the host system are typically used. In that type of VM configuration, if you don't allocate virtual processors and memory from the same NUMA node, workloads might have poor performance. Performance is negatively affected because workloads can't take advantage of the NUMA optimizations. To learn more about the maximum configurable components in Hyper-V, see [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/maximum-scale-limits.md).
 
 In Windows Server, Hyper-V presents a Virtual NUMA topology to VMs. By default, this Virtual NUMA topology is optimized to match the NUMA topology of the underlying host computer. Exposing a Virtual NUMA topology into a VM lets the guest operating system, and any NUMA-aware applications running within it, take advantage of the NUMA performance optimizations, just as they would when running on a physical computer.
 
@@ -67,7 +67,7 @@ For more info on Virtual NUMA, see [Hyper-V Virtual NUMA overview](/previous-ver
 
 Here are some articles to help you learn more about Hyper-V.
 
-- [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md)
+- [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/maximum-scale-limits.md)
 
 - [Hyper-V architecture](architecture.md)
 

WindowsServerDocs/administration/windows-commands/forfiles.md

@@ -25,7 +25,7 @@ forfiles [/P pathname] [/M searchmask] [/S] [/C command] [/D [+ | -] [{<date> |
 | /M `<searchmask>` | Searches files according to the specified search mask. The default searchmask is `*`. |
 | /S | Instructs the **forfiles** command to search in subdirectories recursively. |
 | /C `<command>` | Runs the specified command on each file. Command strings should be wrapped in double quotes. The default command is `"cmd /c echo @file"`. |
-| /D `[{+\|-}][{<date> | <days>}]` | Selects files with a last modified date within the specified time frame:<ul><li>Selects files with a last modified date later than or equal to (**+**) or earlier than or equal to (**-**) the specified date, where *date* is in the format MM/DD/YYYY.</li><li>Selects files with a last modified date later than or equal to (**+**) the current date plus the number of days specified, or earlier than or equal to (**-**) the current date minus the number of days specified.</li><li>Valid values for *days* include any number in the range 0-32,768. If no sign is specified, **+** is used by default.</li></ul> |
+| /D `[{+\|-}][{<date> | <days>}]` | Selects files with a last modified date within the specified time frame:<ul><li>Selects files with a last modified date later than or equal to (**+**) or earlier than or equal to (**-**) the specified date, where *date* is in the same regional format as your Windows device, for example MM/DD/YYYY for English (United States).</li><li>Selects files with a last modified date later than or equal to (**+**) the current date plus the number of days specified, or earlier than or equal to (**-**) the current date minus the number of days specified.</li><li>Valid values for *days* include any number in the range 0-32,768. If no sign is specified, **+** is used by default.</li></ul> |
 | /? | Displays the help text in the cmd window. |
 
 #### Remarks

WindowsServerDocs/administration/windows-commands/ftp.md

@@ -4,7 +4,7 @@ description: Reference article for the ftp command, which transfers files to and
 ms.topic: reference
 ms.author: alalve
 author: xelu86
-ms.date: 10/16/2017
+ms.date: 10/17/2025
 ---
 
 # ftp
@@ -34,7 +34,7 @@ ftp [-v] [-d] [-i] [-n] [-g] [-s:<filename>] [-a] [-A] [-x:<sendbuffer>] [-r:<re
 | -x:`<sendbuffer> `| Overrides the default SO_SNDBUF size of 8192. |
 | -r:`<recvbuffer>` | Overrides the default SO_RCVBUF size of 8192. |
 | -b:`<asyncbuffers>` | Overrides the default async buffer count of 3. |
-| -w:`<windowssize>` | Specifies the size of the transfer buffer. The default window size is 4096 bytes. |
+| -w:`<windowsize>` | Specifies the size of the transfer buffer. The default window size is 65535 bytes. |
 | `<host>` | Specifies the computer name, IP address, or IPv6 address of the ftp server to which to connect. The host name or address, if specified, must be the last parameter on the line. |
 | -? | Displays help at the command prompt. |
 

WindowsServerDocs/docfx.json

@@ -678,7 +678,7 @@
           "✅ <a href=\"https://learn.microsoft.com/windows/release-health/supported-versions-windows-client\" target=\"_blank\">Windows 10</a>",
           "✅ <a href=\"https://learn.microsoft.com/azure/azure-local/release-information-23h2\" target=\"_blank\">Azure Local 2311.2 and later</a>"
         ],
-        "virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md": [
+        "virtualization/hyper-v/maximum-scale-limits.md": [
           "✅ <a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2025</a>",
           "✅ <a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2022</a>",
           "✅ <a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2019</a>",

WindowsServerDocs/get-started/whats-new-in-windows-server-2016.md

@@ -58,7 +58,7 @@ Hyper-V network virtualization (HNV) is a fundamental building block of Microsof
 
 - Linux OSs running on generation 2 VMs can now boot with the Secure Boot option enabled. The OSs that support Secure Boot on Windows Server 2016 hosts include Ubuntu 14.04 and later, SUSE Linux Enterprise Server 12 and later, Red Hat Enterprise Linux 7.0 and later, and CentOS 7.0 and later. Before you boot the VM for the first time, you must configure it to use the Microsoft UEFI Certificate Authority in either Hyper-V Manager, Virtual Machine Manager, or by running the [Set-VMFirmware](/powershell/module/hyper-v/set-vmfirmware) cmdlet in PowerShell.
 
-- Generation 2 VMs and Hyper-V hosts can now use more memory and virtual processors. You can also configure hosts with more memory and virtual processors than previous versions. These changes support scenarios such as running large in-memory databases for online transaction processing (OLTP) and data warehousing (DW) for e-commerce. For more information, see [Windows Server 2016 Hyper-V large-scale VM performance for in-memory transaction processing](https://www.microsoft.com/windows-server/blog/2016/09/28/windows-server-2016-hyper-v-large-scale-vm-performance-for-in-memory-transaction-processing/). To earn more about version compatibility and supported maximum configurations, see [Upgrade virtual machine version in Hyper-V on Windows or Windows Server](../virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server.md) and [Plan for Hyper-V scalability in Windows Server](../virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md).
+- Generation 2 VMs and Hyper-V hosts can now use more memory and virtual processors. You can also configure hosts with more memory and virtual processors than previous versions. These changes support scenarios such as running large in-memory databases for online transaction processing (OLTP) and data warehousing (DW) for e-commerce. For more information, see [Windows Server 2016 Hyper-V large-scale VM performance for in-memory transaction processing](https://www.microsoft.com/windows-server/blog/2016/09/28/windows-server-2016-hyper-v-large-scale-vm-performance-for-in-memory-transaction-processing/). To earn more about version compatibility and supported maximum configurations, see [Upgrade virtual machine version in Hyper-V on Windows or Windows Server](../virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server.md) and [Plan for Hyper-V scalability in Windows Server](../virtualization/hyper-v/maximum-scale-limits.md).
 
 - The Nested Virtualization feature lets you use a VM as a Hyper-V host and create VMs within the virtualized host. You can use this feature to build development and test environments running at least Windows Server 2016 or Windows 10 with an Intel VT-x capable processor. For more information, see [What is Nested Virtualization?](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization).
 

WindowsServerDocs/get-started/whats-new-windows-server-2025.md

@@ -379,7 +379,7 @@ This approach reduces the time, complexity, and errors associated with host netw
 
 With Windows Server 2025, Hyper-V now supports up to 4 petabytes of memory and 2,048 logical processors per host. This increase allows for greater scalability and performance for virtualized workloads.
 
-Windows Server 2025 also supports up to 240 TB of memory and 2,048 virtual processors for generation 2 VMs, providing increased flexibility for running large workloads. To learn more, see [Plan for Hyper-V scalability in Windows Server](../virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md).
+Windows Server 2025 also supports up to 240 TB of memory and 2,048 virtual processors for generation 2 VMs, providing increased flexibility for running large workloads. To learn more, see [Plan for Hyper-V scalability in Windows Server](../virtualization/hyper-v/maximum-scale-limits.md).
 
 ### Workgroup clusters
 

WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md

@@ -13,7 +13,7 @@ Hyper-V supports several versions of Windows Server, Windows, and Linux distribu
 
 Some operating systems have the integration services built-in. Others require that you install or upgrade integration services as a separate step after you set up the operating system in the virtual machine. For more information, see the following sections and [Integration Services](/virtualization/hyper-v-on-windows/reference/integration-services).
 
-Guest operating systems configurable components are confined based on the hosting operating system. To learn more about the maximum configurable components in Hyper-V, see [Plan for Hyper-V scalability in Windows Server](plan/plan-hyper-v-scalability-in-windows-server.md).
+Guest operating systems configurable components are confined based on the hosting operating system. To learn more about the maximum configurable components in Hyper-V, see [Plan for Hyper-V scalability in Windows Server](maximum-scale-limits.md).
 
 ## Supported Windows Server guest operating systems
 

WindowsServerDocs/virtualization/hyper-v/host-hardware-requirements.md

@@ -18,7 +18,7 @@ Then review the [Windows Server catalog](https://www.windowsservercatalog.com/).
 
 If you're already using Hyper-V, it's likely that you can use your existing hardware. The general hardware requirements have changed minimally from  Windows Server 2012 R2, but you need newer hardware to use shielded virtual machines or discrete device assignment. Those features rely on specific hardware support, as described later in this article. Other than that, the main difference in hardware is that second-level address translation (SLAT) is now required instead of recommended.
 
-For details about maximum supported configurations for Hyper-V, such as the number of running virtual machines, see [Plan for Hyper-V scalability in Windows Server](../hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md). The list of operating systems you can run in your virtual machines is covered in [Supported Windows guest operating systems for Hyper-V on Windows Server](Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md).
+For details about maximum supported configurations for Hyper-V, such as the number of running virtual machines, see [Plan for Hyper-V scalability in Windows Server](../hyper-v/maximum-scale-limits.md). The list of operating systems you can run in your virtual machines is covered in [Supported Windows guest operating systems for Hyper-V on Windows Server](Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md).
 
 ::: zone-end