Home > Licensing Protocol > Remote Desktop Disconnected Because Of A Licensing Protocol Error

Remote Desktop Disconnected Because Of A Licensing Protocol Error


Since a moderator is now involved, as you'd made very clear, if they believe you should be awarded a 'great' rating in spite of my comments then I won't belabor the The next time the client connects, an attempt is made to upgrade the validated temporary Terminal Server CAL token to a full Terminal Server CAL token. In a Per User environment you will see it if the server was unable to contact the licensing server, but that is not what is happening in your case. Thanks . http://supercgis.com/licensing-protocol/remote-desktop-disconnected-licensing-protocol-error.html

I have not used Windows 7 embedded at all let alone the specific build you are using so I do not know. van Doornik Members #15 J.R. Arassen May 10, 2010 at 4:25 pm thanks for the post. Database administrator? http://www.networknet.nl/apps/wp/archives/2221

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

Join the community of 500,000 technology professionals and ask your questions. Very easy instructions. They say its a problem with the network but that can't be true on all the networks???

I get no errors. Linux vs. Closing in on the solution. Licensing Protocol Error Remote Desktop Windows Server 2008 next time when you logon Pullup the RDC with Elevated Rights --> RDc --Right click---Run as Admin.

Win 7 OS Ken February 5, 2011 at 4:50 am Hi, I deleted the HardwareID and Store folder. The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 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 Some posts above suggest running IE as adminstrator, but it is the "Remote Desktop Connection" program that needs to be run as Administrator in order for the registry keys to be http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/remote-desktop-connection-error-message-the-remote/cc914f39-3d8e-4671-b569-b1ba5d68b380 The protocol is the problem.

Help Desk » Inventory » Monitor » Community » Jump to content Citrix Citrix Discussions Log In Citrix.com Knowledge Center Product Documentation Communities Blogs All CategoriesAppDNAArchived Products (includes End of Life)Citrix The Remote Session Was Disconnected Because License Store Creation Failed With Access Denied It works for me Spaski May 20, 2010 at 3:20 pm Thanks that helped!!!!! Have you updated the Wyse image to the latest version available on one thin client as a test? After the user has logged into the session, the Terminal Server instructs the License Server to mark the issued temporary Terminal Server CAL token as being validated.

The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008

Setup your RDP session for your terminal server. The client will try to obtain a new license from the server the next time that it connects." Just worked for me…Hope this helps some Santosh April 20, 2010 at 11:13 The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol Windows 7 The amount of fixes combined mean I'm not going to activate that image prior to monday tho, provided I get around to creating the image this week still. The Remote Computer Disconnected Session Licensing Protocol Windows 7 Covered by US Patent.

ed December 23, 2010 at 1:57 am copying the MSLicensing registry key from another system and imported it, works like charm Will Howard December 20, 2010 at 8:01 pm Swapnil Easy http://supercgis.com/licensing-protocol/remote-desktop-disconnected-error-in-the-licensing-protocol.html I'm logged on as an administrator. With Windows 7 the security settings for a regular user are severe. Required fields are marked *Comment Name * Email * Website Notify me of follow-up comments by email. Change The Terminal Server Licensing Mode From Per Device To Per User

If an unlicensed client connects to a Terminal Server for the first time, the Terminal Server issues the client a temporary Terminal Server Client Access License (CAL) token. haydee February 28, 2010 at 9:09 am I deleted my MSlicensing from my laptop computer in error…please help I have windows XP and have been trying to get this back, I Verify connection. navigate here I hope Tuesday will give me some means of testing this further with the updates. 1317-315687-1689256 Back to top J.R.

may be there are situations when it doesn't. Remote Session Was Disconnected Because There Are No OK onto the issue. I still have the same problem.

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

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Have you connected to the registry on one of the thin clients and checked permissions on the MSLicensing key? The old Citrix servers have been around for a couple of years and never gave us problems.Edited by: jvdoornik on 31-okt-2012 4:35 1317-315687-1684945 Back to top J.R. Mslicensing Registry Key Missing van Doornik Members #3 J.R.

Log In or Register to post comments Please Log In or Register to post comments. Even worse, also checking the GPO's that are unleashed on these machines again show specifically that the Users should have 'full control'. which went through without a hitch (after just popping a screen up asking me if I wanted to allow access to this computer). http://supercgis.com/licensing-protocol/remote-desktop-disconnected-error-licensing-protocol.html RDP from Full OS XP clients and windows 7 do not have issues.

I have used the diagnostic utility built into the RD session host MMC. van Doornik Members #5 J.R. Reply stu says: November 1, 2009 at 11:36 am Just had this exact same problem on a win7 machine. No I have not edited GP on 2003 system.

The error in licensing protocol is almost exclusively seen in Per Device environments. You will need to find one that fits your scenario but there is not a place on the server to say fix this. Your Windows XP and Windows 2000 clients receive 'The remote session was disconnected because the local computer client access license could not be upgraded or renewed' when they attempt to connect and Win 7 Prof.

It has all the relevant info. I did find a solution though. These are Thin clients (Wyse C90LE7) with Windows7 embedded.Steps suggested to takefor workstation WILL NOT work with Windows 7 embedded.