How do I set the licensing mode on the remote desktop session host server 2016?

How does one specify licensing mode in RDS on Server 2016

Archived Forums

>

Remote Desktop Services (Terminal Services)

• Question

• 1

  Sign in to vote

  In RD Licensing Diagnoser on Server 2016, I get a message that the licensing mode for the Remote Desktop Session Host server is not configured. How does one set this. I cannot find the "RD Session Host Configuration Tool" like I we have used in the past with Windows Server 2008 R2 to accomplish this task.

  Thanks
  NK

  Friday, February 10, 2017 8:32 PM

Answers

• 12

  Sign in to vote

  Hi,

  If you created a RDS deployment using Server Manager -- Add roles and features -- RDS install -- Quick/Standard -- Session-based you would set the licensing mode and RD Licensing server name in RDS Deployment Properties and make sure the server is part of a session collection.

  If you do not create a RDS deployment then you can set it via group policy settings. For example, open gpedit.msc:

  Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing

  Use the specified Remote Desktop license servers Enabled

  Set the Remote Desktop licensing mode Enabled

  -TP

  • Marked as answer by NJK-Work Friday, February 10, 2017 9:06 PM

  Friday, February 10, 2017 8:49 PM

All replies

• 12

  Sign in to vote

  Hi,

  If you created a RDS deployment using Server Manager -- Add roles and features -- RDS install -- Quick/Standard -- Session-based you would set the licensing mode and RD Licensing server name in RDS Deployment Properties and make sure the server is part of a session collection.

  If you do not create a RDS deployment then you can set it via group policy settings. For example, open gpedit.msc:

  Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing

  Use the specified Remote Desktop license servers Enabled

  Set the Remote Desktop licensing mode Enabled

  -TP

  • Marked as answer by NJK-Work Friday, February 10, 2017 9:06 PM

  Friday, February 10, 2017 8:49 PM

• 0

  Sign in to vote

  Thanks.

  Friday, February 10, 2017 9:06 PM

• 0

  Sign in to vote

  Thank You, I had the same issue and this resolved it.

  Wednesday, July 11, 2018 5:52 PM

• 0

  Sign in to vote

  Thanks here also. Worked nicely on 2016.

  Wednesday, August 29, 2018 2:27 AM

• 0

  Sign in to vote

  thanks, the local gpo setting fixed it for me. I had edited the license server settings in the properties of the RDS deployment but they didn't seem to be applied, even though the licensing node was lit green.

  Friday, November 23, 2018 6:40 PM

• 0

  Sign in to vote

  Almost 2 years later and this is still the best answer I can find online.

  Wednesday, January 30, 2019 5:55 PM

• 0

  Sign in to vote

  2 hours messing with an RDS deployment. 2 minutes with gpedit. Thank you!!

  Saturday, February 23, 2019 12:53 AM

• 0

  Sign in to vote

  Thanks. This thread helped me as well.

  I don't often deploy RDS but every time I do I run into problems like this and it take ages to look up a solution. You'd think Microsoft would streamline the process which I'm sure will save a lot of phone calls to support.

  
  
  • Edited by Cougie Sunday, April 7, 2019 11:18 PM

  Sunday, April 7, 2019 11:18 PM

• 0

  Sign in to vote

  This is a great example of something working fine for a decade, followed by a decision to remove a convenient tool to do something, and not making it obvious how to do things differently.

  Tuesday, October 15, 2019 2:01 PM

• 0

  Sign in to vote

  This solution is "almost" correct. For me at least, the key part was : "make sure the server is part of a session collection."

  For my RDS 2016 deployment, until I made the server part of a session collection, the RDS licensing diagnoser kept saying error! I also published an app at the same time. Actually, the the RDS licensing diagnoser kept saying that the mode is not set, even though I had set it correctly using "edit deployment properties". I had set it to per user, but the registry entry was set to 5 (should be 4 for per user). Must be a bug or something.
  

  By the way, I did NOT have to do any group policy editing...should not have to since the licensing server was being applied using group policy anyway.

  I also looked at:

  https://www.tbngconsulting.com/blog/bid/404182/Licensing-mode-for-the-Remote-Desktop-Session-Host-is-not-configured

  https://www.tecklyfe.com/remote-desktop-licensing-mode-is-not-configured-error-on-windows-server/

  IMHO both these people are recommending something which is not necessary.

  ---

  -Rajeev rajdude.com

  Thursday, March 5, 2020 4:21 PM

16 Replies

· · ·

Cayenne

OP

Ken Carter

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

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

Da_Schmoo

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

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

James8090 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

Da_Schmoo

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

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

James8090 May 30, 2017 at 14:36 UTC

My thoughts as well, can't hurt.

Also found this:

https://www.tbngconsulting.com/blog/bid/404182/Licensing-mode-for-the-Remote-Desktop-Session-Host-is...

4

· · ·

Mace

OP

Da_Schmoo

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

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

James8090 May 30, 2017 at 14:50 UTC

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.

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.

0

· · ·

Mace

OP

Da_Schmoo

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

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

James8090 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.

https://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

Da_Schmoo

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

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

James8090 May 31, 2017 at 20:08 UTC

So nobody has any answers?

0

· · ·

Pure Capsaicin

OP

DragonsRule

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 31, 2017 at 20:14 UTC

Microsoft Licensing expert

211 Best Answers

840 Helpful Votes

1 How-to

So you did install the RDS role before joining the domain?

0

· · ·

Serrano

OP

James8090 May 31, 2017 at 20:16 UTC

GrammarPolice wrote:

So you did install the RDS role before joining the domain?

Couldn't say but considering it listed the non-domain server name I would think so.

0

· · ·

Pure Capsaicin

OP

DragonsRule

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 31, 2017 at 20:17 UTC

Microsoft Licensing expert

211 Best Answers

840 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

James8090 Jun 13, 2017 at 19:42 UTC

No best answer. Fixed.

0

· · ·

· · ·

Jalapeno

OP

Wood-E May 11, 2018 at 21:54 UTC

James8090 wrote:

My thoughts as well, can't hurt.

Also found this:

https://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.

Troubleshooting ‘remote desktop licensing mode is not configured’ error

Designed by Freepik

Accessing remote desktops and configuring them is a common administrative task in organizations, and it has taken greater importance in the current work-from-anywhere culture. However, accessing remote desktops is not always a straightforward task as it could require licenses and can throw up many errors in case of misconfigurations. The error message is often not detailed enough to give you the cause of the problem, so fixing it can take up a ton of time and effort, not to mention the frustrations that come with it. One such critical error that’s not self-explanatory is the “remote desktop licensing mode is not configured” error. In this article, let’s learn all about this error, its causes, and how to fix it.

But before that, a touch on the basics.

What is remote desktop licensing?

Every device or user that wants to connect to a remote desktop session host requires a Client Access License (CAL), to help you install and track licenses across different computers. This CAL also helps with streamlining access and ensures that no unauthorized system can connect to a remote host.

When a host or device tries to connect to a remote desktop session (RDS) Host server, it checks the configuration to see if a CAL is required. If yes, the RDS host server requests a CAL from the RD license server. Next, the server checks if the CAL is valid and issues the same to the client.

Using this CAL, the client connects to the RD Session host server and, through it, to the required remote desktop.

Many CAL versions apply to different session host versions. For example, the 2008 and 2008 R2 session hosts are compatible with RDS 2008 R2 CAL, RDS 2012 CAL, RDS 2016 CAL, and RDS 2019 CAL, while the 2012 session host is compatible with RDS 2012 CAL and later versions. So, check the version compatibility for your CAL.

Microsoft offers a 120-day grace period, and no license is required during this time. After this time ends, a client needs a CAL to log into a remote desktop through the RD Session Host server.

Now that you know what remote desktop licensing is, let’s jump into the error.

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.

How To Fix The Remote Desktop Licensing Mode Is Not Configured Error

• Click on Start and type gpedit and go into Edit Group Policy
  If you centrally manage your Group Policy, you can edit it on your Domain Controller and apply it to the OU where your Remote Desktop Licensing Servers are
• Navigate to: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
• Open Use the specified Remote Desktop license servers
  Change it to Enabled and enter your licensing server host name or IP address (or localhost)
• Open Set the Remote Desktop licensing mode
  Change it to Enabled and set it to Per Device or Per User depending on your license
• Restart the server

If you open the Remote Desktop Licensing Diagnoser, you shouldn’t see anymore errors regarding your licenses.

Share This: