Microsoft Terminal Server Licensing Error
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server
No Remote Desktop Client Access Licenses Available For This Computer
and Tools Blogs TechNet Blogs TechNet Flash Newsletter ms licensing registry key TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals
Hkey_local_machine\software\microsoft\mslicensing
Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2016 System Center reset remote desktop licensing grace period 2008 r2 2016 Windows 10 Enterprise SQL Server 2016 See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL remote desktop connection license expired Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Remote Desktop Services (Terminal Services) Remote Desktop Services in Windows Server 2008 R2 Troubleshooting Troubleshooting Remote Desktop Licensing Issues Remote Desktop Licensing Issues Remo
Fixes / Remote Server Licensing Fix Remote Server Licensing FixIf you use Microsoft's Remote Desktop connection on a regular basis, there's a pretty good chance you've run into this
Mslicensing Registry Key Missing
problem: Eventually, you get an error that tells you that remote desktop client access license stored on this computer has been modified your Remote Desktop License will expire in "X" number of days. If you try to google
Mslicensing Regedit
a solution to this problem you'll be inundated with accusations that you're stealing the program and that you should go pay for a valid license. https://technet.microsoft.com/en-us/library/hh553162(v=ws.10).aspx How can you be stealing something that is included with most modern versions of the Windows operating system? Without going into just why this happens, the solution is actually pretty easy. The following procedure is for either Windows Vista or Windows 7. Read below and follow the instructions closely:Click on the Start http://jeffpicard.com/blog/computer-fixes/microsoft-remote-desktop-licensing-fix/ button and in the search box type "regedit" (without the quotes)The Regedit program should be highlighted at the top of the start window. Either simply hit ENTER, or double click it.In Regedit, navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensingRight click on the key name "MSLicensing" and select DELETE.Close RegeditDo NOT open any shortcuts for Remote Connections at this point. Instead, you need to open the Remote Desktop Connection Manager. It's VERY important that you do this by RIGHT clicking on the program and selecting "Run as administrator." If you don't do this properly, the registry key you deleted in step 4 will not be recreated. The Remote Desktop Connection Manager can be found at: START/All Programs/Accessories/Remote Desktop Connection.Select the remote connection you want to use and click "Connect." If you've done this properly, a new registry key will be added that will have updated licensing information.This fix will need to be redone on a som
following error message with Remote Desktop ConnectionDesktop ConnectionDesktop Connection when you try to connect to a machine: “Remote session was disconnected because there are no Remote Desktop client access licenses available https://community.spiceworks.com/how_to/40598-fix-remote-session-was-disconnected-because-there-are-no-remote-desktop-client-access-licenses for this computer. Please contact the server administrator“ Steps (3 total) 1 The solution is delete the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing The solution is delete the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing 2 Try connecting in again http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ If it doesn’t work and you get the following error message: “The remote computer disconnected the session because of an error in the licensing protocol“; 3 Still does not work? Then all you remote desktop need to do is Right-Click on the Remote Desktop Connection icon and select “Run as Administrator“. References Fix – Remote session was disconnected because there are no Remote Desktop client access licenses 26 Comments Mace hsc5775 Jun 19, 2013 at 07:00am #3 The "Run as Administrator" option is always a good trick. thx for share Sonora Moree Aug 5, 2013 at 02:49am Thanks! Its perfectly work with remote desktop client "Run as Administrator" step. This trick seems like a joke from Microsoft to IT support. A good start on this beautiful Monday. Chipotle Guy 6779 Jan 23, 2014 at 12:24am I know it's a pretty easy fix, what i want to know is what causes the issue ? Pimiento Sludg3 May 13, 2014 at 12:56pm Hi guys , under MS licensing i have HardwareID and Store sub folders , should i remove these too? Tabasco WouterNel May 13, 2014 at 01:20pm Delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing and all its contents. When you reconnect with RDP the key will be recreated! Pimiento jeremy63 Jul 30, 2014 at 12:57pm Should I delete the registry key on the server side, or on the client's computer that connects to the server? Tabasco WouterNel Jul 31, 2014 at 08:36am jeremy63, Only on the client computer and then run RDP as Administrator. Pimiento toyinfolarin Sep 3, 2014 at 12:11pm hi guys, i tried out these options listed (HKEY deletion and running as administrator), i couldnt connect still to the WMS 2012 running on the server machine. could this be because i was not able to promote the server to a domain controller? or what
functional and activated 2012 Remote Desktop Session Host server displayed the following message: This was a simple setup on one server with the: connection broker, Session Host and Licensing server with 2012 CAL's installed. Even though the licensing seems to be configured correctly, in server manager: and powershell: Licensing diagnostics: everywhere you look, everything seems to be OK. But the license manager shows something odd: No licenses are being used? This server was used since late 2012. Some interesting things could also be found in the event logs, the following events appear: EventID: 1130 Source: TerminalServices-RemoteConnectionManager 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. and: EventID: 1128 Source: TerminalServices-RemoteConnectionManager 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. The solution was to delete the REG_BINARY in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod Only leaving the default. Note: you must take ownership and give admin users full control to be able to delete this key. After a reboot the server should be working again, licenses are now being used: Although everything seemed to be ok and configured correctly with valid licenses, it seems that the setup was still in a 180 day grace period, even though it was correctly configured. A possible bug in RDS 2012? This entry was posted in Remote Desktop. Bookmark the permalink. ← UTMv9 Reserve node feature in HA Bing → 142 Responses to No remote Desktop Licence Server availible on RD Session Host server 2012 Sean says: April 20, 2013 at 14:03 Works thanks for the write up! Reply ankush says: January 30, 2015 at 07:29 if i do so is there any discrepancy happening,pls suggest Reply ankush says: January 30, 2015 at 07:32 if i delete this key is there any negative impact on my netywork or do i need to take a backup ofr the same. Reply Eric Verdurmen says: February 2, 2015 at 07:47 I haven't encountered a single issue, but is it's always wise take a snapshot or make a backup before making this change. Reply Bryan says: February 5, 2015 at 03:23 It