TS CAL on thin client device

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.

Javier
Wed Jul 13 08:03:42 CDT 2005

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@test.com> wrote in message
news:ORpvUO5hFHA.1048@tk2msftngp13.phx.gbl...
> 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.
>
>

Mike
Wed Jul 13 10:02:05 CDT 2005

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@remove.this.engineer.com> wrote in
message news:OkJ$Mt6hFHA.708@TK2MSFTNGP09.phx.gbl...
> 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@test.com> wrote in message
> news:ORpvUO5hFHA.1048@tk2msftngp13.phx.gbl...
>> 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.
>>
>>
>
>