Update

Author: Simonx Xu

support/windows-server/active-directory/manually-remove-lingering-objects.md

@@ -14,7 +14,7 @@ appliesto:
 ---
 # Manually remove lingering objects on outdated replication partners
 
-This article helps manually remove [lingering objects](information-lingering-objects.md#summary) after you bring an outdated domain controller (DC) or global catalog server back online. In many cases, you can clean up lingering objects using the `repadmin /removelingeringobjects` command or tools like [Lingering Object Liquidator](lingering-object-liquidator-tool.md). However, these facilities don't work if you have [abandoned objects](https://support.microsoft.com/topic/attributes-that-contain-stale-or-bad-data-cause-exchange-offline-address-book-oab-generation-failures-and-event-ids-9126-9330-and-9339-together-with-stop-error-code-8004010e-occur-d505154b-f51f-6604-436b-e30fe4e486d9).
+This article helps manually remove [lingering objects](information-lingering-objects.md#summary) after you bring an outdated domain controller (DC) or global catalog server back online. In many cases, you can clean up lingering objects using the `repadmin /removelingeringobjects` command or tools like [Lingering Object Liquidator](lingering-object-liquidator-tool.md). However, these facilities don't work if you have abandoned objects.
 
 _Original KB number:_   314282
 

support/windows-server/active-directory/windows-time-service-event-ids-24-29-38.md

@@ -19,7 +19,7 @@ This article provides a solution to an issue where you receive the Windows Time
 _Original KB number:_   976924
 
 > [!NOTE]  
-> If you are a Small Business customer, find additional troubleshooting and learning resources at the [Support for Small Business](https://smallbusiness.support.microsoft.com) site.
+> If you are a Small Business customer, find additional troubleshooting and learning resources at the [Support for Small Business](https://support.microsoft.com/smallbusiness) site.
 
 ## Symptoms
 

support/windows-server/backup-and-storage/support-policy-4k-sector-hard-drives.md

@@ -103,7 +103,7 @@ The following are known compatibility issues that may occur when you use large-s
 
 - On Windows 7 and Windows 2008 R2, installation will fail with an error **Windows Setup could not configure Windows on this computer's hardware**. This issue occurs under the conditions that are outlined in the following article:
 
-  ["Windows Setup could not configure Windows on this computer's hardware" installation error on a Windows 7 or Windows Server 2008 R2 computer](https://support.microsoft.com/help/2466753).
+  ["Windows Setup could not configure Windows on this computer's hardware" installation error on a Windows 7 or Windows Server 2008 R2 computer](https://support.microsoft.com/topic/0db2c9ac-0343-75d9-50a1-d4922029ac2a).
 
 - If you're using a logical sector drive of a size other than 512 bytes, Windows system image backup and restore operations may fail. And you receive the following error message:
 

support/windows-server/high-availability/microsoft-support-policy-failover-clusters.md

@@ -95,6 +95,4 @@ For more information about failover clustering, see [Failover Clustering Overvie
 
 For more information about the Microsoft support policy for earlier operating systems, see:
 
-- [309395](https://support.microsoft.com/help/309395) The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
-
-- [943984](https://support.microsoft.com/help/943984) The Microsoft Support Policy for Windows Server 2008 or Windows Server 2008 R2 Failover Clusters
+- [309395](https://support.microsoft.com/topic/a254227b-925b-d68f-9e29-d2cc17087759) The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog