Activate the Remote Desktop Services license server
- Article
- 07/29/2021
- 2 minutes to read
- 4 contributors
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
In this article
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016
The Remote Desktop Services license server issues client access licenses [CALs] to users and devices when they access the RD Session Host. You can activate the license server by using the Remote Desktop Licensing Manager.
Set-RDLicenseConfiguration
- Reference
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
Module: RemoteDesktop
Defines settings for the RD Licensing server and the licensing mode of the Remote Desktop deployment.
In this article
How to activate the Windows Remote Desktop Service [RDS] Role
When is the RDS role needed?
The default server setting is RDP Admin mode, which allows single sessions with the appropriate privileges. If there is only one user, then additional RDS [Remote Desktop Service] licenses are not required.
If multiple users need to connect to the server simultaneously, each user needs a Remote Desktop Server Client Access License [RDS CAL] added to the license manager, with the session host configured to use that license manager.
Note: If this is not done, the RDS will go into Evaluation Mode, which will expire after 120 days, effectively locking users out.An error message ‘Remote Desktop licensing mode is not configured‘ will be displayed.
16 Replies
· · ·
Cayenne
OP
May 30, 2017 at 14:14 UTC
Just installing the CALs is not enough. You need to specify in Server Manager what mode you are using: Device CALs or User CALs. Start RD Session Host Configuration and select the mode you want to use [User- or Device-based CALs].
0
· · ·
Mace
OP
May 30, 2017 at 14:19 UTC
Microsoft Licensing expert
144 Best Answers
691 Helpful Votes
Server Manager, RDS, Edit Deployment properties - do you have your licensing server and mode defined here?
0
· · ·
Serrano
OP
May 30, 2017 at 14:27 UTC
Yes it's there. It does have the server listed before and after domain promotion it appears but not sure why that would matter.
1
· · ·
Mace
OP
May 30, 2017 at 14:30 UTC
Microsoft Licensing expert
144 Best Answers
691 Helpful Votes
I'd remove the entry for the non-domain joined licensing server.
1
· · ·
Serrano
OP
Best Answer
May 30, 2017 at 14:36 UTC
My thoughts as well, can't hurt.
Also found this:
//www.tbngconsulting.com/blog/bid/404182/Licensing-mode-for-the-Remote-Desktop-Session-Host-is...4
· · ·
Mace
OP
May 30, 2017 at 14:40 UTC
Microsoft Licensing expert
144 Best Answers
691 Helpful Votes
You mentioned "before and after" domain promotion. I can see issues arising if you joined the server to the domain after installing the RDS Role. In a workgroup setup, only per device licenses are valid, there are hoops you need to jump through to get things working and you lose some features. I can envision weirdness if this is the case.
0
· · ·
Serrano
OP
May 30, 2017 at 14:50 UTC
Single server environment, Essentials. I only said that as that is the only reason I can think of that would have both the pre and post domain names being listed.Da_Schmoo wrote:
You mentioned "before and after" domain promotion. I can see issues arising if you joined the server to the domain after installing the RDS Role. In a workgroup setup, only per device licenses are valid, there are hoops you need to jump through to get things working and you lose some features. I can envision weirdness if this is the case.
0
· · ·
Mace
OP
May 30, 2017 at 14:53 UTC
Microsoft Licensing expert
144 Best Answers
691 Helpful Votes
Essentials? My understanding is Essentials only supports the RDGateway role which it installs by default and not the full RDS Services like Session Hosts, etc.
1
· · ·
Serrano
OP
May 30, 2017 at 19:47 UTC
Server 2012r2 with Essentials Role Installed.
Not what I was informed when licensing this server.As the server is Server 2012r2 anyoneusing RD Gateway directly needs a CAL. As this server is Server 2012R2 with the Essentials Role installed the RDS CALS were required for any remote access:
Finally, it is important to note that turning on the Essentials Experience role does not change the licensing terms for the edition that you purchased in any way. The most common question is around using the Remote Web Access feature of the Essentials Experience role. Because this feature makes use of the Remote Desktop Gateway role service of Remote Desktop Services [RDS], an RDS client access license [CAL] is required for each user who is using this feature with the Standard and Datacenter editions. However, for the Essentials edition, as with previous versions, the use of Remote Web Access does not require an RDS CAL. For more information, see this Licensing Brief.
//blogs.technet.microsoft.com/sbs/2013/09/03/understanding-licensing-for-windows-server-2012-r2-essentials-and-the-windows-server-essentials-experience-role/
0
· · ·
Mace
OP
May 30, 2017 at 19:52 UTC
Microsoft Licensing expert
144 Best Answers
691 Helpful Votes
Having the Essentials "role" installed doesn't change the licensing. Anyone using any RDS feature - Remote Host, RemoteApps, RDGateway, requires an RDS and a Server CAL.
The Server Essentials product itself doesn't require any additional licensing but that's the Essentials SKU, not Standard with the Essentials "role".
1
· · ·
Serrano
OP
May 31, 2017 at 20:08 UTC
So nobody has any answers?
0
· · ·
Pure Capsaicin
OP
May 31, 2017 at 20:14 UTC
Microsoft Licensing expert
211 Best Answers
836 Helpful Votes
1 How-to
So you did install the RDS role before joining the domain?
0
· · ·
Serrano
OP
May 31, 2017 at 20:16 UTC
Couldn't say but considering it listed the non-domain server name I would think so.GrammarPolice wrote:
So you did install the RDS role before joining the domain?
0
· · ·
Pure Capsaicin
OP
May 31, 2017 at 20:17 UTC
Microsoft Licensing expert
211 Best Answers
836 Helpful Votes
1 How-to
Personally, I agree with Da_Schmoo. That probably messed things up. I would fully remove all the RDS related roles and start over.
0
· · ·
Serrano
OP
Jun 13, 2017 at 19:42 UTC
No best answer. Fixed.
0
· · ·
· · ·
Jalapeno
OP
May 11, 2018 at 21:54 UTC
James8090 wrote:
My thoughts as well, can't hurt.
Also found this:
//www.tbngconsulting.com/blog/bid/404182/Licensing-mode-for-the-Remote-Desktop-Session-Host-is....
This worked perfectly for me. Thanks!
1
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
27 Replies
· · ·
Pure Capsaicin
OP
Oct 15, 2019 at 19:01 UTC
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes
What does Get-RDlicenseconfiguration show?
//docs.microsoft.com/en-us/powershell/module/remotedesktop/get-rdlicenseconfiguration?view=win...
0
· · ·
Serrano
OP
Oct 15, 2019 at 19:10 UTC
2 things.
1. Add pc to Remote Desktop Host AD group
2. Make sure GPO points to license server in the policy applied to the session host
1
· · ·
Anaheim
OP
Oct 15, 2019 at 19:13 UTC
Mode LicenseServer
PerUse {ServerXXX.FQDN}
it's the correct RD Licensing server.
0
· · ·
Serrano
OP
Oct 15, 2019 at 19:19 UTC
You need to enable the License server security group policy and add the secondary RDS server [the server that does not have the licenses installed on it] to the RD Endpoint Server group.
0
· · ·
Mace
OP
Oct 15, 2019 at 19:23 UTC
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
It's pulling that old licensing server address from somewhere - RDS Deployment properties on the RDS box or Group Policy.
1
· · ·
Anaheim
OP
Oct 15, 2019 at 19:43 UTC
I wish I knew where it was pulling it from.
0
· · ·
Anaheim
OP
Oct 15, 2019 at 19:43 UTC
I followed your directions. I'll come back and update you, thanks for the help!
0
· · ·
Mace
OP
Best Answer
Oct 15, 2019 at 21:17 UTC
Personally I find setting the license server via GPO the most reliable way. I've had issues with the server manager not setting correctly in the past.
Set the license mode and server via [L]GPO and the error should go away so long as the license server is activated.
0
· · ·
Anaheim
OP
Oct 15, 2019 at 22:20 UTC
I am still getting that message and the error message 1131
0
· · ·
Pure Capsaicin
OP
Oct 16, 2019 at 01:15 UTC
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes
Da_Schmoo wrote:
It's pulling that old licensing server address from somewhere - RDS Deployment properties on the RDS box or Group Policy.
Agreed. You need to figure out where it's getting this from. Your other settings don't matter if they are being overwritten somehow with bad info.
You said it's the IP, not the FQDN that's in the error? Is that IP in use at this point?
0
· · ·
Serrano
OP
Oct 16, 2019 at 11:36 UTC
Have you checked the RD Licensing Diagnoser on the secondary RDS server? What server does it point to?
0
· · ·
Anaheim
OP
Oct 16, 2019 at 15:59 UTC
I have and its looking for the OLD RD Licensing server. I don't know how to change it because everywhere I look has the NEW RD Licensing server. The OLD licensing server is SOMEWHERE in the system but I can't find where. this is driving me nuts.
0
· · ·
Serrano
OP
Oct 16, 2019 at 17:25 UTC
Connect to the new server in the licensing diagnoser
0
· · ·
Anaheim
OP
Oct 16, 2019 at 17:55 UTC
0
· · ·
Serrano
OP
Oct 16, 2019 at 18:04 UTC
justgoogleit wrote:
You need to enable the License server security group policy and add the secondary RDS server [the server that does not have the licenses installed on it] to the RD Endpoint Server group.
Did you do this? Because this should resolve the issue. I had a similar issue and resolved it as above
0
· · ·
Anaheim
OP
Oct 16, 2019 at 18:05 UTC
I did do that.
0
· · ·
Mace
OP
Oct 16, 2019 at 18:06 UTC
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
Check:
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
in Gpedit on the RDS Server in question.
2
· · ·
Anaheim
OP
Oct 16, 2019 at 18:36 UTC
0
· · ·
Anaheim
OP
Oct 16, 2019 at 18:36 UTC
0
· · ·
Anaheim
OP
Oct 16, 2019 at 18:37 UTC
0
· · ·
Serrano
OP
Oct 16, 2019 at 19:48 UTC
what is the information in the Remote Desktop Services License Server Information field that you cut out? Does it point to the new or old server? If old, then you are connected to the wrong server in rd licensing server diagnoser.
0
· · ·
Anaheim
OP
Oct 16, 2019 at 20:52 UTC
it's the old one. I don't know where it is getting that information though.
0
· · ·
Serrano
OP
Oct 17, 2019 at 13:15 UTC
You need to "Connect to Remote Desktop Session Host Server" like I indicated in my reply a few posts back, using a picture. If you've set up all the details via gpo, ran a gpupdate, then you should just need to point to the License server in the licensing diagnoser on the secondary RDS server.
0
· · ·
Anaheim
OP
Oct 17, 2019 at 22:41 UTC
This is just as frustrating for me as it is for you. I've done everything outlined above to no avail. I even went to the OLD RD server and GP and put in the NEW RD server as the licensing server.
0
- 1
- 2
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Use the specified Remote Desktop license servers
This policy setting allows you to specify the order in which an RD Session Host server attempts to locate Remote Desktop license severs.
If you enable this policy setting, an RD Session Host server first attempts to locate the license servers that you specify. If the specified license servers cannot be located, the RD Session Host server will attempt automatic license server discovery.
In the automatic license server discovery process, an RD Session Host server in a Windows Server-based domain attempts to contact a license server in the following order:
1. License servers that are specified in the Remote Desktop Session Host Configuration tool
2. License servers that are published in Active Directory Domain Services
3. License servers that are installed on domain controllers in the same domain as the RD Session Host server
If you disable or do not configure this policy setting, the RD Session Host server uses the license server discovery mode specified in the Remote Desktop Session Host Configuration tool.
Supported on: At least Microsoft Windows Server 2003 with SP1
License servers to use:
| RegistryHive | HKEY_LOCAL_MACHINE |
| RegistryPath | SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services |
| ValueName | LicenseServers |
| ValueType | REG_SZ |
| Default Value |
Separate license server names with commas.
Example: Server1,Server2.example.com,192.168.1.1
vmware_rdsh.admx