Error Related To Licensing In Terminal Server
Contents |
360 games PC games terminal server licensing error 4105 Windows games Windows phone games Entertainment All Entertainment
Office Licensing On Terminal Server
Movies & TV Music Business & Education Business Students & educators office 2007 licensing terminal server Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet office 2003 licensing terminal server Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Microsoft Licensing Terminal Server
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered quickbooks licensing terminal server by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization terminal server licensing pricing PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly Access Gateway)Profile ManagementProof
Terminal Server Licensing 2012
of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb https://support.microsoft.com/en-us/kb/187614 InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products XenApp XenApp 6.5 for Windows Server 2008 R2 Application Publishing Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Remote Desktop causes a licensing http://discussions.citrix.com/topic/315687-remote-desktop-causes-a-licensing-protocol-error-for-user-initiated-connections-to-rds-servers-but-not-to-non-rds-servers/ protocol error for user-initiated connections to RDS servers, but not to non-RDS servers Started by J.R. van Doornik , 30 October 2012 - 08:56 AM Login to Reply 19 replies to this topic J.R. van Doornik Members #1 J.R. 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. This image contains Windows Server 2008 R2, fully patched, with XenApp 6.5 installed. 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 servers.- RDP shows a licensing pro
Kent Chen June 12, 2009 Tips & Tricks One remote user from work called me the other day saying her remote desktop client stopped working because of “there are no terminal server client access licenses available for this computerâ€. http://www.kjctech.net/the-remote-computer-disconnected-the-session-because-of-an-error/ Well, that's easy, I walked her through and successfully deleted the MSLicensing registry key on her Windows Vista computer, and happily told her you can try it again now. But surprisingly, she replied a few seconds later saying http://www.virtualizationadmin.com/articles-tutorials/terminal-services/licensing/troubleshooting-terminal-server-licensing-issues-part3.html no, still didn't work. But this time the error message was different: The remote computer disconnected the session because of an error in the licensing protocol It's surprising because having been using remote desktop client for ages this terminal server is the first time I saw the error message like this. Out of luck after a few checking here and there, I went to Google for help. Nothing had worked until I was landed to this Microsoft KB, Removing Terminal Server licenses from an RDP client. At the very bottom of this KB, it mentions: If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect licensing terminal server to a Terminal Server may fail. Also, you receive the following error message: An Error occured in the licensing protocol. And suggests that to resolve this problem, right-click the Remote Desktop Connection icon, and then click Run as Administrator. Bingo!! That was it. Did I mention that this problem was actually occurred on a Vista computer above? And it only happens on Vista or later OSs because: By default, the remote desktop connection runs as a user with the lowest user permissions. By default, a restricted user does not have permission to write registry entries to HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys. 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 persistent (9)Remote Desktop Connection 7.0 Released for Vista and XP (0)RDP to Windows Remote Desktop from Linux (0)Remote Desktop (RDP) on iPhone (2)Terminal License Will be Expired in x Days (0) registry remote desktop client 22 Responses to "The remote computer disconnected the session because of an error in the licensing protocol" Keith says: October 22, 2009 at 10:37 pm Thanks, this saved me from nearly having a coronary when the old tric
26 Sept. 2007] Some of the more less-common issues with Terminal Server licensing, including: corrupt license databases, activation issues, and problems adding CALs. If you would like to be notified when Michael Burle releases the next article in this series please sign up to the MSTerminalServices.org Real time article update newsletter. If you would like to read the previous articles in this series please go to: Troubleshooting Terminal Server Licensing Issues (Part 1) Troubleshooting Terminal Server Licensing Issues (Part 2) In parts one and two of this four-part series, we discussed the more common server-related licensing issues.In this segment, I’ll cover some of the more less-common issues with terminal server licensing, including: Corrupt license databases Activation issues Problems adding CALs Corrupt Licensing Database Although rare, it is possible for the licensing database to become corrupt.Symptoms of a corrupt database include not being able to start the licensing service, failure of the service to stay running, or possibly the inability of terminal servers to lease CALs (although this last one is most likely due to some other underlying issue). Corruption can occur for a number of reasons, but the most popular is making the mistake of placing the licensing database on a compressed drive.The drive compression could cause a write-delay, thereby corrupting the database.Per Microsoft, Jet-based databases should not be located on compressed drives.See Microsoft KB Q318116 for more information. Other ways corruption can occur is incorrect shutdown of the server or a licensing service crash, or a hardware related issue such as a problematic RAID controller or faulty cache. Of course, there is no better protection against corruption than a good backup; however if you find yourself with a corrupt database you can recreate a new (empty) database pretty easily. Keep in mind that the new database will not have any of your CALs installed; you will need to contact the Microsoft Clearinghouse to recover them. Recreating the database is as simple as removing or renaming the existing database folder and restarting the service: Stop the Terminal Server Licensing service. Rename the LServer directory in Windows\System32 (default location) to something such as LServer_Old. Create a new folder where the old one was (\Windows\System32 by default) called LServer. Start the Terminal Server Licensing service. When the service is started, it will automatically create a new TLSLic.edb database file along with a set of transaction logs.You