Troubleshooting Terminal Server. The terminal server cannot issue a client license. You can set the RestrictAnonymous registry value to 2 if both the license server and the terminal server are Windows Server 2003based servers. How to reset RDC client license on Windows 7 Windows Registry Editor Version 5. Troubleshooting Terminal Server Licensing Issues Part 2If you would like to read the other articles in this series please go to In part one of this four part series, we looked at the most popular licensing related issues pertaining to license server availability. In this segment, as well as in part three well examine some additional common server related issues and conclude with client side common issues in part four. No Licenses Available on License Servers. Another common issue is simply running out of licenses. This is most often due to inadequately planning for the proper number of connections to the farm. Available licenses can be observed in the Terminal Server Licensing program, so thats the first place to look. The different pools, or types, of licenses will be displayed along with the total number of licenses in each pool, the number allocated and how many remain. If you double click on a particular pool, more details will be displayed including the machine name to which it was issued, when it was issued and when the CAL expires. Two event IDs common when the license server can be reached but is out of licenses include Event IDSource. Description. 10. 00. Term. Service. Unable to acquire a license for user lt user, domain lt domain 1. Term. Service. The terminal server cannot issue a client license. Term. Service. The terminal services client lt clientname has been disconnected because its temporary license has expired. Event IDs 1. 00. 0 and 1. ID 1. 01. 1 may be logged if the client has a temporary CAL and it has expired. If this occurrs, then licensing counts are not sufficient to handle the actual number of connections. To resolve this, purchase and add more device CALs. Using LSREPORTLSREPORT, another great utility in the resource kit, can display detailed information about the issue status of the CALs in the licensing database. The following command line arguments can be used with LSREPORT F filename  Output file nameD start endOnly licenses from start to endTOnly temporary licensesWInclude Hardware. Terminal Server Remote Desktop Services licensing. If an unlicensed client connects to a Terminal Server for the. The license is stored in the clients registry. Terminal Server License ErrorAn overview of new functionality provided by Terminal Services Licensing TS Licensing. A Terminal Services license server is a computer. Registry Keys for Terminal Services. The relevant configuration options for terminal servers, terminal server sessions, users, and clients can be found in different. When working with Windows 2000 Terminal Services Licensing, its important that you understand the three license server discovery methods and the registry option for. Terminal Server License Servers Group' title='Terminal Server License Servers Group' />ID in reportserverlist. List of license servers. Usage  LSREPORT W F c report. Figure 2 LSREPORTIn some circumstances, its possible that a client may lease more than one CAL thereby prematurely consuming all the CALs in the database, as seen in the above example. This is typical when the MSLicensing key has been deleted on the client. In most cases, a new client can connect using a temporary CAL until the allocated but unused CAL is returned to the pool through normal attrition. More detailed information on the MSLicensing key will be covered in part four. Paint Shop Pro 6 Hack Or Crack. Mixed Licensing Environments. There is a known issue with the licensing service in Windows Server 2. Windows 2. 00. 0 and Windows Server 2. Normally, Windows 2. CALs were available on Windows Server 2. However, a bug in the Windows Server 2. LServer. exe prevents this from occurring. This could lead to a failure to accept the connection and may appear to be intermittent. Typically, the following circumstances accompany this issue Your environment consists of a mix of both Windows 2. Windows Server 2. The Windows 2. 00. Server based license servers have no available permanent CALs. The Windows Server 2. CALs. The connecting client is running an older version of Windows, such as Microsoft Windows 9. This issue has been fixed in Windows Server 2. SP2, but a hotfix is available from Microsoft to address the problem on Windows Server 2. SP1 and earlier more details are available in Microsoft KB Q9. Contact Microsoft Product Support Services to obtain the hotfix. Terminal Servers in the Wrong Licensing Mode. This is another common issue. It used to be much more popular before Windows Server 2. SP1 as there was a bug in the AddRemove programs process. If you added a Windows component at any time after installing Terminal Services, the registry value Policy. Ac. On would get set to an invalid value of 0 and would cause the server to revert to per device mode. This issue was corrected in SP1. The two modes still seem to confuse a lot of people. Windows Server 2. Terminal Servers can be in one of two licensing modes  either per user or per device. The choice pertains to whom or what leases the CAL, or more importantly, which CALs were purchased. Per device CALs are leased to machines or devices, while per user CALs are allocated to named users. Per device CALs are explicitly leased to clients and are recorded in the license servers database. Upon first connection, clients are given a temporary access license, which is good for 9. The second time the client connects, and on each subsequent connection until successful, the terminal server will attempt to upgrade the temporary CAL to a permanent one. Permanent CALs are leased for a limited amount of time up to 8. Per user CALs are not leased as there is currently no tracking mechanism available to tie a terminal services CAL to a user account. Therefore, terminal servers in per user mode only check for license server availability, but never actually lease a CAL to the user. If the terminal server can contact the license server, it simply accepts the connection. The important point here is the licensing mode that is in effect is determined by the terminal server, not the license server or the CALs installed. If you are licensing Terminal Services in per user mode allocating CALs per named user, then be sure you are in the appropriate mode, and have verified this is set correctly on all terminal servers in your environment. This can be adjusted in the Terminal Services Configuration program from Administrative Tools at any time and does not require a reboot or a restart of services. Common symptoms of an incorrect licensing mode are event log entries for event ID 1. If you see this on only one terminal server out of the farm, then definitely check the licensing mode on the misbehaving box. You can also automate the process of checking or setting this value by creating a script to query the value in the following registry key HKLMSystemCurrent. Control. SetControlTerminal. ServerLicensing CorePolicy. Ac. On. The two valid entries are 2 for per device mode and 4 for per user mode. A value of 0 indicates that this was set as a result of the pre SP1 bug noted earlier. Large Licensing Database Issues. Although uncommon, some terminal server licensing databases may become large. If the database reaches around 8. MB or more, there may be problems with the licensing service. This issue is usually accompanied by the following event in the Windows event log Event IDSource. Description. 43. Term. Serv. Licensing. Work Manager error Cant Startup work scheduler, Error code 1. There is a known issue with licensing databases that are larger than 8. MB in size.  The licensing service uses a Microsoft Jet based database engine, and the transactions involved in a large database can consume a lot of memory. If a transaction hangs or runs for an extended period of time for instance, it cant complete because the disk is full, this can cause Jet to consume the entire Version Store, crashing the service. In case you are wondering, the Version Store is used in Jet based databases as an in memory cache used to hold pending transactions until they can be written to disk. Microsoft included a new registry key in Windows Server 2. Version Store in Jet transactions. If you find you have a large database and are seeing event ID 4. HKLMSystemCurrent. Control. SetServicesTerm. Serv. LicensingParameters. Add a new Value called Max. Ver. Pages REGDWORD with a value data of 1. Most likely, you will not see this issue except in extremely large terminal server deployments of several hundred nodes. For more information on this issue, check out Microsoft KB article Q3.