How to license RDS for 2012R2 using workgroup?

Question

RDP

Good afternoon!
Help, please, deal with the licensing of the terminal server on Windows Server 2012R2. We do not use a domain, but use a workgroup, because there are two servers in the network and if one of them fails, you can easily switch to the other. We don't have a sysadmin , so it's easier for us :)
One of the servers runs Windows Server 2003 and we don't touch it.
On the second, they did this:
1. Installed Windows Server 2012R2, licensed it.
2. Bought "per user" licenses for RDS.
3. Installed and licensed the terminal server approximately according to this instruction .
We got this:
4. Some time has passed, apparently, the terminal server licensing test period has ended, and when we tried to connect, we saw this:
5. After reading the Microsoft forums , we deleted the HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Grace Period
6 registry key Everything seemed to work
7. After some time, this key appeared in the registry again, and the remote desktop licensing manager still looks like this:
That is, the "per user" licenses we bought were never activated, and it looks like , by deleting the Grace Period key of the register, we simply reset the RDP test period timer, and now we are connecting, obtaining test licenses "per device".
Apparently, soon the test period will end again and we will again get a connection error?
What can we do to make it all work properly?
Is it possible to license a terminal server using a workgroup and not a domain?
Thanks for reading! :)

Answer 1

Delete the HKLM\SOFTWARE\Microsoft\MSLicensing registry key on the client
for x64
HKLM\SOFTWARE\Wow6432Node\Microsoft\MSLicensing
The problem has been known since the shaggy year, googled by the text of the error.
The error occurs due to the fact that the RDP client saves information about the license server in this branch, if the old license server has become unavailable, then after some time the client starts to swear with such an error.
You can safely delete it, after a reboot and the next connection, the branch will be recreated with updated information.