Skip to content

Commit 76b8e78

Browse files
author
Simonx Xu
authored
Merge pull request #8138 from warren-msft/docs-editor/cannot-connect-rds-no-license-1738629925
AB#3726: Update cannot-connect-rds-no-license-server.md
2 parents 433dc9f + d2b8d02 commit 76b8e78

1 file changed

Lines changed: 12 additions & 15 deletions

File tree

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

Lines changed: 12 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
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/20/2025
4+
ms.date: 02/08/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
8-
ms.reviewer: kaushika, v-tappelgate, rafx
8+
ms.reviewer: kaushika, v-tappelgate, rafx, warrenw
99
ms.custom: sap:Remote Desktop Services and Terminal Services\Licensing for Remote Desktop Services (Terminal Services), csstroubleshoot
1010
keywords: RD Licensing server, RD CAL
1111
---
@@ -17,27 +17,24 @@ This article helps you troubleshoot the "No licenses available" error in a deplo
1717

1818
Clients cannot connect to Remote Desktop Services, and they display messages that resemble the following:
1919

20-
```output
21-
The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.
22-
```
20+
> The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.
2321
24-
```output
25-
Access was denied because of a security error.
26-
```
22+
> Access was denied because of a security error.
2723
2824
Sign in to the RD Session Host as a domain administrator and open the RD License Diagnoser. Look for messages like the following:
2925

30-
```output
31-
The grace period for the Remote Desktop Session Host server has expired, but the RD Session Host server hasn't been configured with any license servers. Connections to the RD Session Host server will be denied unless a license server is configured for the RD Session Host server.
32-
```
26+
> The grace period for the Remote Desktop Session Host server has expired, but the RD Session Host server hasn't been configured with any license servers. Connections to the RD Session Host server will be denied unless a license server is configured for the RD Session Host server.
3327
34-
```output
35-
License server <computer name> is not available. This could be caused by network connectivity problems, the Remote Desktop Licensing service is stopped on the license server, or RD Licensing isn't available.
36-
```
28+
> License server \<computer name\> is not available. This could be caused by network connectivity problems, the Remote Desktop Licensing service is stopped on the license server, or RD Licensing isn't available.
29+
30+
Clients can connect to Remote Desktop Services, but they display a balloon message that resembles the following:
31+
32+
> Remote Desktop licensing mode is not configured.
33+
Remote Desktop Services will stop working because this computer is past its licensing grace period. On the RD Connection Broker server, use Server Manager to specify the Remote Desktop licensing mode.
3734

3835
## Cause
3936

40-
These issue could be caused by the following user messages:
37+
These issues could be caused by the following user messages:
4138

4239
- The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer.
4340
- The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.

0 commit comments

Comments
 (0)