Rdp License Error
Contents |
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 problem: Eventually, you get an error that tells you that your Remote Desktop License will expire in "X" number no remote desktop client access licenses available for this computer of days. If you try to google a solution to this problem you'll be inundated
No Remote Desktop License Servers Available 2008 R2
with accusations that you're stealing the program and that you should go pay for a valid license. How can you be
Ms Licensing Registry Key
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
Hkey_local_machine\software\microsoft\mslicensing
Windows 7. Read below and follow the instructions closely:Click on the Start 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, remote desktop connection license expired 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 somewhat regular basis. I think I've got to do this about two to three times a year. 42 Responses to "Remote Server Licensing Fix" Kanchana May 14, 2012 at 5:35 am | PermalinkThis is not fixing my issue in windows 7. Brandon May 17, 2012 at 3:37 pm | Permalinkdidnt work for me either Kanchana May 22, 2012 at 8:06 am | PermalinkIs there any other fix available for windows 7 professional Jeff May 22, 2012 at 10:33 am | PermalinkHey guys. I used this fix when my office was running Microsoft Server 2000. I can vouch that it works with Windows 7 in this situation. I'm not sure if it works with any other versions of Server. We'v
indicating that no Remote Desktop license servers are available in Windows Server 2012. You may encounter the following error message when trying to connect to a Windows Server 2012 Remote Desktop Session remote desktop client access license stored on this computer has been modified Host (RDSH) server: The remote session was disconnected because there are no reset remote desktop licensing grace period 2008 r2 Remote Desktop License Servers available to provide a license. Please contact the server administrator. When this error appears, remote desktop license expired server 2012 no Remote Desktop connections may be made to the server. This error message may appear even if previous Remote Desktop connections to the server were successful and no recent changes were http://jeffpicard.com/blog/computer-fixes/microsoft-remote-desktop-licensing-fix/ made to the RDSH server. A hotfix is available for this issue. It may be download here. Additional Information: This information applies to Windows Server 2012. There is an alternative workaround for this issue. The first step in troubleshooting the issue should be to run the RD Licensing Diagnoser tool from Server Manager. This tool checks the existing Remote Desktop licensing configuration http://www.dell.com/support/article/us/en/04/SLN288851 for problems and provides troubleshooting suggestions for any that it finds. If the RD Licensing Diagnoser reports the correct licensing information and finds no problems, the issue may be caused by an apparent bug in Windows Server 2012 in which the RDSH server fails to contact the licensing server after the 120-day licensing grace period expires. If the licensing configuration appears to be correct and the RD Licensing Diagnoser reports no problems, perform the following steps: Open Registry Editor (regedit). Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM. Export this registry key to a file before making any changes. Locate the GracePeriod key and either delete or rename it. It may be necessary to take ownership of the key and/or modify its permissions first. Reboot the RDSH server. You should now be able to successfully connect to it. Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick
following error message with Remote Desktop ConnectionDesktop ConnectionDesktop Connection when you try to connect to a machine: “Remote session was disconnected https://community.spiceworks.com/how_to/40598-fix-remote-session-was-disconnected-because-there-are-no-remote-desktop-client-access-licenses because there are no Remote Desktop client access licenses available for http://www.thewindowsclub.com/remote-session-disconnected-no-remote-desktop-client-access-licenses 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 If it doesn’t work and you get the following error message: “The remote remote desktop computer disconnected the session because of an error in the licensing protocol“; 3 Still does not work? Then all you 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 no remote desktop 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 "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 c
No Remote Desktop client access licenses available RECOMMENDED: Click here to fix Windows errors and improve system performance Remote Desktop Protocol (RDP) basically helps us to connect two system at distant location. We've already seen how to enable, disable the Remote Desktop connection using RDP protocol. However, when you establish a Remote Desktop connection on Windows 8.1, 8, 7 or Vista operating systems, sometimes licensing errors may arise. Generally, in such cases, you're likely to receive following error: The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator. The root cause behind this issue is that the Terminal Server (TS) is not able to locate license server. Thus as a result of this, you received the message and are unable to bridge a Remote Desktop connection. If you face this problem on Windows Server, it is better to check if the license server is correctly installed, and Terminal Server Licensing service is running perfectly on it. If this doesn't helps, you need to follow these steps: Making mistakes while editing the Windows Registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point before proceeding. 1. Press Windows Key + R combination, type put regedit in Run dialog box and hit Enter to open the Registry Editor. 2. In the left pane of Registry Editor, navigate here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing Advertisement ^ 3. In the above shown window, right click on the MSLicensing key and select Export. This will let you to save this registry key in terms of registry file as a backup. Now right click same registry key and select Delete. Provide the registry key delete confirmation by clicking Yes option here: After deleting you must close Registry Editor and restart the machine. When next time, the Remote Desktop client is started, the deleted registry key will be rebuilt, consequently solving the problem. Hope this helps! RECOMMENDED: Click here to repair/restore missing Windows files & Optimize your PC Related Posts: Windows Registry Editor Tips & Features Enable, Disable Remote Desktop Connection in Windows 10/8.1 Set up & use Windows Remote Assistance in Windows 10/8.1 Microsoft Remo