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

Remote Desktop An Error In The Licensing Protocol


Any suggestions? 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 luv2bike2 September 15, 2009 at 8:03 pm the deleting of the registry key/subkeys did not work so I copied the MSLicensing registry key from my computer to the one that was van Doornik 17 posts Posted 20 November 2012 - 01:21 PM Need to go to a meeting in a few minutes. this contact form

I have verified that both keys have full access for the Local Workstation group "Users" to make sure that it is not a security issue. That is not acceptable since a lot of our users are not administrators nor can use admin credentials on company computers. Which failed in exactly the same way as the connect to a server in a different farm. It did not recreate the licensing keys. http://www.networknet.nl/apps/wp/archives/2221

The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008

Why did the Ministry of Magic choose an ax for carrying out a death sentence? When I connect to a Windows 2003 Citrix machine, or a Windows 2008 Citrix machine is when the error crops up. Carino August 9, 2010 at 3:33 pm what pc will where i edit.. The remote computer disconnected the session because of an error in the licensing protocol.

This fixed the error on my Vista Home Premium! While creating the license keys right click and you'll find the option run as administrator and this will create the licensing keys. van Doornik 17 posts Posted 31 October 2012 - 08:28 AM Some further details: Exactly the same problem occurs if we try to use remote desktop to access servers in our Mslicensing Key I did find information on running IE as an administrator and this only works on a per session basis.

After that, use the administrative permission to run the mstsc.exe, check if the issue still persists in this situation. No Remote Desktop Client Access Licenses Available For This Computer pls help Gautam January 14, 2010 at 2:15 am @Chass - Sounds good. Thank you. view publisher site regards, swapnil Tricky November 24, 2010 at 8:27 pm I had the same RDP problem but on a Windows 7 machine.

Have used TS for years and never saw this error. Change The Terminal Server Licensing Mode From Per Device To Per User in the server or on the pc who have problem? Windows XP – simply run Remote Desktop Connection 5. 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?

No Remote Desktop Client Access Licenses Available For This Computer

JSI Tip 8247. If so, why is it allowed? The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 After you delete the REG key run RDC as administrator. The Remote Computer Disconnected Session Licensing Protocol Windows 7 Spazz October 12, 2009 at 12:17 pm I removed the key because of an error that the licensing could not be renewed.

I tried to delete the registry file only, but it said :unable to delete all specified values" Anyone got clue? weblink Now connects fine. please note all other Windows workstations do not get the licensing protocol error from the Server. I did this on several Windows XP clients and it workedokay but, I tried it on a Vista and Windows 7 without any luck. Mslicensing Registry Key Missing

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. All Rights Reserved Privacy & Terms Advertise © Copyright 2015 - www.TechBuzz.in Home How-tos The remote computer disconnected the session because of an error in licensing protocol by mtoddh on June 25, 2014 05:06pm Introduction RDP fails navigate here Linux vs.

If it helps, this post here tells you more about it with screenshots too. Hkey_local_machine\software\microsoft\mslicensing I've deleted the keys inside of MsLicensing and rebooted. Brandon May 17, 2012 at 3:37 pm | Permalinkdidnt work for me either Kanchana May 22, 2012 at 8:06 am | PermalinkIs there any other fix available for windows 7 professional

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

Recommended reading: Registry tweak to improve performance of Windows XP SHARE Facebook Twitter tweet Gautam RELATED ARTICLESMORE FROM AUTHOR How To's How to Remove Shortcut Virus from Pendrive How To's Recover Uninstalling Terminal Services should fix the issue. I was able to fix the issue on a Windows 7 machine where this registry had been deleted. Mslicensing Key Not Rebuilding Please try connecting to the remote computer again or contact your server administrator.

Win XP Prof. When the client is restarted, the missing registry key is rebuilt. 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 http://supercgis.com/licensing-protocol/remote-desktop-error-in-the-licensing-protocol.html 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

when i am trying to do remote connection I am getting following erro. Best Chass January 14, 2010 at 12:41 am I'm running Vista Home trying to fix the same problem with a users computer. This way the Licensing Key will be unique for each terminal. Open a CMD.EXE window. 2.

But it won't work for me. 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. Monday, September 23, 2013 6:26 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site. Thank you!

That leaves one hotfix to be installed: http://support.citri...ticle/CTX130473At present the servers apparently contain 3 fixes, namely the XA650W2K8R2X64001 (passthrough authentication fails), XA650W2K8R2X64019 (CPU consumption of WINLOGON.EXE) and XA650W2K8R2X64025 (BSOD on VDTW30.DLL). Solution: Try connecting to the remote computer again. 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. 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

kimi September 8, 2015 at 11:23 pm | Permalinkif u using windows 2012simple.. van Doornik 17 posts Posted 30 October 2012 - 08:56 AM Situation: A Citrix farm with a number of servers that are all started from the same basic image through provisioning. Gautam February 28, 2010 at 10:33 am @Haydee - If you've followed all steps mentioned in the post, you should have a new MSLicensing key created when you restart your system. So just to test that scenario, I've tried just connecting it to one of our domain controllers...

Thank you! And your indications are still working well. Mike June 11, 2010 at 3:01 pm Using Windows 7: your suggestions worked for me. 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.

Still no luck logging in. my one computer is remove from the server i can't manage the time for it……how can i connect again to that computer..