Licensing terminal services server 2008

Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Remote Desktop Services Terminal Services. FileName: This is an output parameter containing the file name of the report generated. This file name can be used to perform other operations on the report like Delete and FetchReport. DeleteReport: This interface is used to delete an existing per user usage report.

This is not a static function and must be called from the per user report object. FetchReportEntries: This interface is used to get the user name and other information from a per user usage report. This tool is not a static function and must be called from a per user usage report object. This class has three members:.

Historically, there was no way to do it. An administrator would have had to wait until the CAL expired or lost its validity and was automatically reclaimed by its mechanism. An administrator has to also select the specific client whose CAL needs to be revoked.

But there are certain restrictions on the number of CALs that can be revoked at a given time. This is a restriction imposed by the License Server to prevent misuse.

A CAL goes into a revoked state right after revocation, and its state is cleared when it goes past its original expiration date. When the administrator has exceeded this limit, he is given a date when further revocation is possible.

TS CALs can only be revoked when it is reasonable to assume that the machine they were issued to will no longer participate in the environment, for example, when the machine failed. Client machines, no matter how infrequently they may connect, are required to have a TS CAL at all times. This also applies for per user licensing. Our expert will look at four different troubleshooting scenarios in this next sidebar:. The Diagnostic tool does not report all possible problems in all possible scenarios during diagnosis.

However, it collates the entire TS Licensing information of Terminal Services and the License Servers at a single place and identifies common licensing configuration errors. Upon launch of the Licensing Diagnosis tool, it first makes up a list of License Servers that the terminal server can discover via auto-discovery and also those that can be discovered via manual specification by using either the Use The Specified License Servers option in TSConfig.

It then contacts each License Server in turn to gather its configuration details, such as the activation state, License Key Pack information, relevant Group Policies, and so on. For this to work properly, we need to make sure that the Licensing Diagnosis tool has been launched with credentials that have administrator privileges on the License Servers.

If needed, use the Provide Credentials option to specify appropriate credentials for each License Server individually at run time. A summary of diagnostic messages, with the possible resolution steps, is provided by this tool at the end of diagnosis.

The terminal server has just been set up, and the licensing mode of the server has remained in Not Yet Configured mode. Within the grace period of days, TS has allowed connection to clients. Past the grace period, the administrator observes that the clients are no longer able to connect. The administrator launches the diagnostic tool and finds that two diagnostic messages are reported.