Home > Terminal Server > Terminal Server Licensing Protocol Error

Terminal Server Licensing Protocol Error


Changes made:Windows Updates (as per WSUS)Microsoft hotfix 435151 (Reported as already being installed)Microsoft hotfix 443159Microsoft hotfix 443528 (Not applicable to the computer, so was not installed)Citrix hotfix rollup 1 for XenApp All the way to 2008R2. van Doornik Members #1 J.R. Answers too above posts: Firewall: The Firewall on the server has already been deactivated for troubleshooting purposes. http://openoffice995.com/terminal-server/terminal-server-licensing-protocol-error-vista.php

this is a good workaround for an admin, not so much a user. 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 I was getting an error stating my license for client access to Windows Server 2003 were counting down to expire.I followed the initial instructions to a "T" and thank you!!! Both are running Windows XP pro and both have up to date SP's.

The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008

Was going crazy looking at all the possible server-side issues. Cam May 19, 2015 at 11:15 am | PermalinkFantastic, it worked like a charm! You should now be able to connect to your 2008 per user licensed terminal server. 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.

So logging remotely with an invalid ClientHWID will produce an error, but if the registry has no key for ClientHWID then it will be recreated propertly? Thanks for the info. Please contact the server administrator“ Steps (3 total) 1 The solution is delete the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing The solution is delete the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing 2 Try connecting in again If Mslicensing Registry Key Missing What should I tell them?

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 Ms Licensing Registry Key VMWare virtual disk (vmdk) March 12, 2008 / 287 Comments Posted in VMWare Microsoft .NET Framework 2.0 Service Pack 1 (KB110806) failed December 27, 2007 / 68 Comments Posted in Microsoft, Per user or per device?What errors are you seeing on the XA servers related to term serv license?Depending on how the XA are licensed you might try to delete client's license https://social.technet.microsoft.com/Forums/windowsserver/en-US/d64d00c4-c87b-4af6-83b5-54daf2c82938/remote-desktop-licensing-protocol-error?forum=winserverTS wwII yellowstone youtubeWP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.RSS FeedsSubscribe to this site's RSS feed.

Password (default) Wyse#123 (case sensitive). Removing Terminal Server Licenses From An Rdp Client Windows 7 I get a desktop, and I can enter my logon credentials for that server. 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. 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

Ms Licensing Registry Key

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. http://jeffpicard.com/blog/computer-fixes/microsoft-remote-desktop-licensing-fix/ 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 The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 and the MSLicensing key does not reappear in the registry. No Remote Desktop Client Access Licenses Available For This Computer When reviewing the application logs on both Citrix servers, I'm presented with two notices that might shed further light on things:Event ID 9009 - Happens on both the XenApp server I

OK onto the issue. http://openoffice995.com/terminal-server/terminal-server-licensing-error-citrix.php Articles, News, Problem Solutions and Other Interesting Information... 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 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 The Remote Computer Disconnected Session Licensing Protocol Windows 7

It works for me Spaski May 20, 2010 at 3:20 pm Thanks that helped!!!!! I've dug around in the hotfixes, found that after the rollip, I'm still 9 fixes short of finishing Citrix, and there are two Microsoft hotfixes that I'd need to install. Actually we have hosted 2 server in data centre. his comment is here Wole September 6, 2010 at 2:17 pm Thanks guys..copying MSLicensing registry key from a PC known to be working to the PC with the problemw saved the day.

What I am trying todo is rule out a permission problem with your thin clients. Change The Terminal Server Licensing Mode From Per Device To Per User 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 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

Thanks for the advice.

I spent too much time on this and to find out such a simple solution. However I couldn't do it with my server 2008 R2 - 64 bit. Removed MSLicensing key, did not recreate itself. Mslicensing Regedit At that point I expect the policy to have permeated through the environment too.

Does the mass of sulfur really decrease when dissolved in water and increase when burnt? I can vouch that it works with Windows 7 in this situation. Rigth clicking on the RDC client and running as admin did. weblink Who calls for rolls?

Started Remote Desktop on a machine that had the new image, and tried to connect. Thanks. -TP Marked as answer by Yuan WangMicrosoft employee, Moderator Tuesday, May 31, 2011 8:17 AM Tuesday, May 24, 2011 4:32 PM Reply | Quote Moderator All replies 0 Sign in http://pberblog.com/post/2009/12/01/Sysprepped-XP-SP3-images-gets-error-in-the-licensing-protocol-when-connecting-to-Terminal-Server.aspx Jonas November 6, 2013 at 3:23 am | PermalinkTY!Worked like a charm.Client. Privacy statement  © 2016 Microsoft.

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? Your last suggestion about redirecting the XA server to a different licensing server isn't really an option, since we have one licensing server, and connections to and from servers on Windows Thank you! The problem was not on the remote desktop or terminal server but on the client itself.

yuvi May 27, 2013 at 6:52 am | Permalinkvery helpful..thanks a lot..:) Remi October 29, 2013 at 11:26 am | PermalinkHi there!I had the same issue on multiple clients running Windows Will get back To you soon. This is strictly a TS server. Art January 12, 2011 at 1:45 am This worked like a champ.

van Doornik , 30 October 2012 - 08:56 AM Login to Reply 19 replies to this topic J.R. Rogalik July 13, 2011 at 6:29 pm After the MSLicensing removal you must start mstsc as the administrator for the reconstruction of keys. Someone told me to delete the RDC files on my MAC and that would solve the problem. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys.

The protocol is the problem. Verify that RDP session to your Terminal server still works.