Licensing Diagnosis: Problems and Resolutions

Licensing Diagnosis: Problems and Resolutions

  • Comments 19

Licensing problems and resolutions for the terminal server

Licensing Diagnosis is capable of diagnosing potential problems in a typical terminal server/ license server deployment.  Here is the list of the potential problems along with their suggested resolutions.

ISSUES WITH DISCOVERY

Problem 1: The terminal server has not discovered any license servers.  If the grace period for the terminal server has expired, connections to the terminal server will be denied unless a license server is configured for the terminal server.

Resolution 1: Configure a license server for the terminal server. If you have an existing license server, use the Terminal Services Configuration tool to specify that license server for the terminal server. Otherwise, install TS Licensing on a computer on your network.

If you have configured a license server for the terminal server but the license server does not appear in the list of discovered license servers, use TS Licensing Manager to review the configuration of the license server.  TS Licensing Manager may be launched using the ‘Start TS Licensing manager' action item available in the action pane for Licensing Diagnosis tool.  For more information on reviewing the configuration for a license server, refer to How to review and configure a license server.

 

Problem 2: License server <Server Name> is not available. This could be caused by network connectivity problems, the Terminal Services Licensing service is stopped on the license server, or TS Licensing is no longer installed on the computer.

Resolution 2: Make sure you have network connectivity between the terminal server and the license server. Also check that the Terminal Services Licensing service is started on the license server. If TS Licensing is no longer installed on the computer, ensure that the license server is not manually specified and/or is no longer published in Active Directory Domain Services.  For more information on un-publishing a license server, refer to Un-publishing license server from AD .

 

ISSUES WITH CREDENTIALS

 

Problem 3: The Terminal Services Configuration tool is running with local account credentials. Licensing Diagnosis will not be able to discover domain or forest license servers automatically and the Total Number of TS client access licenses available value may be inaccurate.

Resolution 3: For best results with Licensing Diagnosis, use the Terminal Services Configuration tool with domain account credentials.

 

Problem 4: To identify possible licensing issues, administrator credentials for license server <Server Name> are required.

Resolution 4: Provide administrator credentials for the Terminal Services license server.  To provide credentials use the ‘Provide Credentials' action item in the action pane for Licensing Diagnosis.

 

ISSUES WITH CONFIGURATION

 

Problem 5: License server <Server Name> cannot issue TS CALs to the terminal server because of a version incompatibility.

Resolution 5: Check that the version of the license server supports issuing TS CALs to the terminal server. The license server must be running the same (or a more recent) version of the operating system as the terminal server. You might need to upgrade your license server to an appropriate operating system or install a new license server with the appropriate operating system.

 

Problem 6: License server <Server Name> is not activated.

Resolution 6: Use TS Licensing Manager to activate and install TS CALs on the license server.  TS Licensing manager may be launched using the ‘Start TS Licensing manager' action item available in the action pane for the Licensing Diagnosis tool.  For more information on activation and installation of TS CALs on a license server, refer to How to activate a license server.

 

Problem 7: License server <Server Name> cannot issue TS CALs to the terminal server because the "License server security group" Group Policy setting is enabled.

Resolution 7: Add the computer account for the terminal server to the Terminal Server Computers group on the license server. 

 

Problem 8: The licensing mode for the terminal server is not configured.

Resolution 8: Set the licensing mode on the terminal server to either Per User or Per Device by using Terminal Services Configuration tool. Use TS Licensing Manager to install the corresponding TS CALs on the license server.  For more information on installation of TS CALs on license server, refer to How to install CALs on a license server.

 

Problem 9: The terminal server is in <Per Device or Per User> licensing mode, but license server <Server Name> does not have any <Terminal Server Version> <Per Device or Per User> TS CALs installed.

Resolution 9: Use TS Licensing Manager to install the appropriate TS CALs on the license server.  If the license server has installed licenses of the other mode, changing the licensing mode for the terminal server may also resolve the issue.  To change the licensing mode, use the Terminal Services Configuration tool.

 

Problem 10: The terminal server is in <Per Device or Per User> licensing mode, but license server <Server Name> does not have any <Terminal Server Version><Per Device or Per User> TS CALs available.  (Note: The license server may have CALs installed but these CALs are currently not available for issuance.)

Resolution 10: Use TS Licensing Manager to install the appropriate TS CALs on the license server.  TS Licensing manager may be launched using the ‘Start TS Licensing manager' action item available in the action pane for Licensing Diagnosis tool.

Additional references

Leave a Comment
  • Please add 7 and 6 and type the answer here:
  • Post
  • Hi all,

    I've a problem with providing credential in Licensing Diagnosis. When a give a domain admin credentials, the authentication prompt again. What  kind of credential a need to provide?

    The TS Licensing Server is a domain controller (W2k8).

    Thank you for help (and sorry for my bad english)

    Best Reagrds

    JD

  • i have a terminal server both the license are on single machine every thing is wrk fine both i just both another user CALs and i want to add those new CALs to an exisiting CALs how am i going to go about it because have try all i could but is not working

    thanks

  • aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

  • Why does the Terminal Server create different strength keys when activating is doe directly or via Web Brower?

    For Conection=direct it creates 4096 key length and SHA256. For web browser connection based activation it creates 2048 key length and SHA1.

    The latter supports older client connects.

    ~josef

Page 2 of 2 (19 items) 12