Skip to content

Commit 21f363c

Browse files
authored
Updates from editor
1 parent feca84d commit 21f363c

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

support/windows-server/remote/cannot-connect-rds-no-license-server.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Cannot connect to RDS because no RD Licensing servers are available
33
description: This article describes how to troubleshoot RDS connection errors that are related to Remote Desktop licensing.
4-
ms.date: 01/17/2025
4+
ms.date: 01/20/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -44,7 +44,7 @@ These issue could be caused by the following user messages:
4444

4545
In this case, [check the RD Licensing configuration](#check-the-rd-licensing-configuration).
4646

47-
If the RD License Diagnoser lists other problems, such as "The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client," there may be a problem that affects the license certificates. Such problems tend to be associated with user messages, such as the following:
47+
If the RD License Diagnoser lists other problems, such as "The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client," there might be a problem that affects the license certificates. Such problems tend to be associated with user messages, such as the following:
4848

4949
Because of a security error, the client could not connect to the Terminal server. After making sure that you are signed in to the network, try connecting to the server again.
5050

@@ -129,7 +129,7 @@ For more information, see [Access this computer from the network - security poli
129129
## Refresh the X509 Certificate registry keys
130130

131131
> [!IMPORTANT]
132-
> Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you start modifying the registry, [back up the registry](https://support.microsoft.com/help/322756) so you can restore it in case something goes wrong.
132+
> Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you start modifying the registry, [back up the registry](https://support.microsoft.com/help/322756) so that you can restore it in case something goes wrong.
133133
134134
To resolve this problem, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the RD Licensing server. Follow these steps.
135135

@@ -140,7 +140,7 @@ Here's how to reactivate the RD Licensing server:
140140

141141
1. Open the Registry Editor and navigate to **HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server\\RCM**.
142142
2. On the Registry menu, select **Export Registry File**.
143-
3. Enter **exported- Certificate** into the **File name** box, then select **Save**.
143+
3. Enter **exported- Certificate** into the **File name** box, and then select **Save**.
144144
4. Right-click each of the following values, select **Delete**, and then select **Yes** to verify the deletion:
145145
- **Certificate**
146146
- **X509 Certificate**

0 commit comments

Comments
 (0)