If there isn't a server-side solution (or avoidance mechanism), there should be, given the only variable in this equation is the server. many thanks Peter November 7, 2011 at 9:00 pm This still doesn't work. June 30, 2016 Safari Running Slow on iOS10 - Fix June 29, 2016 HOT NEWS Computer Tips And Tricks Save webpage to PDF in Google Chrome Iphone iPhone stuck on Apple Checked the problematic machine (thin client). this contact form
Microsoft needs to address this issue! Anyway, I'm not absolutely convinced this is the only solution, even if it is functional; hence the 'good' versus 'great' rating. 0 LVL 59 Overall: Level 59 Windows Server 2008 Re-run Remote Desktop Connection a. So I exported them from an XP machine but it won't import the keys.
I had to launch as admin, otherwise it didn't work after deleting the key." I remember I did this a year ago on one machine... BTW the key was recreated (didn't show up immediately). --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis Marked as We have home users which are experiencing this issue in addition to those which we have direct control over. Worked fine.
Thanks for the info. Shutdown and restart Windows XP. If running Windows 7 or Vista, you must right click on the Remote Desktop Connection shortcut and choose “Run as Administrator” b. The Remote Session Was Disconnected Because License Store Creation Failed With Access Denied Thanks again. 0 LVL 59 Overall: Level 59 Windows Server 2008 47 Remote Access 6 Internet Protocols 5 Message Expert Comment by:Darius Ghassem2012-10-05 The Licensing are stored on the client.
We've already discussed one of the regular problem: "The Remote Computer Disconnected the session because of an error in the Licensing protocol". […] LEAVE A REPLY Cancel reply STAY CONNECTED1,041FansLike APLICATIONS The Remote Computer Disconnected Session Licensing Protocol Windows 7 Microsoft Customer Support Microsoft Community Forums ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: http://0.0.0.3/ Connection to 0.0.0.3 failed. I don't have any other Vista machines in the building to export the key from. I was searching and performing all the available solutions but all in vain from deleting the registry up to importing registry files from other PCs.
This worked for me. Remote Session Was Disconnected Because There Are No I have to do this every 90 days because we don't have control over the firewall. This is a small mess that might grow larger as more users make attempts to connect to the new server. The only solution was to RDP to a Terminal Server on the same side of the firewall, log off and get a temporary CAL.
regards arasssen JT April 29, 2010 at 10:00 am thanks all, these solved the problem I faced. https://community.spiceworks.com/how_to/84081-the-remote-computer-disconnected-the-session-because-of-an-error-in-licensing-protocol I did find a solution though. The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 That should help if you are on Vista. Change The Terminal Server Licensing Mode From Per Device To Per User We have 4 other TS users, neither of whom are having any problem connecting. "The remote computer disconnected the session because of an error in the licensing protocol Please try connecting
Well, that's easy, I walked her through and successfully deleted the MSLicensing registry key on her Windows Vista computer, and happily told her you can try it again now. http://supercgis.com/licensing-protocol/remote-computer-disconnected-session-because-error-licensing-protocol-windows-7.html I'm simply unsatisfied with the state of affairs as it relates to this situation. 0 LVL 59 Overall: Level 59 Windows Server 2008 47 Remote Access 6 Internet Protocols 5 If in case you still face problems, especially because of registry key, the you can overwrite the new registry setting with your old one, since you would have taken a backup. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing 3. Licensing Protocol Error Remote Desktop Windows Server 2008
Worked for both my Win7 and my Vista computers. Again there are ways to deploy different ways of of the solutions I provided. haydee February 28, 2010 at 9:09 am I deleted my MSlicensing from my laptop computer in error…please help I have windows XP and have been trying to get this back, I navigate here Never would have guessed this.
Running Vista SP2. Then connected as standard user. If you continue to receive this error message, contact the server administrator" Well here's the solution to fix this problem: This actually is a registry fix. Mslicensing Key It worked. 2.
Some posts above suggest running IE as adminstrator, but it is the "Remote Desktop Connection" program that needs to be run as Administrator in order for the registry keys to be peter majors July 7, 2011 at 8:52 pm No luck on this, followed instructions exactly. Chass Gautam November 12, 2009 at 2:35 pm @Ramu - welcome ramu ramu November 12, 2009 at 11:14 am thank u bozz Gautam October 30, 2009 at 5:11 pm @Matt - his comment is here all of them about the same: "Just delete the "HKLM\Software\Microsoft\MSLicensing" registry key...then launch remote desktop using "Run as Administrator".
Giving a lower grade on a solution that worked but didn't meet your expectation of a solution that currently is not feasible because of limitation of the OS and how it The client will try to obtain a new license from the server the next time that it connects." Just worked for me…Hope this helps some Santosh April 20, 2010 at 11:13 I am trying to connect using Windows 7 home laptop to our office server. it works fine for me.
Delete the old HardwareID-temp and Store-temp and close the registry editor. Solved The remote computer disconnected the session because of an error in licensing protocol Posted on 2012-10-05 Internet Protocols Windows Server 2008 Remote Access 1 Verified Solution 12 Comments 3,919 Views and both we access thru remote desktop, while one server we were able to connect thru remote desktop, another server we getting that error. Removed MSLicensing key, did not recreate itself.