Terminal Services Licensing Diagnosis Snap-in extension

  • Comments 11

Identify potential licensing problems for the terminal server.

In Windows server 2008, a new snap-in extension, Licensing Diagnosis, has been added to the terminal server configuration snap-in to assist the administrator in managing and maintaining terminal servers.  Licensing Diagnosis can analyze a terminal server and highlight potential service-affecting issues that might be encountered due to the configuration of the terminal server/ license server deployment in the network. 


Licensing Diagnosis is primarily designed to:

1)      Determine whether a user or computing device will be allowed to connect to a terminal server. 

2)      Determine which license servers are discoverable by the terminal server and whether these license servers have TS CALs available to issue to users or computing devices that are connecting to a terminal server. 

3)      Identify any potential licensing problems and provide suggested resolutions to these problems.


Licensing Diagnosis is not designed to:

1)      Analyze and configure license servers in the network.  The TS Licensing Manager tool already exists to analyze, configure, and manage a license server.

2)      Act as a remedial tool to automatically configure or fix identified licensing issues for a terminal server.  It is a diagnostic tool, a self-help guide, to identify potential problems and recommend probable solutions.


Running Licensing Diagnosis

Licensing Diagnosis must be run by a user having administrator privileges.  In a domain, it is recommended that a domain account with administrator privileges be used to ensure optimal usability and results.

To run the Licensing Diagnosis Snap-in

1.      Open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.

2.      In the left pane, click Licensing Diagnosis. Licensing Diagnosis will automatically try to discover license servers and identify licensing configuration problems and then display the results.


Once Licensing Diagnosis is launched, the following screen appears.  (Click for full-size image.)

Licensing Diagnosis 

There are four main sections to Licensing Diagnosis:

1.       Terminal Server Configuration Details displays status and configuration information for a terminal server.  It also contains the Summary of Licensing Diagnosis which is used to convey the overall state of the Terminal Server Configuration.

2.       Licensing Diagnosis Information displays identified licensing problems along with suggested solutions.  For more information about potential problems, refer to Licensing Diagnosis: Problems and Resolutions.

3.       Terminal Services License Server Information displays the license servers that are discoverable by a terminal server.

4.       License Server Configuration Details displays status and configuration information about a license server.


In addition, the action pane for Licensing Diagnosis contains several action items such as ‘Refresh,’ ‘Provide Credentials,’ and ‘Launch TS Licensing Manager’ to facilitate diagnosis.


Additional references

·      Windows Server 2008 TechCenter

·      What’s new in Terminal Services Licensing – Licensing Diagnosis

·         Summary of Licensing Diagnosis

·         Licensing Diagnosis: Problems and Resolutions


Leave a Comment
  • Please add 6 and 4 and type the answer here:
  • Post
  • Windows Server 2008 adds a new snap-in extension, called Licensing Diagnosis, to its roster of terminal

  • Understanding the licensing state of a terminal server though Licensing Diagnosis Summary of Licensing

  • Understanding the licensing state of a terminal server though Licensing Diagnosis Summary of Licensing

  • What about TS licencing management in non domain enviroment?

    We have many customers runnin TS 2003 in workgroup enviroment where they have installed TS CALs per user and have activated licence server with OLP licences in it but it doesn't distrubute (it says it has 10 of 10 free licences).

    Also, will u make TS 2008 to deny any remote loging on it if user/device doesn't have his (TS)CAL?

    This would be great help for us administrators because its hard to learn bosses/customers why they need to pay licences while it can "work" without it :(

  • Per-user licensing is on an honors basis, i.e. if the TS (which is in per-user mode) can contact an activated 2003 TSLS that has at least one per-user TSCAL installed, the connection is granted. In 2003, per-user TSCALs are neither issued, nor tracked.  In 2008 the per-user licenses are tracked, for your own reporting needs.

  • So what r u saying that for easy licence administratoring u suggest per device TSCALs, no matter that per user r more logical than per device in todays IT enviroment.

    I read in my MCSE 2003 books that per user licencing was introduced to help us and save some money, but it's shown it's living hell and if u take all admin extra hour it's much more expensive than TSCAL per device!

    What happened with good "door" licences:"If u need access buy key(s)(CAL(S)) to access it!"?

    Why does Microsoft offer TSCALs per user while it has so much problems and lame support regarding it ?!

    Why, why, why .... WHY?

    Geather all your brains and fix licencing problems for sake of us all or 2008 will look like 2003 R3 (2003 R2 + Vista)!


    Tracking was possible with admin pack for Win 2003 too.

    TS 2003 can work without any TSCAL and without Terminal Licence server too!!! :-S

    How in a hell u plan to prolong licencing to yours customers while u allow to ppl to do everything wihtout it?!

  • You must have been a reporter in a previous life, as you completely misquoted me.  Where did I say that I suggest Per-Device Licensing?  What I did was explain how per-user TS Licensing works.  Whether one chooses per-device or per-user, completely depends on the business, i.e. a hospital with three shifts of 1000 users sharing the same computers could save close to $200K by licensing per-device (assuming all users don't access TS remotely).  If however the number of users is >= to the number of client devices, per-user TS licensing is definitely easier to manage at the same price.

    There are no problems that I'm aware of with per-user liceinsg, except that the business needs to track how many users are accessing TS, and in 2008 there are built-in reports to supply these reports.

  • LoL ... if I was reporter than u must been politician in previous life, because u said all and nothing at the same time.

    And what about rest what I said?

    U forgot to comment that too! ;)

    And what u meant by "no problems" with per user TSCALs?

    I hope u didn't refer to installing on workgroup enviroment that I spoke prevously.

    Because every kid knows to admin TS licencing in domain enviroment with >20 user/PC enviroment.

    Why Microsoft feel so ashamed of small bussiness (workgroup enviroment) that gives them lame support?

    Because I was speaking about small enviroment and their problems regarding lack of software support because most of tools require domain.

    U may ask yourself why then "I" (I refer to ppl who also have same problem(s)) don't install domain then?

    Answer is simple, lack of customers money to have IT staff inside his firm to admin whole enviroment plus they should have to update all he PCs to XP Pro / Vista Bussiness.

    There comes Microsoft VOLUME licencing ...

    But their PCs r running OEM Win 98 SE or OEM XP Home because its almost half cheaper than thoes who they need to update and also gives what they need.

    Small companies ain't ashamed to have "home" versions, because they look for cheaper legal versions not named as "bussiness" because it's "bussiness product".

    Because for example HQ with 4 PCs and 4 dislocated shops is perfect example of use TS 200x in small bussiness enviroment.

    They bougth server just for thoes dislocated locations to work and share same bussiness aplication using their low cost Internet (ADSL2+).

    Also I must note that ppl who work at cash register aint that PC "handy" as they should be.

    So if u wish domain you should educate staff too!

    So customer pays 3-4k$ for: server, OS + CALS + TSCALS and UPS. And expects that for that kind of money it runs by itself!

    So at the end let me give my final notes what I was trying to explane u:

    1. Lack of support for TS Licences per-user in workgroup enviroment

    2. Giving access to TS without any licence at all (CAL and TSCAL!)

    3. Help admins to work their job with ease, not by googling for ages to find other "victom" who find a hack to make it happen

    4. Microsot NON understanding for real needs in SB enviroment.

  • Hi Domagoj,

    I was going through your post above and it seems that you are not very happy with the current state of licensing through TSCALs espeically in PerUser mode.  I just wanted to comment on some of these issues.

    1. Lack of support for TS Licences per-user in workgroup enviroment

    You are right.  This is absent and as far as I know, this is not going to be available in W2K8.  The solution put forward by MS is based on having an AD and will not work in a workgroup.  That being said, since MS is not enforcing PreUser, even if you are not compliant, no connection will be denied.  Tracking of information will be almost impossible but still an admin who wants to be compliant for the most part can make an educated guess about the number of people who might access a TS and buy the appropriate TS CALs.  If you do not do this, MS wont come knocking at your door.  Its almost similar to any software where a software vendor specifies its terms of usage and the buyer can comply by it or break the rules.  MS has just provided some infrastructure in W2K8 so that u can identify and verify if you are compliant but you may choose to ignore it.

    2. Giving access to TS without any licence at all (CAL and TSCAL!)

    This seems like something which had been done for the benefit of the admins.  I think all things such as TS grace period or temp cals ( and even non-enforced peruser) have been put inplace for the benefit of the admins.  This has been placed so that the admins who want to be compliant, can be compliant (and are given time to be compliant) without adversely affecting the TS deployment.

    3. Help admins to work their job with ease, not by googling for ages to find other "victom" who find a hack to make it happen

    I think this licensing diagnosis is a great tool and is an effort from MS towards helping admins.  There may be still a lot that may be needed but I would suggest you come up with suggestions for MS rather than just bickering about the current situation.  Write a mail to the blog writer for suggestions and who knows he might just respond.

    4. Microsot NON understanding for real needs in SB enviroment.

    Cant comment on this in detail.  But again, if you think there is something you require, it will probably be best to provide description of what you want and need rather than complainting that MS doesnt understand your needs.  BTW it seems that MS might come up with some new features in the next version of the server.  I agree that MS seems to be slow getting there, but better late than never, I would say.



  • Licensing problems and resolutions for the terminal server Licensing Diagnosis is capable of diagnosing

  • Licensing problems and resolutions for the terminal server Licensing Diagnosis is capable of diagnosing

Page 1 of 1 (11 items)

Terminal Services Licensing Diagnosis Snap-in extension