Mstsc License Protocol Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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 Answered by: Remote Desktop Licensing Protocol error Windows
The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008
Server > Remote Desktop Services (Terminal Services) Question 0 Sign in to mslicensing key vote I have spent the last 4 hours looking for solution online including Microsoft sites.So unless you have an mslicensing registry key missing EXACT match ofsolution to problem DO NOT tell me toTRY this or that in any article as I have probably already read it or tried it. OK onto the issue. Brand new
The Remote Computer Disconnected Session Licensing Protocol Windows 7
2008 R2 SP1 standard Dell server. All updates applied. Joined as a stand alone server to domain. Remote desktop role installed. License server role installed. License server activated. 10 Per User RD (open License) Cals installed. Remote Desk Host Diagnostics gives clean bill of health. No other roles etc. installed. This is strictly a TS server. Workstations are Wyse thin clients running Windows
Hkey_local_machine\software\microsoft\mslicensing
7 Embedded. They can see all allowed resources on domain. they can get to the internet as well. network connectivityand navigation confirmed. So.... When I start up RDP client on said terminals I get error of:The remote computer disconnected the session becase of an error in the licensing protocol. Remeber this is a Windows 7 embedded. hacks to registry or file copy from other OSes do not apply. And yes I checked with Wyse support. other Misc data: No firewall activated on server using the administrator account to attempt logon as it is already included in group. (Should not matter as it is a LICENSING PROTOCOL error anyway) It is part of a 2003 domain. No I have not edited GP on 2003 system. Yes the event log has been reviewed. I see NO entries for this issue. IDEAS????? Thursday, May 19, 2011 6:39 PM Reply | Quote Answers 1 Sign in to vote Issue Resolved. With Windows 7 the security settings for a regular user are severe. What would have worked for Vista and previous will not work with Windows 7. To
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 of days. If you try to google change the terminal server licensing mode from per device to per user a solution to this problem you'll be inundated with accusations that you're stealing the program and
Remote Session Was Disconnected Because There Are No
that you should go pay for a valid license. How can you be stealing something that is included with most modern versions of the remote session was disconnected because license store creation failed with access denied 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 button https://social.technet.microsoft.com/Forums/windowsserver/en-US/d64d00c4-c87b-4af6-83b5-54daf2c82938/remote-desktop-licensing-protocol-error?forum=winserverTS 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 http://jeffpicard.com/blog/computer-fixes/microsoft-remote-desktop-licensing-fix/ 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've upgraded to Server 2003 and this error no longer seems to be a problem (**UPDATE: It's STILL a problem**). All I can say is to make sure you follow the instructions to the letter. It's VERY important that you r
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://serverfault.com/questions/54893/remote-desktop-to-win-2008-error-in-license-protocol Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted the remote up and rise to the top Remote Desktop to Win 2008: Error in License protocol up vote 0 down vote favorite I am sitting on a Win XP machine trying to connect to a Windows 2008 Server. I think the cause of this issue might be due to the fact that I said yes to install a terminal server back when I installed the server as I didn't the remote computer know it wasn't nessecary for RDP. I don't know if this i9s what is blocking the connection but something is. The error message (translated from danish): "The remote computer disconnected the session due to an error in the licensing protocol. Try again or contact serveradministrator." Now the real issue here is that I can't remote desktop and fix the error. I have also tried: mstsc -console without any luck. Any suggestions are welcome :) windows windows-server-2008 share|improve this question asked Aug 17 '09 at 9:10 user16966 11615 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote You can try rebooting the server, but you'll need to check on the license server to see if there are any errors. If you installed Windows 2008 in Terminal Server mode you'll need to get on the server and remove Terminal Services in order to get the admin RDP working again. You probably don't have any Terminal Service licenses to use. share|improve this answer answered Aug 17 '09 at 9:21 mrdenny 25.4k33163 add a comment| up vote 0 down vote If you don't install a Terminal Licencing Server within 120(?) days of installing the Terminal Server service, Terminal Services will ce