none
RDS 2016 - Licensing Issue - Per Device - Warning at user logon RRS feed

  • Question

  • 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

  • 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 log from TerminalServices-RemoteConnectionManager around the time of the logon.  Please do 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 have 2016 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 permanent RDS 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 create a fresh MSLicensing 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  


    Wednesday, February 1, 2017 10:21 AM
    Moderator

All replies

  • 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 log from TerminalServices-RemoteConnectionManager around the time of the logon.  Please do 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 have 2016 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 permanent RDS 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 create a fresh MSLicensing 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  


    Wednesday, February 1, 2017 10:21 AM
    Moderator
  • 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
  • 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
    Moderator
  • 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
  • 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
    Moderator
  • 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
  • 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
    Moderator
  • 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
  • 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