this is the message "protocol error this session will disconnect try later" can some help me. Joe May 31, 2016 at 2:39 pm | PermalinkThanks mate. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? van Doornik 17 posts Posted 15 November 2012 - 09:27 AM Our license server is a 2008 R2 machine.
That should suffice. Leave a Reply Click here to cancel reply. Guillaume December 10, 2013 at 1:43 am | PermalinkYou are my saver !!! It worked without me editing the registry or anything else.
Thanks. · Lionel Chen TechNet Subscriber Support in forum If you have any feedback on our support, please contact [email protected] posting is provided "AS IS" with no warranties, and confers This worked for me. How to describe very tasty and probably unhealthy food How do you say "enchufado" in English? The Remote Session Was Disconnected Because License Store Creation Failed With Access Denied Cheers, ben February 4, 2011 at 4:47 am I just wanted to make sure when you said "delete the MSLicensing key", you meant the whole folder or just the registry file
I get a desktop, and I can enter my logon credentials for that server. Thanks for the advice. All the way to 2008R2. check here If you do not know how to take back up of your registry manually follow this tutorial : Tutorial to to back up the registry in Windows Vista or in Windows
It took the second one for me and I went ahead and changed the permissions too. 1) Right click the icon and click “Run as Administrator” 2) In the search menu Remote Session Was Disconnected Because There Are No The key was deleted, I ran the RDP Client as an Administrator but was still given the same error. Thank you so much. Worked for me.
share|improve this answer answered May 9 '12 at 19:27 just.another.programmer 3802719 add a comment| up vote 0 down vote This problem made by some kind of caching of remote desktop licensing https://community.spiceworks.com/how_to/84081-the-remote-computer-disconnected-the-session-because-of-an-error-in-licensing-protocol I hope Tuesday will give me some means of testing this further with the updates. 1317-315687-1689256 Back to top J.R. The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 b. Change The Terminal Server Licensing Mode From Per Device To Per User Under the embedded system, the thin clients startup and automatically login under a default "standard" user account.
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 http://supercgis.com/licensing-protocol/remote-desktop-connection-error-in-the-licensing-protocol-windows-7.html hitesh October 16, 2012 at 9:58 pm | PermalinkThank you so much Nadeem October 18, 2012 at 12:33 am | Permalinkyour computer could not connect another console session on the remote W7 Enterprice. The Rollup fixes a heap of other problems, so this might indeed be advisable to do, tho it remains to be seen if this impacts the problem we're facing. Licensing Protocol Error Remote Desktop Windows Server 2008
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 If you do not know how, please Google "How to take back up of Registry file". 2> When I said "Delete the MSLicensing Key", I meant the whole folder itself, rather 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. his comment is here Linux vs.
The error message (translated from danish): "The remote computer disconnected the session due to an error in the licensing protocol. Mslicensing Registry Key Missing He said there are 3 solutions. It now pops up the following notice:The desktop you are trying to open is currently unavailable.
Connects to a 2003 Citrix server without problemsConnects to a 2003 non Citrix server without problemsConnects to a 2008 R2 non Citrix server without problemsConnects to a 2008 R2 Citrix server It says error deleting the key. Matt October 29, 2009 at 9:32 pm Got same problem. Mslicensing Key Best, Compari February 17, 2010 at 10:53 am I am running MAC PRO and the server is Windows 2000.
please note all other Windows workstations do not get the licensing protocol error from the Server. Please try connecting to the remote computer again or contact your server administrator. The combination of the updates and the policy seems to have solved the issues. weblink After that, use the administrative permission to run the mstsc.exe, check if the issue still persists in this situation.
Rogalik July 13, 2011 at 6:29 pm After the MSLicensing removal you must start mstsc as the administrator for the reconstruction of keys. Tuesday, August 23, 2011 4:22 PM Reply | Quote 1 Sign in to vote After the reboot of my workstation and correcting the time on the Server, I was able to 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. Win 7 OS Ken February 5, 2011 at 4:50 am Hi, I deleted the HardwareID and Store folder.
Edit: I didnt read your question properly, as mrdenny said you dont need to install the Terminal Services role in order to remotely access the server for administration. regards, swapnil Tricky November 24, 2010 at 8:27 pm I had the same RDP problem but on a Windows 7 machine. THANK YOU. I have deleted the keys and followed the procedure through on two different systems both with the same emssage one it worked fine the other it didn't .
van Doornik Members #1 J.R. Please try connecting to the remote computer again or contact your server administrator." When I looked up in the knowledge base, this is what Microsoft had to say : "Cause: The Windows XP – simply run Remote Desktop Connection 5. Regards, Hassan Gautam December 20, 2010 at 12:40 am @Swapnil - Which OS are you using ?
While running, right click and select the option ‘Run as adminimstrator'. Contact your administrator to confirm that the correct settings are in place for your client connection. I did find information on running IE as an administrator and this only works on a per session basis. This fixed the error on my Vista Home Premium!
Uninstalling Terminal Services should fix the issue. Reply didier quelle says: November 27, 2012 at 6:17 am yes, i believe you can fly! I have 125 servers in the fileld around 8000 workstations… and all have this problem. And your indications are still working well.
I have been trying to connect to my customer's server for weeks.