Terminal server temporary license

Check Microsoft KB The issue it's reporting is supposedly fixed in SP1 and later, but I've seen this issue over and over again. If the reg entry it wants you to modify doesn't exist then create it as a DWORD and set it to per user or per device. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Asked 12 years, 6 months ago. Active 12 years, 6 months ago.

Viewed 6k times. If I run licmgr. Any ideas how to fix the underlying problem though, or what may be causing it? Improve this question. Rob Bobbit Rob Bobbit. By default, the remote desktop connection runs as a user with the lowest user permissions.

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. Check whether the problem is fixed. If the problem isn't fixed, contact support. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.

Please rate your experience Yes No. The second license is a Client Access License for the server. This is the standard server access license measured in License Manager, the same utility that is in Windows NT Server. License Manager does not distinguish between RDP client access and other types of server access for example, it does not distinguish between a normal shared file and printer resource access.

Terminal Server License Manager reports but does not enforce licensing. 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.