windows-7 windows-vista remote-desktop terminal-services share|improve this question asked May 9 '12 at 14:54 just.another.programmer 3802719 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote accepted The Claudius August 14, 2012 at 8:37 am | PermalinkProblem fixed! Please if u can tell m the right solution. You'll be prompted to delete a few keys and subkeys and hence it's better if you take a back up of your registry manually, so that you can restore it if this contact form
Reply Sarah says: June 9, 2010 at 10:58 am Worked like a charm! Rebooting will create new Keys under HardwareID and Store and this will fix your problems. 5> If you had renamed the keys and subkeys instead of deleting them, navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing The issue is that when imaging these thin clients, one does not want to duplicate the MSLicensing key data from terminal to terminal, so the thin client manufacturer "Wyse" instructs us Short URL to this thread: https://techguy.org/1002377 Log in with Facebook Log in with Twitter Log in with Google Your name or email address: Do you already have an account?
kimi September 8, 2015 at 11:23 pm | Permalinkif u using windows 2012simple.. Shivaditya October 22, 2012 at 2:35 am | PermalinkDears, If facing issue in Windows 7 try this registry setting changes in Local machine not on server or system.Windows Registry Editor Version Thank you Thank you Thank you 🙂 Reply TheQuestor says: March 15, 2010 at 1:04 am You sir are a god.
Still same error. I have had this problem now on multiple computers and everything says to delete the regkey mslisencing wich did not fix the error. boogey July 6, 2016 at 5:41 pm | PermalinkWindows 2012 server. Mslicensing Registry Key Missing I log into their VPN, then RDC.
Forum SolvedRemote desktop computer seems to sleep/idle several minutes after i disconnect Forum Task Scheduler: "The remote computer was not found" error Forum can't do anything with computer but loop because The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 I don't have any other Vista machines in the building to export the key from. I did the run as admin and it still won't work. his explanation I would like not to have to manually execute mstsc.exe as an Administrator on all of our newly purchased thin clients.
Powered by WordPress.Options Theme Licensing Protocol Error Remote Desktop Windows Server 2008 Also, you receive the following error message: An Error occured in the licensing protocol. The fix is basically the same for Windows XP through Windows 7, though Vista/7 may require one more step. They said then I am not an administrator.
Was going crazy looking at all the possible server-side issues. http://superuser.com/questions/422455/how-to-reset-rdc-client-license-on-windows-7 I appreciate you sharing your knowledge! The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol Windows 7 Just what I was looking for. The Remote Computer Disconnected Session Licensing Protocol Windows 7 Gautam February 28, 2010 at 10:33 am @Haydee - If you've followed all steps mentioned in the post, you should have a new MSLicensing key created when you restart your system.
Try our newsletter Sign up for our newsletter and get our top new questions delivered to your inbox (see an example). weblink regards, swapnil Tricky November 24, 2010 at 8:27 pm I had the same RDP problem but on a Windows 7 machine. thanks. Click here to join today! Change The Terminal Server Licensing Mode From Per Device To Per User
Thanks !!!!!!!!!!!!! users can only log onto one of them and everyone gets the message when trying to connect to the other... After you delete the REG key run RDC as administrator. navigate here Liger August 4, 2010 at 12:02 am @Joe I had this problem on windows 7 and I run as admin and recreated the deleted keys.
But after doin the above steps still getting same error. Mslicensing Key hondafrank, Jun 15, 2011 #6 barrypatch Thread Starter Joined: Sep 10, 2004 Messages: 190 "The remote session was disconnected because there was an internal error in the remote computer's licensing protocol." Thread Status: Not open for further replies.
If there is an error in the licensing protocol, your computer cannot be connected to the remote computer. This causes a silent failure with the error message "problem in licensing protocol". (Ideally, the program would be redesigned to display a UAC challenge prompt in this situation). Fire November 16, 2010 at 7:18 pm In Windows 7 it's really important that you start the remote desktop session after deleting the registry key "as Administrator". Mslicensing Key Not Rebuilding Monday, September 23, 2013 6:26 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site.
They haven't upgraded to 7 yet, so I keep one laptop with VISTA just to do work for them. I might be crazy, but I was thinking the problem at to be on their end. what about this??? his comment is here The software should regenerate the keys and you will see the login screen Hassan December 20, 2010 at 6:00 pm Hi, I hade the same problem: This solv my problem.
Joe May 31, 2016 at 2:39 pm | PermalinkThanks mate. Someone told me to delete the RDC files on my MAC and that would solve the problem. Once you have taken the back up, 1> Click on Start Menu -> Go to Run Command box -> Type regedit -> This opens the registry Editor. 2> Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing Justin July 11, 2012 at 1:55 am | PermalinkThank you :) this fixed my issue…..
At the very bottom of this KB, it mentions: If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect NicNick Laurino Wednesday, April 07, 2010 2:04 PM Reply | Quote 1 Sign in to vote Hello Nick, On the Windows Vista and Windows 7 clients, please backup and remove Rogalik July 13, 2011 at 6:29 pm After the MSLicensing removal you must start mstsc as the administrator for the reconstruction of keys. Create a new local administrative user and try with that.
This was the key for me. This did the trick!