If an RDP client is denied access to the server when it tries to make a connection, increasing the license count in Terminal Server License Manager will not resolve the problem.
Client Access Licenses must be added to License Manager. These licenses are good for 60 days. The RDP client making use of a temporary license will continue to do so for the full 60 days even if new licenses are added. After 60 days, the client's temporary license will expire, and the client will get a new license either a temporary license if no normal licenses are available, or one of the new licenses that have been added. Logging on at the Terminal Server console uses one Client Access License, but this is not reflected in the license count in License Manager.
In the event that only one Client Access License is available, RDP clients at the console or elsewhere will not be able to connect even though the License Manager in-use license count is zero. This is different from normal licensing behavior because administrators can always log on at the console or connect to the server remotely even if no licenses are available. Administrators must log on at the Terminal Server console, or access the server by means other than the RDP client, if the Terminal Server runs out of licenses.
When an RDP client is denied access, the client will receive the generic message: Terminal Server has ended the connection. Computers running Windows for Workgroups 3. Terminal Server License Manager creates seven temporary files in the System32 directory. The temporary files are called JET1. These files are used to temporarily store newly created licenses. It is possible to have more than seven JETx. TMP files. Right-click the license server you want to modify, and then click Properties.
To see a step-by-step guide for deploying Terminal Services Licensing, visit the following Microsoft web site:. Overview You must activate a license server before it can issue licenses to Terminal Services clients. In the console tree, expand All servers. Click Next. On the "Completing the Terminal Server Activation Wizard" page, do one of the following: To install client license key packs for your license server, click Next.
Close the Terminal Server Licensing window. Troubleshooting After a license server is activated, it becomes the registrar for Terminal Services client licenses. Need more help? Expand your skills. Get new features first.
Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. Before you start to perform the procedures that are described in the following sections, you must have the paper agreement that you received when you purchased the CALs.
In the Terminal Server Licensing snap-in, right-click the Terminal Services license server, and then click Properties. In the Installation method list, click Telephone , and then click OK. Right-click the Terminal Services license server, and then click Install Licenses.
Click Next. You can also contact Microsoft Customer Support Services at the following telephone number: For more information, click the following article number to view the article in the Microsoft Knowledge Base:. You'll receive a message that states that the CALs have been installed successfully.
0コメント