Secondstreet
asked on
Remote desktop licensing not available, Server 2012
Hey all,
I have a terminal server in Windows Server 2012 that the 120 grace period expired for licenses. I had setup the license server on the same server, it's a domain member/system, and installed the licenses (50). For some reason, on boot, the server has:
The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.
And it will not allow remote desktop users to connect, stating that their isn't a license server available. I've gone into License manager, verified the server is activated and working. I can ping the license server by the FQDN I'm using.
In licensing diagnosis, it says the server is up, the licenses are available, and it can't find any problems.
When I try to connect a remote desktop I get an event log warning:
The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.
Funny, because the Remote Desktoop Session Host Config tool doesn't exist in 2012. Argh! Help!
I have a terminal server in Windows Server 2012 that the 120 grace period expired for licenses. I had setup the license server on the same server, it's a domain member/system, and installed the licenses (50). For some reason, on boot, the server has:
The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.
And it will not allow remote desktop users to connect, stating that their isn't a license server available. I've gone into License manager, verified the server is activated and working. I can ping the license server by the FQDN I'm using.
In licensing diagnosis, it says the server is up, the licenses are available, and it can't find any problems.
When I try to connect a remote desktop I get an event log warning:
The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.
Funny, because the Remote Desktoop Session Host Config tool doesn't exist in 2012. Argh! Help!
Cliff Galiher
The session host does not find the licensing server automatically, even hen it is on the same install. You must use server manager, edit the session host properties, and poi t it at the licensing server
ASKER
I've already done that. It is set correctly, I've tried two different licensing servers. I've set this up on other Terminal Services machines without a problem.
I've seen this happen on a 2012 RDSH server, even though it appeared that everything was set up correctly. I never determined the root cause, but if I recall, configuring licensing via Group Policy worked. The settings are located at Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing. Feel free to configure it in the server's local policy if there's only one RDSH server and you don't want to create/modify a GPO.
ASKER
Unfortunately, I've tried that workaround as well without any luck. Thanks for the suggestion though. I have a case open with Microsoft, I'll post what they say.
I'm going through the same situation currently with Microsoft support.
Is there anything that you could report?
https://www.experts-exchange.com/questions/28035739/Remote-Desktop-Services-Windows-Server-2012-Role-cannot-be-added-to-Server.html
Is there anything that you could report?
https://www.experts-exchange.com/questions/28035739/Remote-Desktop-Services-Windows-Server-2012-Role-cannot-be-added-to-Server.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I actually did that in the registry and it didn't fix it. I eventually made a static DNS entry in the hosts file to the license server... and it seemed to fix it. Thanks for the help dosh, all good responses and things to try, to fix.
FYI - I have had this happen to me twice with new server 2012 RDS servers where they were configured and showed no errors with licensing. After the 120 days they gave the exact same issues. I had MS fix the one, and this thread helped with the other. I would advise watching any RDS Servers you set up right around the 120 day mark...