Remote Desktop Licensing Manager
TEST YOUR SMARTS
Which of the following retains the information it's storing when the system power is turned off?
Submit »
88% of IT pros got this right.
Challenge
×
Get answers from your peers
along with millions of IT pros who visit Spiceworks.
Join Now
What an absolute nightmare to get support from Microsoft telephonically! We're a SPLA partner and our distributor gave us a telephone number but they lack english and ugh. We have Windows Server 2019 installed and want to have 7 RDP licenses on the device. I have gone ahead and installed RD Licensing Manager on the server as a feature. I went into RD Licensing Manager and we activated the server. After that, we setup a License:
The problem is that currently only 2 people can be logged in at teh same time. When a 3rd tries to log in via RDP, the session indicates that 2 people are logged in and 1 has to be booted. YOu then select the person to get disconnected and after some time you can be logged in. Based on the "Issued: 0" above, I believe that I am missing an additional step to get the licenses activated / issued on the server. I have repeated the steps plenty of times (have rebuilt the server and added additional licenses but nothing seems to work). Please can someone help :) When I call Microsoft they simply help you to activate the server but no support post that. I dont know if I need to do someone else to actually "assign" these licenses to the actual Windows Server 2019 server.
Best Answer
Chipotle
OP
PPC
Dec 2, 2019 at 09:42 UTC
The server needs to be a session host server. It sounds like what you have done so far is just install the licensing manager, that could be installed on any computer in the network and merely manages licensing for whatever machines your session host server(s) are on your network (the session hosts are the servers that many people will be actually logging in to at the same time, this can be the same as your licensing manager). Your server is only allowing 3 RDS connections because that's default and it's not a session host server.
View this "Best Answer" in the replies below »
10 Replies· · ·
Poblano
OP
mauzilla
Dec 2, 2019 at 09:23 UTC
We have restarted and still no luck. Must the server be on a domain to have multiple RDP connections? The client is breathing down our necks with this and I really dont have an answer and it seems that Microsoft cannot offer support post installing the license. the license has been reinstalled a number of times, I even disabled the firewall but its almost as if the local server does not recognise that the RD licensing manager server is active (or reading these licenses correctly).
0
· · ·
Poblano
OP
R.D.Pearson
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Just to confirm you have added the Terminal Services role? By default only two users can be connected unless TS role has been installed.
0
· · ·
Poblano
OP
mauzilla
Dec 2, 2019 at 09:36 UTC
I have checked now and cannot find the Terminal Services role in 2019. I have however gone ahead and installed the Remote Desktop Sessions Host role now. Is the role stillc alled "Terminal SErvices" in Windows Server 2019?
0
· · ·
Chipotle
OP
Best Answer
PPC
Dec 2, 2019 at 09:42 UTC
The server needs to be a session host server. It sounds like what you have done so far is just install the licensing manager, that could be installed on any computer in the network and merely manages licensing for whatever machines your session host server(s) are on your network (the session hosts are the servers that many people will be actually logging in to at the same time, this can be the same as your licensing manager). Your server is only allowing 3 RDS connections because that's default and it's not a session host server.
1
· · ·
Chipotle
OP
PPC
Dec 2, 2019 at 09:44 UTC
It's not called terminal services at all now but some bits and pieces of windows still reference the old naming (like tsclient and mstsc). It's all called RDS (Remote Desktop Services) now.
0
· · ·
Poblano
OP
mauzilla
Dec 2, 2019 at 09:58 UTC
I have "Remote Desktop Services" : Remote Desktop Licensing and Remote Desktop Session Host installed (2 of 6 installed) The server itself is not part of a domain. If I go to "Remote Desktop Services" under "Server Manager", I am told that I am currelct logged on as a location adminsitrator ont he computer. You must be logged on as a domain user to manage servers and collections". Does this mean that we cannot have 7 RDP licenses without a domain?
0
· · ·
Chipotle
OP
PPC
Dec 2, 2019 at 10:18 UTC
Domain is a requirement now, however if you are using device CALs you should be able to pull it off but you have to do a load of stuff manually. This shows how: https://ryanmangansitblog.com/2013/10/30/deploying-a-rdsh-server-in-a-workgroup-rds-2012-r2/
0
· · ·
Chipotle
OP
PPC
Dec 2, 2019 at 10:19 UTC
That guide is for Server 2012 but it should be roughly the same as 2019, there are a few small changes. Let us know if you run into problems anywhere.
0
· · ·
Poblano
OP
mauzilla
Dec 2, 2019 at 10:33 UTC
Thank you, got it working! For those in need (single server, no domain controller):
This worked for me, thank you all for your help above!
3
· · ·
Chipotle
OP
PPC
Dec 2, 2019 at 20:53 UTC
Very glad you are up and running and so quick. The post Terminal Services installation of RDS can be very confusing and counter-intuitive at the best of times.
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. |