- #Server 2012 terminal services manager missing license#
- #Server 2012 terminal services manager missing windows#
You may need to take inventory of your session hosts and ensure that they are pointed to your 2012 / 2012 R2 license server if they aren't already pointed to it. This should effectively do the same thing as rebuilding the license database, but I mention it because it was successful in at least one case.įinally, when you decommission your old 2008 R2 server, be sure to think through what that will entail for your session hosts.
In one case, a customer had to rename the "C:\Windows\System32\Lserver" folder, uninstall the RDS roles, reboot, and reinstall the RDS Licensing role in order to get the service to start again. After this, you will need to have your Retail CAL pack or your EA information in order to reinstall your licenses. Select Rebuild the license server database.ģ.
Open your RD Licensing Manager, right click on your server and select Manage Licenses.Ģ. Be sure you have your licensing information.ġ. If you do this, you will have to re-install your licenses after the rebuild. If this happens, you can rebuild the database using the "Manage Licenses" wizard. In this case, the licensing server database had become corrupt. We have seen at least one case where the 2012 License Manager Service still did not start even after removing the 2008 R2 License server. If you still want to have two or more license servers, you will need to build another matching 2012 / 2012 R2 license server. If you are moving to a 2012 / 2012 R2 environment, then deactivate and decommission your 2008 R2 license server.
#Server 2012 terminal services manager missing windows#
I am being told this is not an option on Windows server 2016. I could see who was logged into each server, when they logged, I could send them a message, and even remote into their session, if needed. You cannot have a 2008 R2 and a 2012 / 2012 R2 License server in the same RDS environment. I was using the mmc.exe with the Remote Desktop Services Manager snap in. In fact, every time you try to start the service, it starts for a short time and then stops on its own.Īlternatively, you may see this service crash. You try to start it again, but after a short period of time (30 seconds to a few minutes) it stops on its own again. When you look under services.msc, you notice that the Remote Desktop Licensing service is stopped on the 2012 / 2012 R2 server. You have both a 2008 R2 and an 2012 or 2012 R2 Licensing server in your RDS environment. Hello AskPerf! My name is Matt Graham and I'll be discussing an issue that you may see on your RDS Licensing Server. First published on TECHNET on Sep 24, 2015
0 kommentar(er)
