Re: TermServ CAL issued to "Unknown" is locking one of my CALs!

"news" <news@xxxxxxxx> wrote on 16 aug 2005 in
microsoft.public.windows.terminal_services:

> Thanks very much, Vera, for your timely response and great
> information.
>
> Mia culpa: Last week I started to administrate this TS from my
> new Samsung i730 PocketPC phone using the built in Terminal
> Server client and Verizon's EVDO network. This must be the
> "unknown" machine name!! Its like I locked someone else's car
> keys it my own car!

To be frank, I suspected so. You were the most likely candidate :-)

>> * You cannot revoke issued TS CALs.
>> TS CALs have an expiration date of 52-89 days after issueing.
>> Licenses that are not used (because the client does not
>> connect to the TS anymore) will automatically be returned to
>> the LS after the expiration date. In the meantime, new clients
>> will get a temporary TS CAL, which is valid for 90 days.
>
> The "accounts" machine is not being issued a tempory TS CAL,
> though. Is this because it is not considered a "new" client?

That's likely, yes, if it has connected before. Each client can
only receive a temporary license *once* during its lifetime.

>> The only thing you can do is to wait until the license issued
>> to "Unknown" expires (which means you must make sure that users
>> stop connecting from unauthorized clients).
>
> Other than adding a new TSCAL to the server ($$), or waiting
> till the "unknown" license expires, is there a way to get the
> "accounts" machine back on to the network ?

Not without violating the EULA.

> It seems like I should be adding a per-user CAL for the
> Administrator account, which is the one I use from various
> clients as I remotely administrate their network. All of the
> other users use one of the 6 clients on a per-device basis.
> Would that be your advice?

No, this is not possible. You can install a mixture of Per Device
and Per User TS CALs on a single TS Licensing Server, but a single
Terminal Server can only use one type of licenses. You cannot mix
licensing modes on a TS.
Only solution I can see is to buy an extra license.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
.

Relevant Pages

  • Re: can someone help clear this up?
    ... Terminal Services Client Access Licenses are assigned to the client, ... The Terminal Services License Server ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • 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: per Device CAL
    ... non-authorized client. ... CALs for the first time. ... returned to the Licensing Server. ... client 11 will get its temporary license ...
    (microsoft.public.windows.terminal_services)
  • Re: Client disconnected problem
    ... Resetting a thin client to the factory default is ... That would lead to the issueing of a new license (the ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Client on the PPC. ...
    (microsoft.public.windows.terminal_services)