Re: licensing

Tech-Archive recommends: Fix windows errors by optimizing your registry

1. A Windows 2000 Terminal Server does not know what a Per User TS
CAL is, and thus cannot use it. It's also impossible to configure
a W2K TS to use Per user licensing, so I don't know what you did
to make you believe that you have configured the server that way.

If your clients all run W2K Pro or XP Pro, then they will receive
a free TS CAL from the "Existing Windows 2000 Per Device Tokens"
which are present on the TS Licensing Server. But if you have
Windows 9x, NT4, Linux or thin clients, you must buy Per Dvice TS
CALs for these clients. An in your first post, you mention that
these licenses have an entry: Issued=0, so something seems to be
wrong.

2. No, you should not deactivate and reactivate the LS when
installing new licenses. I don't really understand what you have
done, but you seem to have installed a total of 70 Per user Open
licenses in total. If you have bought more licneses than that, you
will have to install them.

3. No, tokens are *not* per concurrent user, so they are *not*
released when they users logs off. Each individual user needs a
"personal" license.


_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?YXN1czYx?= <asus61@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
20 dec 2005:

> thank you, vera
> i have other questions
> 1- my Terminal Server Licensing is in windows 2003 with "CAL per
> User" and i have three application on on terminal server two on
> windows 2003 and one on windows 2000. All three are configured
> for to work with "per User". Now, i have a doubt. I see the link
> received from you, and i have understood that the application
> on windows 2000 terminal server are not possible receive the
> token from to Licensing server, is this very o false ???
> 2- i
> have purchase 70 (installed) + 70 licenses. For these last one
> i proceded with new activation ???
> 3- When a client to connect to terminal server, received the
> token , but when disconnect the token is released ?? or the
> token is blocked for the user ?? Cosequently, i have all 140
> client at the same time connect ???
>
> much kind one for your answer
> tanks you
>
>
> "Vera Noest [MVP]" wrote:
>
>> Yes, this is perfectly normal.
>> I assume that you are worried about the "Not Applicable" entry
>> for your Per User licenses?
>> That's because Per user TS CALs are currently unmanaged. You
>> will have to keep track of the total number of users by hand.
>>
>> Documented here:
>>
>> 822134 - The Function of Terminal Server CALs in Windows Server
>> 2003
>> http://support.microsoft.com/?kbid=822134
>>
>> Note: your Terminal Server must also be put into Per user
>> licensing mode for this to work. You can check this from
>> Administrative Tools - Terminal Services Configuration - Server
>> Settings - Licensing Mode
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?YXN1czYx?= <asus61@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> on 19 dec 2005 in microsoft.public.windows.terminal_services:
>>
>> > I have any question on Windows 2003 Server with activated
>> > Terminal Server Licensing.
>> >
>> > i have purchase a 70 TS per user CAL
>> >
>> > 1 question - in the panel of Terminal Server Licensing on
>> > server B i have : Existing Windows 2000 Server - TS CAL token
>> > (per device) : type=Built In : Total=Unlimited :
>> > Avail=Unlimited : Issued=0 Windows Server 2003 - TS per User
>> > CAL token : type=Open
>> > : Total=70 : Avail=70 : Issued=Not Applicable
>> > Is this regular ?? because i have trapassing the 90 days of
>> > utilization with server applications in TS emulations ?
>> >
>> > 2 question - i have move the activation from server A to
>> > server B, before i have deactivated server A (where are 30
>> > token installated). After i have installed on server B ALL 70
>> > token with egual authorization number and license number .
>> > Is this procedure correct ??
>> >
>> > thank you
.

Relevant Pages

  • Re: Licensing
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... SQL troubleshooting: http://sql.veranoest.net ... Terminal Services Configuration - Server Settings - Licensing ... User TS CALs. ...
    (microsoft.public.windows.terminal_services)
  • Re: Event ID: 1004 - Trm srvr cannot issue a client license. Need advise?
    ... original request I installed the Terminal Server Licensing on the ... Windows 2003 domain controller and ... the terminal server licensing on it. ... Is my fix as simple as installing the windows 2003 ...
    (microsoft.public.windows.terminal_services)
  • Re: thin client license
    ... very old issue, that has been solved since Windows 2000, Service ... I would spend some time reading the Licensing FAQ: ... Device TS CALs. ... MCSE,CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: TS Licensing Issue
    ... You must change the licensing mode of your Terminal Server to the ... TS CALs, it will issue temporary Per Device TS CALs, which will ...
    (microsoft.public.windows.terminal_services)
  • RE: Licensing
    ... It's difficult enough to get the licensing requirements ... > Licensing Microsoft Office in a Windows Terminal Server Environment ... > a Windows CAL for every client, then all clients have the right to ... >>> Since you already have more than enough Windows CALs and TS ...
    (microsoft.public.win2000.termserv.apps)