Skip to content

Commit 8c264fa

Browse files
Merge branch 'MicrosoftDocs:main' into main
2 parents 57b6847 + df14ca9 commit 8c264fa

902 files changed

Lines changed: 6326 additions & 13142 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.openpublishing.redirection.administration.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1329,6 +1329,11 @@
13291329
"source_path": "WindowsServerDocs/administration/windows-server-update-services/manage/wsus-messages-and-troubleshooting-tips.md",
13301330
"redirect_url": "/troubleshoot/windows-server/installing-updates-features-roles/wsus-messages-troubleshooting-tips",
13311331
"redirect_document_id": false
1332+
},
1333+
{
1334+
"source_path": "WindowsServerDocs/administration/manage-windows-server-old.md",
1335+
"redirect_url": "/windows-server/administration/manage-windows-server",
1336+
"redirect_document_id": false
13321337
}
13331338
]
13341339
}

.openpublishing.redirection.json

Lines changed: 520 additions & 0 deletions
Large diffs are not rendered by default.

.openpublishing.redirection.networking.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1279,6 +1279,21 @@
12791279
"source_path": "WindowsServerDocs/networking/sdn/deploy/Deploy-Network-Controller-using-Windows-powershell.md",
12801280
"redirect_url": "/azure/azure-local/deploy/sdn-express-23h2",
12811281
"redirect_document_id": false
1282+
},
1283+
{
1284+
"source_path": "WindowsServerDocs/networking/technologies/netsh/netsh-bridge.md",
1285+
"redirect_url": "/windows-server/administration/windows-commands/netsh-bridge",
1286+
"redirect_document_id": false
1287+
},
1288+
{
1289+
"source_path": "WindowsServerDocs/networking/technologies/netsh/netsh-interface-portproxy.md",
1290+
"redirect_url": "/windows-server/administration/windows-commands/netsh-interface",
1291+
"redirect_document_id": false
1292+
},
1293+
{
1294+
"source_path": "WindowsServerDocs/networking/technologies/netsh/netsh-mbn.md",
1295+
"redirect_url": "/windows-server/administration/windows-commands/netsh-mbn",
1296+
"redirect_document_id": false
12821297
}
12831298
]
12841299
}

.openpublishing.redirection.remote.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -884,6 +884,16 @@
884884
"source_path": "WindowsServerDocs/remote/remote-desktop-services/virtual-machine-recs.md",
885885
"redirect_url": "/windows-server/remote/remote-desktop-services/session-host-virtual-machine-sizing-guidelines",
886886
"redirect_document_id": true
887+
},
888+
{
889+
"source_path": "WindowsServerDocs/remote/remote-desktop-services/remote-desktop-services-overview.md",
890+
"redirect_url": "/windows-server/remote/remote-desktop-services/overview",
891+
"redirect_document_id": true
892+
},
893+
{
894+
"source_path": "WindowsServerDocs/remote/remote-desktop-services/Tenant-on-premises-components.md",
895+
"redirect_url": "/windows-server/remote/remote-desktop-services/desktop-hosting-reference-architecture",
896+
"redirect_document_id": false
887897
}
888898
]
889899
}

.openpublishing.redirection.virtualization.json

Lines changed: 555 additions & 0 deletions
Large diffs are not rendered by default.

CODEOWNERS

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616

1717
# Doc location
1818

19-
/WindowsServerDocs/security/tls/ @robinharwood @Xelu86
19+
/WindowsServerDocs/ @MicrosoftDocs/windowsserverdocs-admin
2020

2121
# Configuration
2222

WindowsServerDocs/administration/Get-started-with-Setup-and-Boot-Event-Collection.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@ title: Get started with Setup and Boot Event Collection
33
description: Setting up Setup and Boot Event Collection collectors and targets
44
ms.date: 10/16/2017
55
ms.topic: how-to
6-
ms.assetid: fc239aec-e719-47ea-92fc-d82a7247b3f8
76
author: robinharwood
87
ms.author: roharwoo
98
---

WindowsServerDocs/administration/OpenSSH/OpenSSH_KeyManagement.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Key-Based Authentication in OpenSSH for Windows
33
description: Find out about OpenSSH Server key-based authentication, generation, and deployment for Windows. See how to use built-in Windows tools or PowerShell to manage keys.
4-
ms.date: 06/30/2025
4+
ms.date: 10/03/2025
55
ms.topic: concept-article
66
ms.author: roharwoo
77
author: robinharwood
@@ -20,6 +20,9 @@ By comparison, Linux environments commonly use public/private key pairs to drive
2020

2121
This document provides an overview of how to use these tools on Windows to begin using key-based authentication with Secure Shell (SSH). If you're not familiar with SSH key management, we strongly recommend that you review [NIST document IR 7966](http://nvlpubs.nist.gov/nistpubs/ir/2015/NIST.IR.7966.pdf), titled _Security of Interactive and Automated Access Management Using Secure Shell (SSH)_.
2222

23+
> [!NOTE]
24+
> Windows OpenSSH doesn't support the `AuthorizedKeysCommand` and `AuthorizedKeysCommandUser` directives. Meaning you can't dynamically fetch SSH keys from Active Directory using these directives as you might on Linux system. For more information about the supported configuration options, see [OpenSSH Server configuration for Windows Server and Windows](openssh-server-configuration.md).
25+
2326
## Key pairs
2427

2528
Key pairs refer to the public and private key files that are used by certain authentication protocols.

WindowsServerDocs/administration/manage-windows-server-old.md

Lines changed: 0 additions & 109 deletions
This file was deleted.

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The virtual machine (VM) integration services include enlightened drivers for th
1717

1818
## Virtual processors
1919

20-
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).
20+
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).
2121

2222
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).
2323

@@ -51,7 +51,7 @@ The following are best practices for configuring a *client version* of Windows i
5151

5252
## Virtual NUMA
5353

54-
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).
54+
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).
5555

5656
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.
5757

@@ -67,7 +67,7 @@ For more info on Virtual NUMA, see [Hyper-V Virtual NUMA overview](/previous-ver
6767

6868
Here are some articles to help you learn more about Hyper-V.
6969

70-
- [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/plan/plan-hyper-v-scalability-in-windows-server.md)
70+
- [Plan for Hyper-V scalability in Windows Server](../../../../virtualization/hyper-v/maximum-scale-limits.md)
7171

7272
- [Hyper-V architecture](architecture.md)
7373

0 commit comments

Comments
 (0)