Warning using the Remote Desktop Web client with per-device licensing is not supported

Set up the Remote Desktop web client for your users

Article
02/17/2022
12 minutes to read
12 contributors

Is this page helpful?

Yes No

Nội dung chính Show

Set up the Remote Desktop web client for your users
Is this page helpful?
In this article
RDS 2016 - Licensing Issue - Per Device - Warning at user logon
Answers
All replies
Not compatible with per-device CALs ^
Installation via PowerShell ^

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

The Remote Desktop web client lets users access your organization's Remote Desktop infrastructure through a compatible web browser. They'll be able to interact with remote apps or desktops like they would with a local PC no matter where they are. Once you set up your Remote Desktop web client, all your users need to get started is the URL where they can access the client, their credentials, and a supported web browser.

Important

The web client does support using Azure AD Application Proxy but does not support Web Application Proxy at all. See Using RDS with application proxy services for details.

RDS 2016 - Licensing Issue - Per Device - Warning at user logon

Archived Forums

Remote Desktop Services (Terminal Services)

Question
0

Sign in to vote

Hello guys,

I'm building a new RDS farm on Windows Server 2016. 2 servers with connection broker, gateway, web server and licensing role (ha mode) installed and 4 session hosts - all on WS2016Standard.

Licensing is configured on both licensing servers - licenses per device are added on both and is integrated with AD. No errors or warning pop-up regarding licensing (though RD Licensing Diagnoser is no longer available in WS2016 apparently). Licensing servers are activated and integrated with AD.

We changed the licensing mode from per user to, per device (an initial mistake). For this change we rebuild the RD licensing database and re-added the per-device licenses. Next we changed the deployment properties 'RD Licensing' mode: we removed both lic servers and re-added them with per device licensing mode.

If we logon with our test users (5 of them) we all get this error. It states: "There's a problem with Remote Desktop Licensing - There is a problem with your license for Remote Desktop and the session will end in 60 minutes. Contact your system administrator to resolve this issue".

Just to be clear: no errors pop-up whatsoever in Group Policy, System, Application and Administrative Event Logs on the Terminal Servers and connection broker servers.

Any guidance on how i can troubleshoot this please?

Wednesday, February 1, 2017 7:37 AM

Answers

1

Sign in to vote

Hi,

NOTE: #5 below corrected the issue Sven was having, however, for future reference the other items are valuable for troubleshooting this error.

1. On the RDSH server that the user connects to, there should be a warning entry in System logfrom TerminalServices-RemoteConnectionManager around the time of the logon. Pleasedo a fresh test connection and then examine the specific RDSH server the user connected to for this entry and reply back.

2. In RDS deployment properties, RD Licensing tab, please make sure the correct FQDN for your RD Licensing server(s)are listed.

3. In RD Licensing Manager, does it show that you have2016 Per Device CALs available to be issued? Related, please check if the specific device you are testing from is listed in RD Licensing Manager as having been issued a temporary or permanentRDS CAL and if yes, is it still valid or expired?

4. Please make sure the RD Licensing service is Running on your RD Licensing server(s), and that there are no firewalls blocking communication between your RDSH servers and your RD Licensing server(s).

5. On the client PC, please rename HKLM\ SOFTWARE\ Microsoft\ MSLicensing key to MSLicensing.bak, open an administrator command prompt, and enter the following:

regsvr32 mstscax.dll

The above command will createa freshMSLicensing key and required subkeys/values. Please test connecting to the server from the workstation after recreating MSLicensing to see if Per Device RDS CAL is issued.

For reference, below is the English version of message:

Text version:

"Remote Desktop License Issue

There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes. Contact your system administrator to fix this problem."

Please reply back with your results/findings, whether positive or negative, and I will assist your further if needed.

Thanks.

-TP
- Edited by TP []MVP Wednesday, February 1, 2017 2:36 PM
- Proposed as answer by TP []MVP Wednesday, February 1, 2017 2:36 PM
- Marked as answer by Sven_Willemen Wednesday, February 1, 2017 2:38 PM
Wednesday, February 1, 2017 10:21 AM

All replies

1

Sign in to vote

Hi,

NOTE: #5 below corrected the issue Sven was having, however, for future reference the other items are valuable for troubleshooting this error.

1. On the RDSH server that the user connects to, there should be a warning entry in System logfrom TerminalServices-RemoteConnectionManager around the time of the logon. Pleasedo a fresh test connection and then examine the specific RDSH server the user connected to for this entry and reply back.

2. In RDS deployment properties, RD Licensing tab, please make sure the correct FQDN for your RD Licensing server(s)are listed.

3. In RD Licensing Manager, does it show that you have2016 Per Device CALs available to be issued? Related, please check if the specific device you are testing from is listed in RD Licensing Manager as having been issued a temporary or permanentRDS CAL and if yes, is it still valid or expired?

4. Please make sure the RD Licensing service is Running on your RD Licensing server(s), and that there are no firewalls blocking communication between your RDSH servers and your RD Licensing server(s).

5. On the client PC, please rename HKLM\ SOFTWARE\ Microsoft\ MSLicensing key to MSLicensing.bak, open an administrator command prompt, and enter the following:

regsvr32 mstscax.dll

The above command will createa freshMSLicensing key and required subkeys/values. Please test connecting to the server from the workstation after recreating MSLicensing to see if Per Device RDS CAL is issued.

For reference, below is the English version of message:

Text version:

"Remote Desktop License Issue

There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes. Contact your system administrator to fix this problem."

Please reply back with your results/findings, whether positive or negative, and I will assist your further if needed.

Thanks.

-TP
- Edited by TP []MVP Wednesday, February 1, 2017 2:36 PM
- Proposed as answer by TP []MVP Wednesday, February 1, 2017 2:36 PM
- Marked as answer by Sven_Willemen Wednesday, February 1, 2017 2:38 PM
Wednesday, February 1, 2017 10:21 AM
0

Sign in to vote

Hi TP,

First: thank you

But to first answer your questions:

1. Event log on the RDS session host doesn't list the entry you are suggesting... in my case these are the logged entries on each login - there's no entry from:TerminalServices-RemoteConnectionManager

2. In my deployment properties i re-added both licensing servers with their FQDN (was NETBIOS-name listed) as you are suggesting.

3. I have added Per Device CALs on both licensing servers, licenses our now being issued:

4. The licensing service is running - i disabled the firewall just to be on the safe side. This is no issue currently because we are still building this farm.

I noticed something interesting though. I have a 'testrds' user. If i start a RDS session with the 'testrds' user from my own workstation, the blue error "Remote Desktop License Issue" pops up and no license is issued out for my workstation.

If i use the same user 'testrds' but start it from any other workstation, no blue error - and a license is issued out from RDS licensing.

Wednesday, February 1, 2017 1:53 PM
0

Sign in to vote

Hi,

On the workstation where it isn't working, do you HKLM\ SOFTWARE\ MSLicensing key with several subkeys as normal? If you want, as a test, you could rename the MSLicensing key to MSLicensing.bak, open an administrator command prompt, and run the following:

regsvr32 mstscax.dll

Once that is finished please test to see if you are able to connect and have a Per Device RDS CAL issued to the workstation.

Thanks.

-TP

Wednesday, February 1, 2017 2:10 PM
0

Sign in to vote

Hi TP,

I recreated the key with regsvr32 and no warning anymore if i start the rds session with the testrds user from my own workstation :)

The server is issueing a license, although a temporary.

Thank you.

With regards,

Sven

Wednesday, February 1, 2017 2:24 PM
0

Sign in to vote

Hi Sven,

Great! I will edit my original post to include the instructions for recreating the MSLicensing key. Please mark it as answer.

Thanks.

-TP

Wednesday, February 1, 2017 2:31 PM
0

Sign in to vote

Hello,

I have the exact same issue as Sven. I followed step no 5 as provided by TP (thanks).

Now the server is issueing a license, although a temporary... why would that be?

Thank you!

Monday, March 27, 2017 11:52 AM
0

Sign in to vote

Hello,

I have the exact same issue as Sven. I followed step no 5 as provided by TP (thanks).

Now the server is issueing a license, although a temporary... why would that be?

Thank you!

Hi,

First time you connect from a device, it is normal to get temporary license. Second time you connect from that device it should change to permanent.

-TP

Monday, March 27, 2017 12:14 PM
0

Sign in to vote

To view Terminal License Server on Windows 10, you can use Powershell

$a = gp "hklm:\SOFTWARE\Microsoft\MSLicensing\Store\LICENSE000" "ClientLicense"
$a."ClientLicense" | set-content c:\temp\Mylicense.p7b -enc byte

This document will explain how terminal license is distributed and why you connect the second time you will get the PERMANENT license

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=2ahUKEwjU04jehcDcAhWP_YMKHZmWCL8QFjACegQIAxAC&url=https%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F2%2Ff%2F2%2F2f2dc861-d567-4492-ae88-81afafa2d08d%2FTerminal%2520Server%2520Licensing.doc&usg=AOvVaw177x9I7u37V3qCkZvqK0bq

This document also shows you how to troubleshoot the Terminal License issue.

Johnathan Nguyen

Friday, July 27, 2018 8:05 PM
0

Sign in to vote

Executei os procedimentos acima e o erro ainda continua, o meu servidor não aparece no gerenciador de licenciamento, mas as licenças foram instaladas com êxito, o único servidor que aparece é um antigo que existe no dominio, mas com licenças windows server 2012 e preciso usar windows server 2016, já tentei de tudo e não consigo resolver, se alguém puder ajudar agradeço

Tuesday, January 8, 2019 6:13 PM

16 Replies

· · ·

Cayenne

Ken Carter

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

· · ·

Mace

Da_Schmoo

May 30, 2017 at 14:19 UTC

Microsoft Licensing expert

144 Best Answers

680 Helpful Votes

Server Manager, RDS, Edit Deployment properties - do you have your licensing server and mode defined here?

· · ·

Serrano

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.

· · ·

Mace

Da_Schmoo

May 30, 2017 at 14:30 UTC

Microsoft Licensing expert

144 Best Answers

680 Helpful Votes

I'd remove the entry for the non-domain joined licensing server.

· · ·

Serrano

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

· · ·

Mace

Da_Schmoo

May 30, 2017 at 14:40 UTC

Microsoft Licensing expert

144 Best Answers

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

· · ·

Serrano

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.

· · ·

Mace

Da_Schmoo

May 30, 2017 at 14:53 UTC

Microsoft Licensing expert

144 Best Answers

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

· · ·

Serrano

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/

· · ·

Mace

Da_Schmoo

May 30, 2017 at 19:52 UTC

Microsoft Licensing expert

144 Best Answers

680 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".

· · ·

Serrano

James8090 May 31, 2017 at 20:08 UTC

So nobody has any answers?

· · ·

Pure Capsaicin

DragonsRule

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?

· · ·

Serrano

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.

· · ·

Pure Capsaicin

DragonsRule

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.

· · ·

Serrano

James8090 Jun 13, 2017 at 19:42 UTC

No best answer. Fixed.

· · ·

Jalapeno

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!

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Not compatible with per-device CALs ^

Before you install the Web Client, you should make sure you use per-user client access licenses (CALs) and not per-device CALs. Otherwise the HTML client would seize all per-device CALs, since it is not compatible with this type of license. It will display a corresponding warning again during installation.

If an RD gateway is missing, the Web Client will refuse to establish a connection

As an additional requirement, the Remote Desktop Services (RDS) deployment must include an RD Gateway even for internal usage on Windows Server 2019, despite the fact Microsoft announced otherwise during the Windows Server Summit.

RD Web Client features and requirements

Installation via PowerShell ^

The RD Web Client is suitable for Windows Server 2016 and 2019, but Microsoft has yet to include it in the installation media of the operating systems. Currently it is not part of Server 2019 either.

The installation occurs via PowerShell's package management, which downloads the required packages from PowerShell Gallery. As a first step, you must update the PowerShellGet module not only on Server 2016 but also on Server 2019. The following command achieves this:

Install-Module -Name PowerShellGet -Force

Update the NuGet provider before installing the Web Client

At this point, it might be necessary to close the PowerShell window and start a new session.

The actual installation requires four commands as this tutorial on Microsoft Docs describes:

Install-Module -Name RDWebClientManagement Install-RDWebClientPackage Import-RDWebClientBrokerCert <.cer file exported from the RD Broker> Publish-RDWebClientPackage -Type Production -Latest

Install the Web Client using PowerShellGet

Please verify the certificate for RD Connection Broker - Enable Single Sign On (SSO). In the RDS deployment configuration, this must always match the certificate previously imported from RD Broker to the Web Client. So if you renew the certificate for RD Broker, you must reimport it to the Web Client.

The certificate for the Web Client must be the same as the certificate assigned for SSO in RD Broker

After successfully adding the package for the Web Client, you can access it via the URL https://<fully qualified domain name of the server>/RDWeb/webclient. This currently supports newer versions of browsers such as Edge, IE 11, Google Chrome, Safari, or Firefox, but not on mobile devices.