2012 RDS Remote Desktop Licensing Service issues
Hello Experts,
We have a 2012 R2 RDS environment. The licensing role is installed on the same server as gateway and RDWeb roles. We have been having many errors in the event logs of session host and licensing server.
On session host, we get:
Event ID 1061 "Remote Desktop Session Host server was unable to retrieve users Licensing information from AD. Error 0x8007054b"
and
Event ID 1131 "The Remote Desktop Session Host server could not contact the Remote Desktop license server licenseservername.domain.l
On the license server the event log shows the events of:
Event ID 4105 "The Remote Desktop license server cannot update the license attributes for user "username" in the Active Directory Domain "domain.local". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "domain.local".
I have added the license server computer account to the Terminal Server License Servers group. When I run the RDS Licence Manager it shows green, and 50 per user CALS available, none in use.
When I run the licensing diagnoser on the session host, it shows green as well and lists the licesne server.
However, We still get the events, and there is a technet article instructing to restart the Remote Desktop Licensing service on the license server, but the services does not exist.
Also, licensing manager show 50 per user CALS available and none in use.
Thanks in advance for the advice.
We have a 2012 R2 RDS environment. The licensing role is installed on the same server as gateway and RDWeb roles. We have been having many errors in the event logs of session host and licensing server.
On session host, we get:
Event ID 1061 "Remote Desktop Session Host server was unable to retrieve users Licensing information from AD. Error 0x8007054b"
and
Event ID 1131 "The Remote Desktop Session Host server could not contact the Remote Desktop license server licenseservername.domain.l
On the license server the event log shows the events of:
Event ID 4105 "The Remote Desktop license server cannot update the license attributes for user "username" in the Active Directory Domain "domain.local". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "domain.local".
I have added the license server computer account to the Terminal Server License Servers group. When I run the RDS Licence Manager it shows green, and 50 per user CALS available, none in use.
When I run the licensing diagnoser on the session host, it shows green as well and lists the licesne server.
However, We still get the events, and there is a technet article instructing to restart the Remote Desktop Licensing service on the license server, but the services does not exist.
Also, licensing manager show 50 per user CALS available and none in use.
Thanks in advance for the advice.
ASKER
Rebooted both servers, the error went away on the licensing server.
I still have the same events mentioned above on the session host for certain periods, this morning for about an hour. Connectivity is good, I have set up ping plotter from session host to licensing server and DC to keep track of connectivity so I can compare to logs if there is actually an issue between the servers.
As for the licensing server, it is set to per user CALS and so is the RDS session host. Still we are not showing any licenses in use, there are still 50 licenses available.
I still have the same events mentioned above on the session host for certain periods, this morning for about an hour. Connectivity is good, I have set up ping plotter from session host to licensing server and DC to keep track of connectivity so I can compare to logs if there is actually an issue between the servers.
As for the licensing server, it is set to per user CALS and so is the RDS session host. Still we are not showing any licenses in use, there are still 50 licenses available.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes I am sure it is missing. I will remove / re-add the role and see if it resolves things.
RD Licensing Manager --> R.Click server name --> Review Configuration
Do you see:
EDIT: In Server Management --> RDS --> RD Licensing (is this set up?)
Then, use Deployment Properties to set the RD Licensing Server.
Do you see:
EDIT: In Server Management --> RDS --> RD Licensing (is this set up?)
Then, use Deployment Properties to set the RD Licensing Server.
Did you check the discovery scopeof terminal services and permission in ADDS..?
ASKER
Phillip,, yes I see those green checks as well, and yes it is configured as license server in deployment properties.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys, this is my plan but I cannot do so until a maintenance window next week, as I do not want to disrupt production, in case it requires a reboot between or after removal and reinstall. I will keep you posted once I can get the role reinstalled.
Good plan. Not sure if a reboot is needed or not but plan for one anyway.
ASKER
I will not be able to try this fix any time soon, the server is in production and we have a very small maintenance window once a month. These three experts recommended a reinstall of the RD Licensing role, which I will attempt. Due to Experts Exchange claiming this ticket "Abandon" after only a few days, I am marking as resolution, as I believe it will fix the issue. If not I can open a new topic.
Check, the host server can ping the licensing server by name, IP & FQDN just to rule out communication issues. Also check you have the license & host set to the same licensing mode (user or device)
Assuming they are OK I'm a little confused as the events on the license server should have stopped when you added it to the right group. try a reboot just to rule it out but then start by checking the server is picking up the right groups and GPOs. try running a Gpresult to confirm the server picks up the right groups etc.