Home > Licensing Protocol > Remote Desktop Connection Error In Licensing Protocol

Remote Desktop Connection Error In Licensing Protocol


If you try the same thing on Windows Vista or Windows 7, when you try to reconnect to the server you get this message: The remote computer disconnected the session because Thanks.. Feel free to chip in with any further things you can think of. 1317-315687-1687831 Back to top Bogdan Stanciu Members #6 Bogdan Stanciu 21 posts Posted 09 November 2012 - 04:34 may be there are situations when it doesn't. this contact form

Make a empty text file Name it "mypatch.reg" or "mypatch.reg" Put bellow text in it and save it Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing] Run it by dubble click on file! What's weird tho, is that a connection was made, but nothing was placed under the MSLicensing keys, and no permission alterations were made.So I then tried connecting as the user to If they try andpretend like it is a normal RDS licensing problem please explain to them that you are using Per User licensing and your full XP and Windows 7 machines 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. http://www.networknet.nl/apps/wp/archives/2221

The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008

If however I try to connect to a different XenApp server in the same farm, I get this screen:http://imageshack.us/photo/my-images/822/windowssec.jpg/Filling in the same credentials as the user allowed to logon remotely (or Telnet to ports from thin client successful. Networking We are looking at adding WiFi coverage into our manufacturing factory. The factory is primarily metal construction (walls, roof, beams etc.) and we're going to need a lot of connectivity.

So I exported them from an XP machine but it won't import the keys. Why is international first class much more expensive than international economy class? Claudius August 14, 2012 at 8:37 am | PermalinkProblem fixed! The Remote Session Was Disconnected Because License Store Creation Failed With Access Denied And of course, once you do install a license server, you need to install licenses!

Saved me a lot of pain :) Swapna Havnur June 2, 2016 at 2:25 pm | PermalinkThank you for the easy instructions , it works. The Remote Computer Disconnected Session Licensing Protocol Windows 7 Generated Wed, 26 Oct 2016 19:25:02 GMT by s_nt6 (squid/3.5.20) Windows Server TechCenter   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة That should help if you are on Vista. https://social.technet.microsoft.com/Forums/windowsserver/en-US/d64d00c4-c87b-4af6-83b5-54daf2c82938/remote-desktop-licensing-protocol-error?forum=winserverTS regards arasssen JT April 29, 2010 at 10:00 am thanks all, these solved the problem I faced.

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 Remote Session Was Disconnected Because There Are No Thanks for the advice. My office support made me wait 4 days with no solutions to my problem. Now the registry settings are renewed.

The Remote Computer Disconnected Session Licensing Protocol Windows 7

Connecting to Windows 2003 machines goes without any issue whatsoever. next time when you logon Pullup the RDC with Elevated Rights --> RDc --Right click---Run as Admin. The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 narayanan February 4, 2010 at 11:29 am hi, am also facing similar problem. Change The Terminal Server Licensing Mode From Per Device To Per User this is the message "protocol error this session will disconnect try later" can some help me.

remove all.. :) hope its will help Neil November 23, 2015 at 9:15 am | PermalinkFantastic, it worked but had to run RDP as an administrator twice the 2ed time it http://supercgis.com/licensing-protocol/remote-desktop-connection-error-in-the-licensing-protocol-windows-7.html The Last Monday Schrödinger's cat and Gravitational waves New employee has offensive Slack handle due to language barrier How to adjust UI scaling for Chrome? van Doornik 17 posts Posted 14 November 2012 - 12:14 PM Looking at the Citrix article http://support.citri...ticle/CTX127883, I'm guessing the alteration in the registry of the machine acting as a client Or am I missing something? 1317-315687-1690604 Back to top Bogdan Stanciu Members #20 Bogdan Stanciu 21 posts Posted 20 November 2012 - 02:47 PM i believe so...doesn't matter 1317-315687-1690590 Back to Licensing Protocol Error Remote Desktop Windows Server 2008

That's it ! Based on everything that you are seeing this (unique issue) would be the likely culprit. when i am trying to do remote connection I am getting following erro. http://supercgis.com/licensing-protocol/remote-desktop-connection-error-in-the-licensing-protocol.html now I can finally work again!

Attached Files desktop launches.JPG 35.52K 0 downloads 1317-315687-1690553 Back to top Bogdan Stanciu Members #12 Bogdan Stanciu 21 posts Posted 20 November 2012 - 01:12 PM http://support.citrix.com/article/CTX124745 - this is exactly Mslicensing Registry Key Missing I was very careful to follow your instructions exactly (run as administrator) and it worked the first time. Imported from a working PC - didn't work either.

I added a remotedesktop program to one server to verify this.

Thursday, August 11, 2011 8:16 PM Reply | Quote 0 Sign in to vote this worked for me, as I am the admin. Chass January 14, 2010 at 2:12 am I had tried right clicking but there is no option for "Run as administrator" when you are logged in as administrator. i needed to rdp from a thin client, read the other articles and found you cannot edit microsoft licenses from the registry. Mslicensing Key All the way to 2008R2.

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 - Microsoft Customer Support Microsoft Community Forums CLOSE News Mobile Applications Iphone Windows Phone Gadgets Design Photography Reviews More Apple Android Windows Phone Iphone Thursday, October 27, 2016 Sign in / Join What I am trying todo is rule out a permission problem with your thin clients. his comment is here Can you help?

In our case the Citrix machines that the user launches the Remote Desktop application on. Blackberry Reviews Epson WorkForce 635 All-In-One Printer, Review, Price, Availability Reviews Hosting And Cost Of Doing Business Reviews Negative Things / Disadvantages About Apple iTouch Before You Buy One More Apple First time! \Thank you very much Raftxo October 26, 2016 at 8:33 am | PermalinkI'm accessing Windows Server 2003 from W10 computer via TS. it works fine for me.

Removed MSLicensing key, did not recreate itself. Which failed in exactly the same way as the connect to a server in a different farm. Paul April 22, 2010 at 12:26 am @Compari: a Mac fix: I was getting this error using RDC on the Mac too, but a colleague found this article from Microsoft: http://support.microsoft.com/kb/187614 How to draw and store a Zelda-like map in custom game engine?

Bitwise rotate right of 4-bit value Computing only one byte of a cryptographically secure hash function Delayed effects after player's death Cannot patch Sitecore initialize pipeline (Sitecore 8.1 Update 3) What Join the community Back I agree Powerful tools you need, all for free. While running, right click and select the option ‘Run as adminimstrator'. Not 100% solved yet, but looks like we're closing in on 100% rapidly :) 1317-315687-1690548 Back to top Pavan nannapaneni Members #11 Pavan nannapaneni 1,041 posts Posted 20 November 2012 -

I have been trying to connect to my customer's server for weeks. 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. Remote Desktop causes a licensing protocol error for user-initiated connections to RDS servers, but not to non-RDS servers Started by J.R. up vote 1 down vote favorite In Windows XP if you have a problem with your RDC client license, you can delete the HKLM\Software\Microsoft\MSLicensing key to force the license to rebuild

van Doornik 17 posts Posted 06 November 2012 - 08:17 AM Nobody having any ideas here? :( 1317-315687-1686397 Back to top Bogdan Stanciu Members #4 Bogdan Stanciu 21 posts Posted 09 van Doornik Members #19 J.R. Microsoft needs to address this issue! Simply being logged in as an administrator will NOT work.

What's the best way set up reliable Wi-Fi in a factory?