Home > Licensing Protocol > Remote Desktop Disconnected Error In The Licensing Protocol

Remote Desktop Disconnected Error In The Licensing Protocol


I am having the same problem, but on some newly purchased Windows Embedded Standard 7 thin clients. Friday, August 05, 2011 5:05 PM Reply | Quote 1 Sign in to vote Ideleted the MSLicensing key (HKLM\SOFTWARE\Wow6432Node\Microsoft\MSLicensing) on a 64bit Windows 7 pc, then ran mstsc as administrator. On one of the Vista 32 BIT machines, the RDP Web connection is working okay, but there are no sub-keys below the HKLM\SOFTWARE\Microsoft\MSLicensing key such as Hardware or Store. JoinAFCOMfor the best data centerinsights. http://supercgis.com/licensing-protocol/remote-desktop-disconnected-licensing-protocol-error.html

Note: You only need to this the first time. And yes, Microsoft now has it's own all-in-one. It worked without me editing the registry or anything else. JSI Tip 8247. http://www.networknet.nl/apps/wp/archives/2221

The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008

Log In or Register to post comments klimenta on Dec 19, 2008 I had the similar problem where the terminal server was behind the firewall and only RDP ports were open. Regards, Zain Reply ZAIN says: October 18, 2016 at 2:31 am Really a wonderful Reply / Solution. It had worked just fine up until the last expiration of the temp license a couple days ago; I guess some recent Vista update issued after May 2009 must have "fixed" Reply TS says: February 17, 2010 at 7:53 pm You are so wonderful.

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. Gautam January 14, 2010 at 2:06 am Chass, though you've logged in as administrator you need to manually run each command as an administrator. may be there are situations when it doesn't. The Remote Session Was Disconnected Because License Store Creation Failed With Access Denied 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

I did find a solution though. The Remote Computer Disconnected Session Licensing Protocol Windows 7 The "User Account Control" is also set to the lowest level for anyone asking. Uninstalling Terminal Services should fix the issue. http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/remote-desktop-connection-error-message-the-remote/cc914f39-3d8e-4671-b569-b1ba5d68b380 Reply Andrea says: January 3, 2011 at 4:29 am Thanks!

After reading the comments here I forced the run as admin option by right clicking, didn't realise it was different from logging in as admin and running the program… This recreated Remote Session Was Disconnected Because There Are No Advertisement Advertisement WindowsITPro.com Windows Exchange Server SharePoint Virtualization Cloud Systems Management Site Features Contact Us Awards Community Sponsors Media Center RSS Sitemap Site Archive View Mobile Site Penton Privacy Policy Terms This way the Licensing Key will be unique for each terminal. This worked for me.

The Remote Computer Disconnected Session Licensing Protocol Windows 7

Advertisement Related ArticlesQ. look at this site many thanks Peter November 7, 2011 at 9:00 pm This still doesn't work. The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 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 Change The Terminal Server Licensing Mode From Per Device To Per User Required fields are marked *Comment Name * Email * Website Notify me of follow-up comments by email.

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 weblink Delete the old HardwareID-temp and Store-temp and close the registry editor. dBforumsoffers community insight on everything from ASP to Oracle, and get the latest news from Data Center Knowledge. By default, a restricted user does not have permission to write registry entries to HKEY_LOCAL_MACHINE. Licensing Protocol Error Remote Desktop Windows Server 2008

please note all other Windows workstations do not get the licensing protocol error from the Server. I don't have any other Vista machines in the building to export the key from. If you are not sure how to delete the key and its subkeys, just rename them as follows : HardwareID to HardwareID-temp and Store to Store-temp. 4> Reboot the system. navigate here Log into your account Forgot your password?

The only solution was to RDP to a Terminal Server on the same side of the firewall, log off and get a temporary CAL. Mslicensing Registry Key Missing I would like not to have to manually execute mstsc.exe as an Administrator on all of our newly purchased thin clients. The protocol is the problem.

Shutdown and restart Windows XP.

You should only need to do this once. Win XP Prof. and Win 7 Prof. Mslicensing Key asked 7 years ago viewed 3604 times active 7 years ago Blog Stack Overflow Podcast #92 - The Guerilla Guide to Interviewing Related 5Can't Remote Desktop to server after rebooting via

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 up and rise to the However, the webpages get saved in... I did this on several Windows XP clients and it workedokay but, I tried it on a Vista and Windows 7 without any luck. http://supercgis.com/licensing-protocol/remote-desktop-disconnected-error-licensing-protocol.html I have been able to fix all of the XP users by deleting the HKEY_Local_Machine\Software\Microsoft\MSLicensing sub-key as mentioned in several documents, but this does not work with all Vista or any

I deleted the registry keys; rebooted the computer; right-clicked Internet Explorer icon, and clicked "Run as administator". Regards, Zain Reply Leave a Reply Cancel reply Your email address will not be published. i renamed the licenses and tried reconnecting to my server it worked. You receive 'The remote computer disconnected the session because of an error in licensing protocol' when you attempt to connect to a remote computer using Remote Desktop on a Windows XP

This fixed the problem for me.