Merging changes synced from https://github.com/MicrosoftDocs/SupportArticles-docs-pr (branch live)

Learn Build Service GitHub App · Learn Build Service GitHub App · commit d716ceed5ed2 · 2025-03-28T09:01:07.000Z
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -13207,6 +13207,10 @@
     {
       "source_path": "support/windows-server/active-directory/remove-orphaned-domains.md",
       "redirect_url": "/troubleshoot/windows-server/windows-security/remove-orphaned-domains"
+    },
+    {
+      "source_path": "support/windows-server/remote/error-when-connecting-terminal-server.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-server/error-when-connecting-terminal-server"
     }
   ]
 }
diff --git a/support/azure/virtual-machines/linux/support-linux-open-source-technology.md b/support/azure/virtual-machines/linux/support-linux-open-source-technology.md
@@ -4,7 +4,7 @@ description: Describes support for Linux distributions and open-source technolog
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
 ms.topic: article
-ms.date: 05/31/2024
+ms.date: 03/28/2025
 ms.reviewer: patcatun, clausw, divargas, rondom, azurevmlnxcic, v-weizhu
 ---
 
@@ -34,7 +34,7 @@ Microsoft Azure supports the [Linux operating system](https://azure.microsoft.co
 
 Microsoft Support provides assistance for the Azure platform or services. Microsoft also provides commercially viable support for Linux. A support plan is required to receive Microsoft Support.
 
-- In Azure Marketplace, Linux distributions are available. Microsoft assists customers for Linux support but may require customers to engage with Linux vendors for collaboration. Vendors may have to provide distribution-specific fixes.
+- Azure Marketplace offers various Linux distributions. Microsoft provides support for Linux customers, but they might need to work with specific Linux vendors for further assistance. These vendors might be required to deliver distribution-specific fixes.
 - In Azure Marketplace, you may select a highly customized Linux image, such as a firewall appliance. Microsoft provides assistance for these images, but the Linux vendor must be engaged to troubleshoot specific system-related problems. Microsoft may collaborate with the vendor for those issues.
 - Microsoft Support doesn't assist customers for basic Linux administration, design, architecture, or deployment of applications or solutions on Azure.
 - The ability to customize Linux is one of the hallmarks of the operating system. We encourage you to use a Linux solution that benefits your organization. However, the Linux vendor may not support some modifications, such as custom kernels or modules. For vendor support, you may be required to use stock kernels or libraries for your image.
diff --git a/support/azure/virtual-machines/windows/toc.yml b/support/azure/virtual-machines/windows/toc.yml
diff --git a/support/windows-client/active-directory/w32time-not-start-on-workgroup.md b/support/windows-client/active-directory/w32time-not-start-on-workgroup.md
@@ -14,12 +14,12 @@ ms.custom:
 
 This article provides workarounds for an issue where the Windows Time service doesn't automatically start in a stand-alone environment.
 
-_Applies to:_ &nbsp; Windows 7 Service Pack 1, Windows Server 2012 R2  
+_Applies to:_ &nbsp; Windows Server (All supported versions), Windows client (All supported versions)  
 _Original KB number:_ &nbsp; 2385818
 
 ## Symptoms
 
-On a workgroup computer that's running Windows 7, Windows Server 2008 R2, or a later version, the Windows Time service stops immediately after system startup. This issue occurs even after the Startup Type is changed from **Manual** to **Automatic**.
+On a workgroup computer that's running Windows client or Windows Server, or a later version, the Windows Time service stops immediately after system startup. This issue occurs even after the Startup Type is changed from **Manual** to **Automatic**.
 
 ## Cause
 
diff --git a/support/windows-client/user-profiles-and-logon/retrieve-certificate-to-troubleshoot-windows-hello-for-business.md b/support/windows-client/user-profiles-and-logon/retrieve-certificate-to-troubleshoot-windows-hello-for-business.md
@@ -12,6 +12,8 @@ ms.custom:
 ---
 # Retrieve certificate to troubleshoot Windows Hello for Business logon failures
 
+_Applies to:_ &nbsp; Windows Server (All supported versions), Windows client (All supported versions)  
+
 This article introduces how to troubleshoot Windows Hello for Business (WHfB) logon failures in a hybrid environment.
 
 ## Scenario
diff --git a/support/windows-server/active-directory/detect-and-recover-from-usn-rollback.md b/support/windows-server/active-directory/detect-and-recover-from-usn-rollback.md
@@ -1,7 +1,7 @@
 ---
 title: How to detect and recover from a USN rollback in a Windows Server-based domain controller
 description: Explains how to recover if a domain controller is incorrectly rolled back by using an image-based installation of the operating system.
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,6 +14,7 @@ ms.custom:
 
 This article describes how to detect and recover if a Windows Server domain controller is incorrectly rolled back by using an image-based installation of the operating system.
 
+_Applies to:_ &nbsp; Windows Server (All supported versions)  
 _Original KB number:_ &nbsp; 875495
 
 > [!NOTE]
diff --git a/support/windows-server/active-directory/ldap-over-ssl-connection-issues.md b/support/windows-server/active-directory/ldap-over-ssl-connection-issues.md
@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot LDAP over SSL connection problems
 description: Describes how to troubleshoot connection problems that involve LDAP over SSL (LDAPS).
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,7 +14,7 @@ ms.custom:
 
 This article discusses steps about how to troubleshoot LDAP over SSL (LDAPS) connection problems.
 
-_Applies to:_ &nbsp; Windows Server 2016, Windows Server 2019, Windows Server 2022  
+_Applies to:_ &nbsp; Windows Server (All supported versions)  
 _Original KB number:_ &nbsp; 938703
 
 ## Step 1: Verify the Server Authentication certificate
diff --git a/support/windows-server/active-directory/no-logon-servers-are-available.md b/support/windows-server/active-directory/no-logon-servers-are-available.md
@@ -1,7 +1,7 @@
 ---
 title: No logon servers are available
 description: Occurs when cloning failed, and the server starts in Directory Services Repair Mode (DSRM). There's no visual indication that the domain controller has started in DSRM.
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,7 +14,7 @@ ms.custom:
 
 This article provides a solution to an error that occurs after you clone a new VDC, and try to sign in interactively.
 
-_Applies to:_ &nbsp; Windows Server 2016, Windows Server 2019  
+_Applies to:_ &nbsp; Windows Server (All supported versions)  
 _Original KB number:_ &nbsp; 2742908
 
 ## Symptoms
diff --git a/support/windows-server/active-directory/ntds-replication-event-2089-backup-latency-interval.md b/support/windows-server/active-directory/ntds-replication-event-2089-backup-latency-interval.md
@@ -1,7 +1,7 @@
 ---
 title: NTDS Replication Event 2089 is logged
 description: Discusses the problem where a new event error message is logged if you don't back up a Windows Server 2003 Service Pack 1 (SP1)-based domain controller in a given time period that is called the backup latency interval.
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -12,23 +12,23 @@ ms.custom:
 ---
 # NTDS Replication Event 2089 is logged if Windows Server 2003 SP1 and later domain controllers aren't backed up in a given time period
 
-This article discusses the problem where a new event error message is logged if you don't back up a Windows Server 2003 Service Pack 1 (SP1)-based domain controller in a given time period that is called the backup latency interval.
+This article discusses the problem where a new event error message is logged if you don't back up a Windows Server-based domain controller in a given time period that is called the backup latency interval.
 
-_Applies to:_ &nbsp; Window Server 2003  
+_Applies to:_ &nbsp; Windows Server (All supported versions)  
 _Original KB number:_ &nbsp; 914034
 
 ## Introduction
 
-When you back up a domain controller that is running Microsoft Windows Server 2003 Service Pack 1 (SP1), a new event error message is logged for each writable domain or application partition that the domain controller hosts. This is true if the partition isn't backed up in a given time period. The time period is called a backup latency interval. You can set a registry value to specify this interval in days.
+When you back up a domain controller, a new event error message is logged for each writable domain or application partition that the domain controller hosts. This is true if the partition isn't backed up in a given time period. The time period is called a backup latency interval. You can set a registry value to specify this interval in days.
 
 ## More information
 
-### New behavior in Windows Server 2003 SP1
+### New behavior in Windows Server 2003 SP1 and later version of Windows
 
 The DSA Signature attribute is modified every time that a system state backup is made. The operating system monitors this attribute. An event error message is logged when the backup latency interval criteria are met. Any Windows Server 2003 SP1-based domain controller may log the event because the DSA Signature attribute is a replicated attribute.
 
 > [!NOTE]
-> The new event error message is not logged until a backup is made on a Windows Server 2003-based domain controller that is running Windows Server 2003 SP1. Only Windows Server 2003 SP1-based domain controllers log this event error message.
+> The new event error message is not logged until a backup is made on a Windows Server 2003-based domain controller that is running Windows Server 2003 SP1 or later. Only Windows Server 2003 SP1-based domain controllers or later log this event error message.
 
 The default time period of the backup latency interval is half of the Tombstone Lifetime (TSL) for logging the event error message on the domain controller. The following list shows the difference in the default TSL values for a forest that is created on Windows Server 2003 and a forest that is created on Windows Server 2003 SP1:  
 
diff --git a/support/windows-server/active-directory/specialpollinterval-polling-interval-time-service-not-correct.md b/support/windows-server/active-directory/specialpollinterval-polling-interval-time-service-not-correct.md
@@ -1,7 +1,7 @@
 ---
 title: Time service does not correct the time
 description: Provides a resolution for the issue that Windows Time service does not correct the time if the service gets into Spike state.
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,6 +14,7 @@ ms.custom:
 
 This article provides a resolution for the issue that Windows Time service does not correct the time if the service gets into Spike state.
 
+_Applies to:_ &nbsp; Windows Server (All supported versions), Windows client (All supported versions)  
 _Original KB number:_ &nbsp; 2638243
 
 ## Symptoms
@@ -51,10 +52,11 @@ To configure Windows Time to use the MinPollInterval/MaxPollInterval as the poll
 
 ## Workaround
 
-If you want to use "SpecialPollinterval", you should change the following registry:  
-    Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config  
-    Value: MinPollInterval  
-    Type: DWORD
+If you want to use "SpecialPollinterval", you should change the following registry:
+
+Key: `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config`  
+Value: MinPollInterval  
+Type: DWORD  
 
 To avoid this issue, the registry key should apply conditional expression as follows:  
 Conditional expression:  
diff --git a/support/windows-server/active-directory/support-for-leap-second.md b/support/windows-server/active-directory/support-for-leap-second.md
@@ -1,7 +1,7 @@
 ---
 title: Support for the leap second
 description: Summarizes Microsoft support for the leap second.
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,6 +14,7 @@ ms.custom:
 
 This article provides information about Microsoft support for the leap second.
 
+_Applies to:_ &nbsp; Windows Server (All supported versions), Windows client (All supported versions)  
 _Original KB number:_ &nbsp; 2722715
 
 ## Summary
diff --git a/support/windows-server/active-directory/time-synchronization-not-succeed-non-ntp.md b/support/windows-server/active-directory/time-synchronization-not-succeed-non-ntp.md
@@ -1,7 +1,7 @@
 ---
 title: Time synchronization may not succeed
 description: Describes a problem that may occur when you try to use a non-Windows NTP time server as a time source. Provides steps to let you synchronize to the non-Windows NTP server.
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,7 +14,7 @@ ms.custom:
 
 When you try to synchronize a Windows-based computer to a Network Time Protocol (NTP) server that isn't running Windows, the synchronization may not succeed. This article provides a resolution to this issue.
 
-_Applies to:_ &nbsp; Supported versions of Windows Server  
+_Applies to:_ &nbsp; Windows Server (All supported versions), Windows Client (All supported versions)  
 _Original KB number:_ &nbsp; 875424
 
 ## Cause
diff --git a/support/windows-server/active-directory/windows-time-service-values-reverted.md b/support/windows-server/active-directory/windows-time-service-values-reverted.md
@@ -14,6 +14,7 @@ ms.custom:
 
 This article describes an issue in which Windows Time service settings are disabled in the registry after you upgrade to Windows Server 2016 or Windows 10 Version 1607.
 
+_Applies to:_ &nbsp; Windows Server (All supported versions), Windows client (All supported versions)  
 _Original KB number:_ &nbsp; 3201265
 
 ## Symptoms
diff --git a/support/windows-server/remote/error-when-connecting-terminal-server.md b/support/windows-server/remote/error-when-connecting-terminal-server.md
diff --git a/support/windows-server/remote/media/display-issues-deploy-apps-remoteapp-hi-def-mode/dynamics-nav-remote-app.png b/support/windows-server/remote/media/display-issues-deploy-apps-remoteapp-hi-def-mode/dynamics-nav-remote-app.png
diff --git a/support/windows-server/toc.yml b/support/windows-server/toc.yml
@@ -252,7 +252,7 @@ items:
     - name: Orphaned child domain controller is not replicated
       href: ./active-directory/orphaned-child-domain-isnt-replicated.md
     - name: RODC replicates passwords
-      href: active-directory/rodc-replicates-passwords-grant-incorrect-permissions.md      
+      href: active-directory/rodc-replicates-passwords-grant-incorrect-permissions.md
     - name: Troubleshoot domain controller replication error 1727
       href: ./active-directory/remote-procedure-call-failed-and-did-not-execute-error.md
     - name: Troubleshoot Jet database errors and recovery steps
@@ -2103,8 +2103,6 @@ items:
       href: ./remote/0xc000035b-when-you-use-lmcompatibility.md
   - name: Certificate management
     items:
-    - name: Error messages when connecting to a Terminal server
-      href: ./remote/error-when-connecting-terminal-server.md
     - name: RDS Connection Broker or RDMS fails
       href: ./remote/rds-connection-broker-or-rdms-fails-caused-by-disabled-tls-10.md
     - name: Use custom server authentication certificate for TLS over RDS
diff --git a/support/windows-server/user-profiles-and-logon/assign-logon-script-profile-local-user.md b/support/windows-server/user-profiles-and-logon/assign-logon-script-profile-local-user.md
@@ -1,7 +1,7 @@
 ---
 title: Assign a logon script to a profile
 description: Describes how to assign a logon script to a profile for a local user.
-ms.date: 01/15/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,6 +14,7 @@ ms.custom:
 
 This article describes how to assign a logon script to a profile for a local user.
 
+_Applies to:_ &nbsp; Windows Server (All supported versions), Windows client (All supported versions)  
 _Original KB number:_ &nbsp; 324803
 
 ## Summary

Original file line number	Diff line number	Diff line change
`@@ -13207,6 +13207,10 @@`
`13207`	`13207`	`{`
`13208`	`13208`	`"source_path": "support/windows-server/active-directory/remove-orphaned-domains.md",`
`13209`	`13209`	`"redirect_url": "/troubleshoot/windows-server/windows-security/remove-orphaned-domains"`
	`13210`	`+ },`
	`13211`	`+ {`
	`13212`	`+ "source_path": "support/windows-server/remote/error-when-connecting-terminal-server.md",`
	`13213`	`+ "redirect_url": "/previous-versions/troubleshoot/windows-server/error-when-connecting-terminal-server"`
`13210`	`13214`	`}`
`13211`	`13215`	`]`
`13212`	`13216`	`}`