Re: TS CAL on thin client device

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



Javier,

Thanks, that clarifies things.

Much clearer than mud - nice to know it's not going to be a problem.

Mike.


"Javier Gomez [SBS MVP]" <javier_gomez@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OkJ$Mt6hFHA.708@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Mike,
>
> This is actually an interesting question... and the bottom line is that
> you don't need to do anything for licenses to get transferred in your
> situation (replacing a broken device). Let me explain what happens:
>
> 1) When you connect a Thin Client to a Terminal Server it will request a
> "permanent" license. But this license has to be renewed a random day
> between 45 to 89 days. If the device doesn't renew the license it goes to
> the "free" pool again.
>
> 2) If you try to connect to a Terminal Server and there are no CALs
> available then the server will issue a temporary CAL (that cannot be
> renewed, except converted to a permanent one) for exactly 90 days.
>
> Since the new device will get a Temp CAL for 90 days and the old one will
> loose it in or before 89 days then the old license its always released
> *before* its needed. Hence its automatically tranferred.
>
> Clearer than mud? :-)
>
> --
> Javier [SBS MVP]
> www.msmvps.com/javier
> << SBS ROCKS !!! >>
>
> "Mike" <test@xxxxxxxx> wrote in message
> news:ORpvUO5hFHA.1048@xxxxxxxxxxxxxxxxxxxxxxx
>> We have a number of systems out running thin client devices such as the
>> Wyse Winterm product or similar. Although I was able to find an MS
>> technical article about how to transfer the TS device CAL from one thin
>> client PC to another (in the event of hardware failure) as this entails
>> editing the registry on the client PC to remove the license, it obviously
>> won't work on a thin client, as it only has Windows CE and no 'regedit'
>> command.
>>
>> So in the event of a Winterm failing and being replaced by the hardware
>> maintenance company, how would we get over the fact that Windows TS
>> Licensing would now consider this to be an extra user? So if the customer
>> had 10 TS device CALs, and ten thin clients, how do we swap one thin
>> client and not need to ugprade with extra TS CALs?
>>
>> Thanks,
>> Mike.
>>
>>
>
>


.



Relevant Pages

  • Re: TS CAL on thin client device
    ... (replacing a broken device). ... But this license has to be renewed a random day between ... If you try to connect to a Terminal Server and there are no CALs ... > We have a number of systems out running thin client devices such as the ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Thin Client Licensing
    ... to allow the terminal service to use the underlying server, ... a CAL/TSCAL pair for a user doesn't mean the Vista/XP license for the users workstation is for free... ... Thin Client" PCs will come or have, an OEM license and that should be fine. ... Regarding the CALS for TS, there are serveral licenses that you might buy ...
    (microsoft.public.windows.terminal_services)
  • Re: Cannot add 5 CAL users w2003
    ... > Then in W2003 the licenze manager works in a different way than in SBS2003 ... > where I could see how many CALS are installed and when I installed the ... >> Mike. ... >>> added in the License Manager application. ...
    (microsoft.public.windows.server.general)
  • Re: Cannot add 5 CAL users w2003
    ... CALs are currently installed. ... Mike. ... > added in the License Manager application. ...
    (microsoft.public.windows.server.general)
  • Re: TS client license issue
    ... CALs, you are allowed to switch them to Per User TS CALs when you ... Note that you would need a Per User license for every person who ... MCSE, CCEA, Microsoft MVP - Terminal Server ... there are 5 thin client terminal always connected to the ...
    (microsoft.public.windows.terminal_services)