RE: How to control which clients are issued TS license?

From: Vera Noest [MVP] (Vera.Noest_at_remove-this.hem.utfors.se)
Date: 02/04/05 

Date: Fri, 04 Feb 2005 07:06:41 -0800

Some extra information:
 
The *first* time a client connects, it is given a temporary license.
That is done with the purpose to avoid your situation: since the
license is issued before it is known who the user is, a malicious
user could use up all your licenses.
During the *second* logon, the client receives a permanent license.

So it must be one of your authorized users who is running around and
logging in (at least 2 times) on different clients.

User education is the keyword here + limiting the number of
authorized users on the TS, instead of adding all Domain Users.

 --
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?UGF0cmljayBSb3VzZQ==?="
<PatrickRouse@discussions.microsoft.com> wrote on 04 feb 2005:

> You can't, unless you restrict (using a 3rd party app or IPSec)
> which computer can logon to the terminal server. If you've
> allowed too many computer to logon to the terminal server, then
> you need more TSCALs.
>
> http://www.workthin.com/tsls2k3.htm
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
> "nolan@easy.com" wrote:
>
>> I have a single Windows 2003 Server running terminal services
>> in a Win2k AD Domain. The terminal server is also the
>> licensing server. We are using per device licenses. How can
>> we control what clients (computers) are issued a TS license?
>> Is there a group policy for this?
>>
>> Our TS licenses are being chewed up because someone logs in one
>> time from a PC and is assigned a license. As I understand it,
>> we cannot revoke these licenses we simply have to wait for them
>> to expire in 52-89 days so we want to exert some kind of
>> positive control over this.
>>
>> Thanks for the help!
>>
>> Jeff

Relevant Pages

  • Re: per Device CAL
    ... >>> from a non-authorized client. ... >>> Let me give you an example: assume that you have 10 TS CALs, ... >>> thanks to its temporary license. ... >>> Noest MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing problem
    ... Have you tried to delete the temporary license from the client (by ... Terminal Server from Your WBT Device ... TS licensing server shows a valid licence ...
    (microsoft.public.win2000.termserv.apps)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... CAL user F will be granted a temporary license. ... client, which is good for 30 days. ... You must first buy and install TS CALs for your CE thin clients. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.apps)
  • kb 187614
    ... Just delete the registry key ... If an unlicensed client connects to a Terminal Server for the first time, ... Access License token. ...
    (microsoft.public.de.german.windows.terminaldienste)
  • Re: one terminalclient cant connect to terminal server.
    ... User/group has not been given the right to "Allow logon through Terminal ... We have a windows 2000 terminal server and a windows 2003 terminal ... terminal services client on windows 2000 workstations. ... I also checked the license server, ...
    (microsoft.public.windows.terminal_services)