Merge pull request #9925 from v-tappelgate/AB#7892-Cleanup

AB#7892 cleanup

Author: v-tappelgate

support/windows-client/windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md

@@ -55,21 +55,17 @@ Use this cmdlet when running a scheduled task that fails with an error, or when
 
 Use this cmdlet when having network printing errors occur, when the client fails to print, or when the printing is slow.
 
-## 
-
 > [!NOTE]
 > If the printing is slow, add the parameter `-procmon` to the end of the cmdlet.
 
 ## Scenario: Windows Remote Management (WinRM)
 
 #### TSS cmdlet
 
-
 ```powershell
 .\TSS.ps1 -Scenario UEX_WinRM
 ```
 
 #### TSS cmdlet description
 
 Use this command to collect data for any WinRM scenario. Run on both source and destination 
-

support/windows-server/setup-upgrade-and-drivers/error-0x80070003-during-process-drivers-for-migration.md

@@ -113,7 +113,7 @@ Such folders shouldn't be empty.
    > [!NOTE]  
    >
    > - The `Get-ChildItem -Directory` cmdlet selects only subfolders. Therefore, the robocopy operation skips root-level files, such as .mum and .manifest files.
-   > - For more information about the `Get-ChildItem` cmdlet and its options, see [Get-ChildItem](/powershell/module/microsoft.powershell.management/get-childitem?view=powershell-7.5).
+   > - For more information about the `Get-ChildItem` cmdlet and its options, see [Get-ChildItem](/powershell/module/microsoft.powershell.management/get-childitem).
    > - For more information about the `robocopy` command and its switches, see [robocopy](/windows-server/administration/windows-commands/robocopy).
 
 1. To copy the subfolders and log the operation, run the following command:

support/windows-server/virtualization/windows-11-vm-wont-start-after-migrating-from-vmware-to-hyper-v.md

@@ -30,14 +30,14 @@ Windows 11 requires a TPM for Secure Boot and security compliance. The following
 
 ## Solution
 
-For best results when you migrate a VM, we recommend that you follow the procedures that are provided in [Convert a VMware VM to Hyper-V in the VMM fabric](/system-center/vmm/vm-convert-vmware?view=sc-vmm-2025). That article provides detailed steps for how to prepare to migrate a VM and the migration process itself.
+For best results when you migrate a VM, we recommend that you follow the procedures that are provided in [Convert a VMware VM to Hyper-V in the VMM fabric](/system-center/vmm/vm-convert-vmware). That article provides detailed steps for how to prepare to migrate a VM and the migration process itself.
 
 The following procedure provides steps that are specific to VMs that run Windows 11 or a later version.
 
 > [!IMPORTANT]  
 >
 > - Make sure that you have administrative access to both the VMware and Hyper-V environments.
-> - Make sure that System Center Virtual Machine Manager (SCVMM) is installed and configured to manage and migrate the VM. For more information, see the "Start by bringing your vCenter server and the source ESXi hosts under SCVMM management" section of [Convert a VMware VM to Hyper-V in the VMM fabric](/system-center/vmm/vm-convert-vmware?view=sc-vmm-2025#start-by-bringing-your-vcenter-server-and-the-source-esxi-hosts-under-scvmm-management).
+> - Make sure that System Center Virtual Machine Manager (SCVMM) is installed and configured to manage and migrate the VM. For more information, see the "Start by bringing your vCenter server and the source ESXi hosts under SCVMM management" section of [Convert a VMware VM to Hyper-V in the VMM fabric](/system-center/vmm/vm-convert-vmware#start-by-bringing-your-vcenter-server-and-the-source-esxi-hosts-under-scvmm-management).
 > - Verify that the edition of Windows 11 that you're using is compatible with Hyper-V requirements, including TPM support.
 
 To configure the security settings for the migrated VM, follow these steps: