Error Terminal Server Licensing
Contents |
Created:26 Mar 2014 | Modified:15 Apr 2016 Languages log in to start download LOGIN Don't have an account? Create one here. Or Continue As Guest Which best describes you: IT Admin Business User DOWNLOAD Information Summary This article terminal server licensing error 4105 contains information on troubleshooting 1003 and 1004 Terminal Server licensing errors. Users attempting terminal server licensing pricing to connect to a XenApp server might experience the following Terminal Services related errors in the Event Log: Event ID: 1003Source: terminal server licensing 2012 TermServiceType: InformationThe terminal service client has provided an invalid license. Event ID: 1004Source: TermServiceDescription: Unable to acquire a license for user name, domain name. For more information, see Microsoft TechNet articles - TS Licensing Step-by-Step
Terminal Server Licensing Cost
Guide and Troubleshooting Terminal Server Licensing. Background With Microsoft (both regular Client Access License (CAL) and Terminal Services CAL) licenses, before an ICA connection is established (the GINA logon pop-up), the client license must be confirmed to exist and be valid. Note: Windows XP Professional workstations do not have built-in CALs with respect to Windows 2003 Terminal Server License Servers. When there is insufficient permissions to the following registry key, windows terminal server licensing connection failures occur. Investigate the Microsoft Terminal Services License manager to see if the workstation is enumerated. If the workstation is not enumerated, then this issue is on the Windows OS level. For more information, contact Microsoft Technical Support and verify that your Windows 2003 Terminal Licenses are activated. Symptom-1 When connecting with a Citrix ICA Client after downloading a Remote Desktop Protocol (RDP) web client, the RDP client might not exhibit any issues and continue to connect. Cause-1 The Event Log does not specify the client device that provided the invalid license. Insufficient permissions are being applied to the Microsoft license key in the registry for the Authenticated Users group. When testing, attempt to create an RDP connection after removing the MSLicense key in the registry as a user (no Domain Admin or Power User Group); the RDP connection also fails. Solution-1 It might be useful to investigate the Cryptography registry keys in HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER on both the server and workstation. See Microsoft TechNet and the usage of RegMon and FileMon for additional information. In addition, see Windows Sysinternals. These changes will be reflected from the client device. If you are making a desktop connection, then opening ICA connection inside the
upon connection: "The remote session was disconnected because there are no Terminal Service License Servers available to provide a license. Please contact your server administrator." This issue can be resolved typically install terminal server licensing by removing a registry key and reconnecting to the RDP or Citrix server. Steps
Terminal Server 2000 Licensing
(3 total) 1 Open the registry editor While logged in as an administrator, click 'start'> 'run' In the 'open' field, type
Office 2010 Terminal Server Licensing
'regedit.exe' and click 'ok.' 2 Locate and delete the MSLicensing registry key Navigate to HKLM\Software\Microsoft key. Export this key for backup purposes. Find the 'MSLicensing' subkey and delete it. 3 Retry your connection to http://support.citrix.com/article/CTX564283 Citrix/RDP Once the key has been deleted, you can try to open the Citrix/RDP session in question again. Note that you do not have to close Internet Explorer (if accessing via this method). If the problem persists, check the remote end to ensure there is a valid terminal services licensing server online and available. Conclusion These steps can also be performed remotely, pending you have admin rights, using a https://community.spiceworks.com/how_to/30826-resolving-no-terminal-server-license-servers-available-when-using-citrix-or-rdp remote registry connection via regedit. References Removing Terminal Server licenses from an RDP client 1 Comment Pimiento Albert6697 Sep 28, 2016 at 04:12pm I ran into this issue because I installed the RDS role for testing on the server I was attempting to connect to and after the allotted period of time (60 or 90 days) I had to have RDS licensing so it blocked any incoming connections due to licensing. I simply removed the role, rebooted and was able to log in via RDP. Read these next... How does your organization track your assets? Hardware What methods does your business use to keep track of the asset-tagged equipment? How do you block port scanners? Security We recently switched to a new internet service (Fiber DIA) and I noticed almost immediately that the blocked traffic spiked and all kinds of IP's were trying to telnet into my new IP block. Strange...So I put in a new firewall rule and then things got stranger. Did my IP camera get hacked? Networking I have kind of a strange thing happening on my home network and it's making me wonder if my IP camera got hacked. Any insights? © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitem
Fixes / Remote Server Licensing Fix Remote Server Licensing FixIf you use Microsoft's Remote Desktop connection on a regular basis, there's a pretty good chance you've run into this problem: Eventually, you get an error that tells you that your Remote Desktop License http://jeffpicard.com/blog/computer-fixes/microsoft-remote-desktop-licensing-fix/ will expire in "X" number of days. If you try to google a solution to this problem you'll be inundated with accusations that you're stealing the program and that you should go pay for a valid license. How can you be stealing something that is included with most modern versions of the Windows operating system? Without going into just why this happens, the solution is actually terminal server pretty easy. The following procedure is for either Windows Vista or Windows 7. Read below and follow the instructions closely:Click on the Start button and in the search box type "regedit" (without the quotes)The Regedit program should be highlighted at the top of the start window. Either simply hit ENTER, or double click it.In Regedit, navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensingRight click on the key name terminal server licensing "MSLicensing" and select DELETE.Close RegeditDo NOT open any shortcuts for Remote Connections at this point. Instead, you need to open the Remote Desktop Connection Manager. It's VERY important that you do this by RIGHT clicking on the program and selecting "Run as administrator." If you don't do this properly, the registry key you deleted in step 4 will not be recreated. The Remote Desktop Connection Manager can be found at: START/All Programs/Accessories/Remote Desktop Connection.Select the remote connection you want to use and click "Connect." If you've done this properly, a new registry key will be added that will have updated licensing information.This fix will need to be redone on a somewhat regular basis. I think I've got to do this about two to three times a year. 42 Responses to "Remote Server Licensing Fix" Kanchana May 14, 2012 at 5:35 am | PermalinkThis is not fixing my issue in windows 7. 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 Jeff May 22, 2012 at 10:33 am | PermalinkHey guys. I used this fix w