Merge pull request #7642 from dknappettmsft/broken-links-fix

Fix broken links

Author: dknappettmsft

.openpublishing.redirection.remote.json

@@ -889,6 +889,11 @@
       "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
+    },
+    {
+      "source_path": "WindowsServerDocs/remote/remote-desktop-services/Tenant-on-premises-components.md",
+      "redirect_url": "/windows-server/remote/remote-desktop-services/desktop-hosting-reference-architecture",
+      "redirect_document_id": false
     }
   ]
 }

WindowsServerDocs/get-started/removed-deprecated-features-windows-server.md

@@ -12,7 +12,7 @@ ms.date: 09/24/2025
 Each release of Windows Server brings new features and improvements. Sometimes older features are removed to make room for better alternatives. This article details the features and functionalities removed or deprecated in Windows Server.
 
 > [!TIP]
-> You can get early access to Windows Server builds by joining the [Windows Insider Program for Business](https://insider.windows.com/for-business), which is a great way to test feature changes.
+> You can get early access to Windows Server builds by joining the [Windows Insider Program for Windows Server](https://www.microsoft.com/windowsinsider/for-business-getting-started-server), which is a great way to test feature changes.
 
 > [!NOTE]
 > Windows Server long-term servicing channel (LTSC) releases have a Fixed Lifecycle Policy that includes 5 years of mainstream support and 5 years of extended support for a total lifecycle of 10 years. To learn more, see:

WindowsServerDocs/identity/ad-ds/manage/troubleshoot/Troubleshooting-Active-Directory-Replication-Problems.md

@@ -63,13 +63,13 @@ If a domain controller running Windows 2000 Server has failed for longer than th
 2. Either forcefully remove Active Directory or reinstall the operating system.
 3. Remove the server metadata from Active Directory so that the server object can't be revived.
 
-You can use a script to clean up server metadata on most Windows operating systems. For information about using this script, see [Remove Active Directory Domain Controller Metadata](https://go.microsoft.com/fwlink/?LinkID=123599).
-
 By default, NTDS Settings objects that are deleted are revived automatically for a period of 14 days. Therefore, if you don't remove server metadata (use Ntdsutil or the script mentioned previously to perform metadata cleanup), the server metadata is reinstated in the directory, which prompts replication attempts to occur. In this case, errors will be logged persistently as a result of the inability to replicate with the missing domain controller.
 
+For more information about removing server metadata, see [Clean up Active Directory Domain Controller server metadata](../../deploy/ad-ds-metadata-cleanup.md).
+
 ## Root causes
 
-If you rule out intentional disconnections, hardware failures, and outdated Windows 2,000 domain controllers, the remainder of replication problems almost always have one of the following root causes:
+If you rule out intentional disconnections, hardware failures, and outdated Windows Server 2000 domain controllers, the remainder of replication problems almost always have one of the following root causes:
 
 - Network connectivity: The network connection might be unavailable, or network settings aren't configured properly.
 - Name resolution: DNS misconfigurations are a common cause of replication failures.

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

@@ -56,8 +56,6 @@
         href: Azure-services-and-considerations-for-desktop-hosting.md
       - name: Understanding the desktop hosting environment
         href: Understanding-the-desktop-hosting-environment.md    
-      - name: Tenant on-premises components
-        href: Tenant-on-premises-components.md  
   - name: Build and deploy
     href: rds-build-and-deploy.md
     items:

WindowsServerDocs/remote/remote-desktop-services/Tenant-on-premises-components.md

@@ -28,7 +28,7 @@ In order to use SMT with Windows Server, you must have a compatible processor. P
 
 For the purposes of this article, the descriptions of SMT and how it's used by Hyper-V apply equally to both Intel and AMD systems.
 
-- For more information on Intel HT Technology, see [Intel Hyper-Threading Technology](https://www.intel.com/content/www/us/en/architecture-and-technology/hyper-threading/hyper-threading-technology.html).
+- For more information on Intel HT Technology, see [Intel Hyper-Threading Technology](https://www.intel.com/content/www/us/en/gaming/resources/hyper-threading.html).
 - For more information on AMD SMT, see [AMD "Zen" Core Architecture](https://www.amd.com/en/technologies/zen-core.html).
 
 ### Understand how Hyper-V virtualizes processors