Merge branch 'main' of https://github.com/MicrosoftDocs/windowsserverdocs-pr into robinharwood-campus-cluster-how-to

Author: robinharwood

.openpublishing.redirection.get-started.json

@@ -464,6 +464,21 @@
       "source_path": "WindowsServerDocs/get-started/get-started-with-windows-server.md",
       "redirect_url": "/windows-server/get-started/overview",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "WindowsServerDocs/get-started/perform-in-place-upgrade.md",
+      "redirect_url": "/windows-server/get-started/upgrade-in-place",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "WindowsServerDocs/get-started/manage-feature-updates-group-policy.md",
+      "redirect_url": "/windows-server/get-started/upgrade-in-place",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "WindowsServerDocs/get-started/upgrade-overview.md",
+      "redirect_url": "/windows-server/get-started/install-upgrade-migrate",
+      "redirect_document_id": true
     }
   ]
 }

.openpublishing.redirection.manage.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "WindowsServerDocs/manage/windows-admin-center/use/migrate-vmware-to-hyper-v.md",
+      "redirect_url": "/windows-server/manage/windows-admin-center/use/vm-conversion-extension-overview",
+      "redirect_document_id": true
+    },
     {
       "source_path": "WindowsServerDocs/management/get-started-with-smt.md",
       "redirect_url": "https://techcommunity.microsoft.com/t5/windows-admin-center-blog/bg-p/Windows-Admin-Center-Blog",

Contributor-guide/metadata-requirements-for-articles.md

@@ -3,7 +3,7 @@ title: Add the required metadata tags to your Windows Server-related article
 description: A list of the information you must add as metadata tags to the top of your Windows Server-related articles. The required tags are subject to change, based on both your reporting and team requirements.
 author: eross-msft
 ms.author: roharwoo
-ms.date: 05/06/2019
+ms.date: 05/07/2019
 ---
 
 # Add the required metadata tags to your Windows Server-related article

WindowsServerDocs/administration/OpenSSH/OpenSSH_Install_FirstUse.md

@@ -57,7 +57,7 @@ To enable SSHD using Server Manager:
 
 1. In the **Properties** window, locate **Remote SSH Access**.
 
-1. Select **Disabled** to enable the OpenSSH service.
+1. Select **Enabled** to enable the OpenSSH service.
 
 > [!NOTE]
 > If you need to allow or restrict specific users or groups from using OpenSSH for remote access, add them to the **OpenSSH Users** user group.

WindowsServerDocs/administration/OpenSSH/OpenSSH_KeyManagement.md

@@ -161,7 +161,7 @@ $authorizedKey = Get-Content -Path $env:USERPROFILE\.ssh\id_ecdsa.pub
 $remotePowershell = "powershell New-Item -Force -ItemType Directory -Path $env:USERPROFILE\.ssh; Add-Content -Force -Path $env:USERPROFILE\.ssh\authorized_keys -Value '$authorizedKey'"
 
 # Connect to your server and run the PowerShell command by using the $remotePowerShell variable.
-ssh username@domain1@contoso.com $remotePowershell
+ssh username@domain@hostname $remotePowershell
 ```
 
 ### Administrative user
@@ -178,16 +178,16 @@ You can use the following code to copy the public key to the server and configur
 $authorizedKey = Get-Content -Path $env:USERPROFILE\.ssh\id_ecdsa.pub
 
 # Generate the PowerShell command to run remotely that copies the public key file generated previously on your client to the authorized_keys file on your server.
-$remotePowershell = "powershell Add-Content -Force -Path $env:ProgramData\ssh\administrators_authorized_keys -Value '''$authorizedKey''';icacls.exe ""$env:ProgramData\ssh\administrators_authorized_keys"" /inheritance:r /grant ""Administrators:F"" /grant ""SYSTEM:F"""
+$remotePowershell = "powershell Add-Content -Force -Path $env:ProgramData\ssh\administrators_authorized_keys -Value '$authorizedKey';icacls.exe ""$env:ProgramData\ssh\administrators_authorized_keys"" /inheritance:r /grant ""Administrators:F"" /grant ""SYSTEM:F"""
 
 # Connect to your server and run the PowerShell command by using the $remotePowerShell variable.
-ssh username@domain1@contoso.com $remotePowershell
+ssh username@domain@hostname $remotePowershell
 ```
 
 For non-English localized versions of the operating system, the script needs to be modified to reflect group names accordingly. To prevent errors that can occur when you grant permissions to group names, you can use the security identifier (SID) in place of the group name. You can retrieve the SID by running `Get-LocalGroup | Select-Object Name, SID`. When you use the SID in place of the group name, it must be preceded by an asterisk (__\*__). In the following example, the __Administrators__ group uses the SID `S-1-5-32-544`:
 
 ```powershell
-$remotePowershell = "powershell Add-Content -Force -Path $env:ProgramData\ssh\administrators_authorized_keys -Value '''$authorizedKey''';icacls.exe ""$env:ProgramData\ssh\administrators_authorized_keys"" /inheritance:r /grant ""*S-1-5-32-544:F"" /grant ""SYSTEM:F"""
+$remotePowershell = "powershell Add-Content -Force -Path $env:ProgramData\ssh\administrators_authorized_keys -Value '$authorizedKey';icacls.exe ""$env:ProgramData\ssh\administrators_authorized_keys"" /inheritance:r /grant ""*S-1-5-32-544:F"" /grant ""SYSTEM:F"""
 ```
 
 These steps complete the configuration required to use key-based authentication with OpenSSH on Windows.

WindowsServerDocs/administration/azure.md

@@ -1,8 +1,8 @@
 ---
 title: Windows Server and Azure Management
 description: Learn how Microsoft Azure can extend Windows Server Management
-author: dknappettmsft
-ms.author: daknappe
+author: robinharwood
+ms.author: roharwoo
 ms.reviewer: rclaus
 ms.topic: overview
 ms.date: 02/27/2022

WindowsServerDocs/administration/manage-windows-server.yml

@@ -7,8 +7,8 @@ metadata:
   title: Windows Server Management documentation
   description: Learn about tools, recommendations and guidance on managing Windows Server.
   ms.topic: landing-page # Required
-  author: dknappettmsft
-  ms.author: daknappe
+  author: robinharwood
+  ms.author: roharwoo
   ms.date: 02/25/2022
   ms.service: windows-server
 

WindowsServerDocs/administration/performance-tuning/role/file-server/index.md

@@ -2,8 +2,8 @@
 title: Performance tuning for file servers
 description: Performance tuning for file servers running Windows Server
 ms.topic: best-practice
-author: dknappettmsft
-ms.author: daknappe
+author: robinharwood
+ms.author: roharwoo
 ms.date: 02/24/2025
 audience: Admin
 ---

WindowsServerDocs/administration/performance-tuning/role/file-server/smb-file-server.md

@@ -2,8 +2,8 @@
 title: Performance Tuning for SMB File Servers
 description: Performance Tuning for SMB File Servers in Windows.
 ms.topic: best-practice
-author: dknappettmsft
-ms.author: daknappe
+author: robinharwood
+ms.author: roharwoo
 ms.date: 01/16/2025
 ---
 

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

@@ -190,7 +190,7 @@ We recommend you use the fixed file type when you need optimal resiliency and pe
 
 When you create a dynamic VHD file, the system allocates space for it on-demand. Blocks in the file start as allocated blocks, and no space in the file backs the unallocated blocks. When a block receives its first write, the virtualization stack then must allocate space for the block in the VHD file, then update the metadata. This allocation increases the number of disk I/Os required for the write, increasing CPU usage. Reads and writes to existing blocks incur disk access and CPU overhead when looking up the blocks' mapping in the metadata.
 
-If you're using a VHDX file, we recommend you use the dynamic file type when you aren't actively monitoring storage on the hosting volume. Make sure you have enough disk space when expanding the VHD file at runtime.
+If you're using a VHDX file, use the dynamic file type when you actively monitor storage on the hosting volume. Make sure you have enough disk space when expanding the VHD file at runtime.
 
 ### Differencing file type