Merge pull request #8542 from v-lianna/v-lianna-patch-4

AB#4640 Update troubleshoot-remote-desktop-disconnected-errors.md

Author: Deland-Han

support/windows-server/remote/troubleshoot-remote-desktop-disconnected-errors.md

@@ -1,11 +1,11 @@
 ---
 title: Troubleshoot Remote desktop disconnected errors
 description: Provides troubleshooting information for Remote desktop disconnected errors.
-ms.date: 01/15/2025
+ms.date: 03/26/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
-ms.reviewer: kaushika
+ms.reviewer: kaushika, warrenw, linquantang
 ms.custom:
 - sap:remote desktop services and terminal services\web access (includes remoteapp and desktop connections)
 - pcy:WinComm User Experience
@@ -19,8 +19,6 @@ adobe-target: true
 
 This article helps you understand the most common settings that are used to establish a Remote Desktop session in an enterprise environment, and provides troubleshooting information for Remote desktop disconnected errors.
 
-_Original KB number:_   2477176
-
 > [!NOTE]
 > This article is intended for use by support agents and IT professionals.
 
@@ -86,7 +84,19 @@ Remote Desktop Services clients are repeatedly denied access to the Remote Deskt
     > Because of a security error, the client could not connect to the Terminal server. After making sure that you are logged on to the network, try connecting to the server again.  
     > Remote desktop disconnected. Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.
 
-Additionally, the following event ID messages may be logged in Event Viewer on the Remote Desktop server.
+Additionally, check the following Event Viewer paths:
+
+On the RD Session Host server:
+
+- **Event Viewer** > **Applications and Services Logs** > **Microsoft** > **Windows** > **RemoteApp and Desktop Connections**
+- **Event Viewer** > **Applications and Services Logs** > **Microsoft** > **Windows** > **TerminalServices-LocalSessionManager**
+- **Event Viewer** > **Applications and Services Logs** > **Microsoft** > **Windows** > **TerminalServices-RemoteSessionManager**
+
+On the RD license server:
+
+**Event Viewer** > **Applications and Services Logs** > **Microsoft** > **Windows** > **TerminalServices-Licensing**
+
+The following event ID messages may be logged:
 
 - Event message 1  
 
@@ -130,7 +140,7 @@ Additionally, the following event ID messages may be logged in Event Viewer on t
 
 ## Resolution for Symptom 1
 
-To resolve this problem, use the following methods, as appropriate.
+To resolve this problem, follow these steps depending on your operating system version.
 
 ### Verify Remote Desktop is enabled
 
@@ -187,6 +197,8 @@ Membership in the local Administrators group, or equivalent, on the RD Session H
 
 #### Add users and groups to the Remote Desktop Users group by using the Remote tab
 
+Follow these steps depending on your operating system version:
+
 1. Start the System tool. To do this, click Start, click Control Panel, click the **System** icon, and then click **OK**.
 
 2. Under **Control Panel Home**, click **Remote settings**.
@@ -259,7 +271,7 @@ To change the port that is assigned to RDP, follow these steps:
 
 3. Locate and then click the following registry subkey:
 
-    `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Remote Desktop server\WinStations`
+    `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations`
 
 RDP-TCP is the default connection name. To change the port for a specific connection on the Remote Desktop server, select the connection under the **WinStations** key:
 
@@ -400,7 +412,7 @@ To resolve this problem, back up and then remove the **X509 Certificate** regist
 
 4. On the **Registry** menu, click **Export Registry File**.
 
-5. Type exported- Certificate in the **File name** box, and then click **Save*.
+5. Type `exported- Certificate` in the **File name** box, and then click **Save**.
 
     > [!NOTE]
     > If you have to restore this registry subkey in the future, double-click the Exported-parameters.reg file that you saved in this step.