Home > Licensing Protocol > Remote Desktop Disconnected Error Licensing Protocol

Remote Desktop Disconnected Error Licensing Protocol

Contents

This will allow the RDC client permission to rebuild the necessary registry keys. Connecting to Windows 2003 machines goes without any issue whatsoever. Only my MAC does. Try to activate the XA server with a different licensing srv to see if you get same errors.CheersBogdan 1317-315687-1687852 Back to top J.R. http://supercgis.com/licensing-protocol/remote-desktop-disconnected-licensing-protocol-error.html

The protocol is the problem. Next to this is a separate Citrix farm that contains a test-environment for applications.Issue: User starts MSTSC (Remote Desktop) as an application on Citrix, and tries to connect to various other Privacy statement  © 2016 Microsoft. I get the same error message as before. http://www.networknet.nl/apps/wp/archives/2221

The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol Windows 7

Reply Kevin says: June 17, 2011 at 2:32 pm yes, i believe you may actually be able to walk on water Reply Gene says: November 23, 2011 at 10:54 pm finally October 29, 2014 Prasad You're awesome, Simple solution for a problem that i thought was complex. van Doornik Members #3 J.R. many thanks Peter November 7, 2011 at 9:00 pm This still doesn't work.

Any thoughts? © Copyright 2006-2016 Spiceworks Inc. Because the RDC client does not by default have permission to create a new key under the HKLM\Software\Microsoft branch, it cannot rebuild the licensing information once it has been deleted! I'm an administrative professional whose company has a less than qualified IT guy…he was going to remove my computer from the office to fix this! Licensing Protocol Error Remote Desktop Windows Server 2008 I compared the old registry values to the recreated values and as far as I can see, only the ClientHWID value has changed.

Since we're using an image, these keys are inherently empty, and should be filled with the appropriate license as logons occur. The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 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 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 my one computer is remove from the server i can't manage the time for it……how can i connect again to that computer..

Ken Gautam February 4, 2011 at 8:10 am @Ben - The easiest way to sort this problem is: 1> Take a back up of your registry file. The Remote Session Was Disconnected Because License Store Creation Failed With Access Denied Related Posts: Terminal License Will be Expired in x Days Remote Desktop Keyboard Shortcuts Remote Desktop (RDP) on iPhone You may also likeHow to make an old school SUBST virtual drive To resolve this behavior, I have scripted FixRDMSL.bat, which contains: @echo off setlocal call :Quiet>nul 2>&1 set key=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing for /f "Tokens=*" %%a in ('REG QUERY %key%^|find /i "%key%\"') do ( @echo o Reason: logged on user does not have rights to write to registry location o Solution: Disable UAC or give user and application necessary rights You may then need

The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008

So I'm only looking at two fixes that are not included in the Service Pack which may or may not have an impact on this:http://support.microsoft.com/kb/2571388/http://support.microsoft.com/kb/2661001The first indicates a resolvement of an https://community.spiceworks.com/how_to/84081-the-remote-computer-disconnected-the-session-because-of-an-error-in-licensing-protocol Solution: Try connecting to the remote computer again. The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol Windows 7 So just to test that scenario, I've tried just connecting it to one of our domain controllers... The Remote Computer Disconnected Session Licensing Protocol Windows 7 Thank you so much.

So it looks like I need to tweak a policy to get this working... weblink There was little valuable information on the Internet to solve this problem. In this one-day training, you'll find out what this new model for Windows really means to your organization and what the benefits are once you've made the move to Windows 10. Regards, Zain Reply ZAIN says: October 18, 2016 at 2:31 am Really a wonderful Reply / Solution. Change The Terminal Server Licensing Mode From Per Device To Per User

Also, you receive the following error message: An Error occured in the licensing protocol. 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 When searched the registry I found MSLicensing in: HKLM\SOFTWARE\Wow6432Node\Microsoft\ do I have to delete it here too? navigate here van Doornik Members #2 J.R.

the Users-group is also allowed 'full control' here).I've looked at the permissions on these keys, and while the Users group (which contains all domain users, including the user I'm testing with) Remote Session Was Disconnected Because There Are No I don't have any other Vista machines in the building to export the key from. share|improve this answer answered Dec 24 '15 at 17:01 Mohammad Saleh Salehi 15913 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using

The problem was not on the remote desktop or terminal server but on the client itself.

Can you help? Reply didier quelle says: November 27, 2012 at 6:17 am yes, i believe you can fly! Regards, Hassan Gautam December 20, 2010 at 12:40 am @Swapnil - Which OS are you using ? Mslicensing Registry Key Missing regards arasssen JT April 29, 2010 at 10:00 am thanks all, these solved the problem I faced.

I can start the application fine. This resolved the issue for me with the only difference being that I had to run RD Web access from an Internet Explorer window with elevated privileges instead of using the Help Desk » Inventory » Monitor » Community » Skip to Navigation Skip to Content Windows IT Pro Search: Connect With Us TwitterFacebookGoogle+LinkedInRSS IT/Dev Connections Forums Store Register Log In http://supercgis.com/licensing-protocol/remote-desktop-disconnected-error-in-the-licensing-protocol.html Run REGEDIT 2.

I don't know where Microsoft RDC files are on the MAC. Worked for both my Win7 and my Vista computers. How to fix remote desktop error in licensing protocol? Reply Chase says: March 17, 2011 at 7:41 am Actually, this "fix", along with many others I have found on Google and other places, did not work as described.

DukeMini May 26, 2010 at 9:45 pm Tried it on different clients. In the end there was a simple solution fix this problem to connect to remote systems. However, only the HardwareID is created after I restart the system. van Doornik Members #15 J.R.

It should remove the key. Chen's WebLog[…]… Reply resume writers says: January 22, 2012 at 2:13 pm resume writers… […]The remote computer disconnected the session because of an error in the licensing protocol | KC's Blog[…]… Print reprints Favorite EMAIL Tweet Discuss this Article 2 superfishnz on Oct 27, 2010 Though this article has been written over 4 years ago, it seems the problem has started happening Open a CMD.EXE window. 2.

van Doornik 17 posts Posted 20 November 2012 - 02:40 PM Flagged it as answered... mayur August 23, 2010 at 10:00 am Thanks that help. So looks like just registry corruption. van Doornik Members #5 J.R.

Q. The second indicates the displaying of an error on Remote Desktop services itself, which both are not the case in my situation. I deleted the registry keys; rebooted the computer; right-clicked Internet Explorer icon, and clicked "Run as administator". Please try connecting to the remote computer again or contact your server administrator.

It worked. 2. What exactly is the problem?