License Protocol Error Terminal Server
Contents |
360 games PC games
The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol Windows 7
Windows games Windows phone games Entertainment All Entertainment no remote desktop client access licenses available for this computer Movies & TV Music Business & Education Business Students & educators the remote computer disconnected the session licensing protocol windows server 2008 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Mslicensing Registry Key Missing
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Hkey_local_machine\software\microsoft\mslicensing
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked mslicensing key not rebuilding by: Licensing Protocol Error using RDP Web connections Windows Server >
The Remote Computer Disconnected Session Licensing Protocol Windows 7
Remote Desktop Services (Terminal Services) Question 0 Sign in to vote We have several clients receiving errors change the terminal server licensing mode from per device to per user after we replaced our TS License server when trying to connect through RDP Web connections. I have been able to fix all of the XP users by deleting https://support.microsoft.com/en-us/kb/187614 the HKEY_Local_Machine\Software\Microsoft\MSLicensing sub-key as mentioned in several documents, but this does not work with all Vista or any Windows 7 machines. We have many remote users with mixed clients and some are 32 BIT some 64BIT Vistal and Windows 7. I did find information on running IE as an administrator and this only works on a https://social.technet.microsoft.com/Forums/windowsserver/en-US/8346736c-e0b5-429b-a0ab-ec43b393551d/licensing-protocol-error-using-rdp-web-connections?forum=winserverTS per session basis. That is not acceptable since a lot of our users are not administrators nor can use admin credentials on company computers. Although it does recreate the MSLicensing key, it will still give the error after that if used normaly from a shortcut created to the RDP Web server. Any help will be appreciated since this is causing major issues for several remote clients. NicNick Laurino Wednesday, April 07, 2010 12:12 PM Reply | Quote All replies 0 Sign in to vote After changing our TS License server, All of our clientswere receiving"The remote computer disconnected the session because of an error in licensing protocol" when trying to access our Windows 2003 Terminal Server using RDP Web. All theinformation I could find indicated thatdeleting the sub keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing keyshould resolve this issue (the applies to was for Windows XP). I did this on several Windows XP clients and it workedokay but, I tried it on a Vista and Windows 7 without any luck
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 http://jeffpicard.com/blog/computer-fixes/microsoft-remote-desktop-licensing-fix/ expire in "X" number of days. If you try to google 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. 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 the remote easy. The following procedure is for either Windows Vista or 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 the remote computer 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 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