Windows Terminal Services Licenses 2

[GiaBetiu]

I saw a lot of questions about Terminal Services Licenses.
Thus, I decided to write an article with some guidelines.
The article is based on the Microsoft white papers, and some details from Microsoft site.
What i did, was just a summary of those documents, pointing some important issues.

If you want to see it,

http://www.almondeyes.net

go to Windows /Advanced /Windows 2000 Terminal Services Licensing

I hope that this will help.


Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[victorv]

hi,
I had a look to your site, very nice, and I have found it
very interesting, star for you; I hope you will write other
interesting articles.

At a my customer I have this situation

- 2 DC AD, and Terminal Server License installed and
activated on one.

- 11 Terminal Servers (with is also Citrix-Metaframe)

- On DC and TS there is W2K - SP2 + hotfix Q287687,
and TS have HKLM\CurrentControllSet\Services TermService\Parameters\DefaultLicenseServer set to LS

On TLS, I have inserted various set of lincense packs.

The first 20 are in a branch of the tree with a
description.
The next 120+120 went in another branch
with another description.
Then there is the temporary branch, and here is all ok.

Well, the 20 license was all iussed, without ending time.
Of the 240, 210 have been iussed, and 30 available (+/-).

The first 100 +/- ( in time iussuing order ) of the 210
are without ending time, while the next (the more recent
iussued) have a end time although are in bought group and
there are still available tokens.

Why "permanent" tokens have a end-time ?

This creates problem becouse at end-time the client
(a winCE WinTerm ) stops to go; an operator brings
to user a new Term and a new license is iussed
(sometime from available pool or from temporary)

This does not create economic problems becouse that
bought+end-time rows seems to be recovered: the problem
is of service, the operator has to run to change the
terminal and the user may stay out of service for a while.

Some ideas ?

bye

 

[mp1976]

Hi Gia

I checked out ur site . It is really terefFFFFFFic.
Nice stuff about win2k. I am planning to give win2k server exams. Any tips on how should i study for the exam.

Thanks

PS.:- U look great.

 

[GiaBetiu]

Hi,
Thanks for your appreciation.

Yes, i think is because of the new features added by the SP3 or that Security RolloutPackage1.
1. Post-Logon License Issuance
This time, when a device accesss for the first time the TS server, TS server will give to the device a temporary license. Then, next time the license will be coverted to a real TS CAL if there are available TS CALs. If not, of course will be denied.

2. Automatic License Token Re-issuance
This is the issue that you have seen it on your latest logged on computers. The fact that the tokens have a life time (random 52-89). This is not so bad. Because the tokens that are not renewed will be returned back into the pool.

For more details see this:

http://www.microsoft.com/windows2000/techinfo/howitworks/terminal/TSLicensing.asp

(of course, i should add this too the article i wrote too)

Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[MaYHeM24]

I just got off the phone with MS Licensing and they said you Do Not need to install licenses on the server side if you are accessing that server, via term services application mode, from a Win2k Professional or WinXP Professional machine. I've been using mine this way, without installing licenses on the server side, for 2 years. I just activated the server and that's it. Those two OS's come with a CAL for TS! The Licensing on the server side is for computers accessing it from a Win9x or thin client.

-=MaYHeM=-
-=IS MGR=-

 

[GiaBetiu]

Yes MaYHeM24, just that "TS CAL" is one thing, and "Server CAL" is a different thing.
Read my article about this. The article however is a synthesis from some Microsoft articles, that indeed are leaving the room for confusions.


Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K

http://www.almondeyes.net