Fix RDS licensing errors preventing Remote Desktop connections

draft · remote-access rdplicenseconfiguration

Generated by docuprocessor (prompt article/v3) · 2026-04-22 14:29

Source thread

thread_id: spaces/AAAA05BdS6s/threads/eLmKx4wopSk · 39 msgs · first 2024-12-27 · participants: Tech ATech B

Tech A 2024-12-27 13:49

Good morning, DUVALSAINT office is not able to log in trough RDP to the server. It's showing this error. I logged Jamie using /admin, but that's not working for all the users. I found this at the license manager at the server.

image/png image.png

**Remote Desktop Connection error dialog box** is displayed with the message: *"The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator."* The dialog contains **OK** and **Help** buttons, and displays a red/white error (X) icon indicating a connection failure. No error codes, part numbers, or numeric readouts are present.

Tech A 2024-12-27 13:49

(no text)

image/png image.png

**SVR22 Configuration Dialog Box** The dialog displays configuration details for license server "SVR22" with Discovery Scope set to Domain and Database Location at `C:\Windows\System32\LServer\`. Two status messages are visible: a **warning** (triangle icon) stating the server or Network Service account is not a member of the Terminal Server License Servers group in Active Directory, preventing issuance and tracking of RDS Per User CALs, with an **"Add to Group"** button present; and a **success/informational message** (checkmark icon) confirming the license server is registered as a Service Connection Point (SCP) in Active Directory Domain Services.

Tech A 2024-12-27 13:49

Should I add it to the group?

Tech B 2024-12-27 14:07

yes, and check RDS licensing service must be running

Tech A 2024-12-27 14:13

I added it, restarted RD Licensing services, but still shoiwing the same. I Found this

image/png image.png

**RD Licensing Diagnoser – SVR22.DENTAL.LOCAL (Windows Server 2022)** The tool reports **2 errors**: (1) "The licensing mode for the Remote Desktop Session Host server is not configured" and (2) "The grace period for the Remote Desktop Session Host server has expired, but the RD Session Host server has not been configured with any license servers." The **Licensing Mode** field shows "Not configured," **Number of licenses available for clients** reads **0**, and the **Remote Desktop Services License Server Information** section states **"0 license server(s) specified"** with no license servers listed.

Tech B 2024-12-27 14:14

open licensing manager and check what licenses installed

Tech A 2024-12-27 14:14

There's an option to reactivate the server

image/png image.png

The screenshot shows a **Windows Remote Desktop Licensing Manager** console with a context menu expanded on a server node (labeled **SVR22** or similar). Under **Advanced**, a submenu is visible with options: **Repeat Last Installation**, **Reactivate Server** (highlighted), and **Deactivate Server**. The license list shows two entries: one **Built-in TS Per Device** license (Unlimited, Built-in) and one **Installed RDS Per...** license (quantity **50**, Retail Purchase).

Tech A 2024-12-27 14:14

(no text)

image/png image.png

The Remote Desktop Licensing Manager console shows server **SVR22** with two licenses listed: **Windows 2000 Server Built-in TS Per Device** (Built-in, Unlimited total/available, 0 issued, Never expires, Keypack ID 2) and **Windows Server 2022 Installed RDS Per User** (Retail Purchase, 50 total, 50 available, 0 issued, Never expires, Keypack ID 3). Both licenses show **0 issued** against their available pools. No errors or warning indicators are visible in the display.

Tech B 2024-12-27 14:15

try reactivating, it might ask for some info, use the office's contact

Tech A 2024-12-27 14:19

It got reactivated, but still not connecting -.-

Tech B 2024-12-27 14:22

splashmein to server

Tech A 2024-12-27 14:22

https://woshub.com/licensing-mode-rds-host-not-configured/#google_vignette

Tech A 2024-12-27 14:22

This is not configured

Tech A 2024-12-27 14:23

643374274

Tech B 2024-12-27 14:28

who and when was this RDS setup? it looks incomplete/unconfigured

Tech A 2024-12-27 14:28

No clue, looks like they have been using this already. I see that they were logging in on different computers to the same server

Tech B 2024-12-27 14:32

find out which users allowed access and add them to the 'RemoteUsers' group i created

Tech A 2024-12-27 14:32

Let me check, I think that all the users under the OU "users" should be able to log in, I see that Jamie Vera is under that OU, he was logging in

Tech A 2024-12-27 14:32

Let me check with him

Tech A 2024-12-27 14:33

Yes, all users

Tech B 2024-12-27 14:36

makes no sense and not recommended and dangerous, why would very user need access to server? anyhow, users part of that group will get access. try with one account make sure it works

Tech A 2024-12-27 14:40

I found this note at Bitrix

image/png image.png

The image shows a **Comment dialog box** from a ticketing or support system. The text reads: *"West location RDP to East office, so no data to backup here."* No error codes, part numbers, indicator lights, or equipment are visible — this is a text-only software UI element.

Tech A 2024-12-27 14:40

Maybe they use 2 different db's from 2 locations

Tech A 2024-12-27 14:41

I added him to the group, he tried to log in, but same error appeared

Tech B 2024-12-27 14:42

How they connect? RDP client or remote app published?

Tech A 2024-12-27 14:43

Remote desktop client

Tech A 2024-12-27 14:44

I see that they are using RemoteApps too

image/png image.png

**Remote Desktop Connection error on Windows 10 workstation.** The RDP client is attempting to connect to **192.168.10.220** with username **DENTAL\WSop1**. An error dialog reads: *"The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator."*

Tech A 2024-12-27 14:44

Anyways they use RDP client too, he was showing me that

Tech B 2024-12-27 14:46

check the URL in remote apps properties

Tech B 2024-12-27 14:46

on the client pc

Tech A 2024-12-27 14:48

It's pointing to cloud.dolphinimaging, so nothing to worry about

Tech B 2024-12-27 14:51

Might be this bug https://www.dell.com/support/kbdoc/en-us/000219084/a Reinstalling role might require server reboot

Tech A 2024-12-27 14:51

I need to ask them about the restart,let me check

Tech A 2024-12-27 14:53

I will call him 1.15pm to reboot the server, during lunchtime

Tech B 2024-12-27 14:54

Ok, when ready check that box and hit next to create deployment

Tech A 2024-12-27 14:54

Sure, will do

Tech A 2024-12-27 14:54

Thanks Alex

Tech B 2024-12-27 14:55

No problem

---
title: "Fix RDS licensing errors preventing Remote Desktop connections"
category: remote-access
tags: ["rdp", "license", "configuration"]
source_thread_id: "spaces/AAAA05BdS6s/threads/eLmKx4wopSk"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T14:29:45"
participants: ["Tech A", "Tech B"]
---

# Fix RDS licensing errors preventing Remote Desktop connections

## Problem

Users at an office were unable to connect to their server via Remote Desktop, receiving the error "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator." The RD Licensing Diagnoser showed two critical errors: the licensing mode for the Remote Desktop Session Host server was not configured, and the grace period had expired with no license servers configured. The license server (SVR22) had valid licenses available (50 RDS Per User CALs) but was not properly integrated with Active Directory - the server was not a member of the Terminal Server License Servers group, preventing license issuance.

## Resolution

1. Add the license server to the Terminal Server License Servers group in Active Directory using the "Add to Group" button in the RD Licensing Manager configuration dialog
2. Restart the Remote Desktop Licensing service on the server
3. If the issue persists, reactivate the license server through RD Licensing Manager (right-click server > Advanced > Reactivate Server)
4. Add authorized users to the appropriate Remote Desktop Users group for access control
5. If licensing errors continue after these steps, the RDS role may need to be reinstalled, which requires a server reboot during maintenance hours

The resolution was incomplete in this case - after completing steps 1-4, the licensing configuration still showed as "Not configured" and users continued receiving connection errors, indicating the RDS role installation may be incomplete and require reinstallation.

## References

- Source discussion: `spaces/AAAA05BdS6s/threads/eLmKx4wopSk`
- Attachments:
  - ![image.png](../attachments/eLmKx4wopSk.0TnyWlZrkYk/image.png) — The Remote Desktop Licensing Manager console shows server **SVR22** with two licenses listed: **Windows 2000 Server Built-in TS Per Device** (Built-in, Unlimited total/available, 0 issued, Never expires, Keypack ID 2) and **Windows Server 2022 Installed RDS Per User** (Retail Purchase, 50 total, 50 available, 0 issued, Never expires, Keypack ID 3). Both licenses show **0 issued** against their available pools. No errors or warning indicators are visible in the display.
  - ![image.png](../attachments/eLmKx4wopSk.56gSt_an6k0/image.png) — The image shows a **Comment dialog box** from a ticketing or support system. The text reads: *"West location RDP to East office, so no data to backup here."* No error codes, part numbers, indicator lights, or equipment are visible — this is a text-only software UI element.
  - ![image.png](../attachments/eLmKx4wopSk.RqJzSoCDnAA/image.png) — **SVR22 Configuration Dialog Box**
  - ![image.png](../attachments/eLmKx4wopSk.bjb5hqfAa5M/image.png) — **RD Licensing Diagnoser – SVR22.DENTAL.LOCAL (Windows Server 2022)**
  - ![image.png](../attachments/eLmKx4wopSk.cF1WATxPZDo/image.png) — The screenshot shows a **Windows Remote Desktop Licensing Manager** console with a context menu expanded on a server node (labeled **SVR22** or similar). Under **Advanced**, a submenu is visible with options: **Repeat Last Installation**, **Reactivate Server** (highlighted), and **Deactivate Server**. The license list shows two entries: one **Built-in TS Per Device** license (Unlimited, Built-in) and one **Installed RDS Per...** license (quantity **50**, Retail Purchase).
  - ![image.png](../attachments/eLmKx4wopSk.eLmKx4wopSk/image.png) — **Remote Desktop Connection error dialog box** is displayed with the message: *"The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator."* The dialog contains **OK** and **Help** buttons, and displays a red/white error (X) icon indicating a connection failure. No error codes, part numbers, or numeric readouts are present.
  - ![image.png](../attachments/eLmKx4wopSk.oXCgbBekc5A/image.png) — **Remote Desktop Connection error on Windows 10 workstation.**

Generated article

draft