Prev: Cannot anymore connect on TS 2003 from remote office
Next: Printer Settings not saving/RDPDR Key Problem
From: DEI on 21 Mar 2008 08:38
WOW thanks for the link! I just found killer site to add to my arsenal!
hehe


"Vera Noest [MVP]" <vera.noest(a)remove-this.hem.utfors.se> wrote in message
news:Xns9A6873024DCE5veranoesthemutforsse(a)207.46.248.16...
> No need to do anything at all. Details are explained here:
>
> How can I revoke an issued license to make it available for a new
> client?
> http://ts.veranoest.net/ts_faq_licensing.htm#revoke_licenses
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "DEI" <dei(a)nospam.com> wrote on 21 mar 2008 in
> microsoft.public.windows.terminal_services:
>
>> I don't mean to steal his post, just want a clarification. If I
>> use device CAL's and replace my workstations will I have to buy
>> additional CAL's since they were issued to the other
>> workstations? Is there a way to clear or delete them to keep
>> them from consuming license? What about user license? (with
>> employee attrition)


From: DEI on 21 Mar 2008 09:09
I've read your FAQ. I saw something that raises the question, if I move my
TS from one domain to another will my current LS expire the moment I
activate my new LS or am I allowed a grace period? Or is it honor system?

I have a feeling my current one isn't issuing them correctly anyhow. I have
'not applicable' under issued for user CAL and that is the license mode on
my TS, however I have a very large number issued under device cals. We use
thin clients and we have the write filter turned off, meaning nothing is
retained after shutdown.


"Vera Noest [MVP]" <vera.noest(a)remove-this.hem.utfors.se> wrote in message
news:Xns9A6873024DCE5veranoesthemutforsse(a)207.46.248.16...
> No need to do anything at all. Details are explained here:
>
> How can I revoke an issued license to make it available for a new
> client?
> http://ts.veranoest.net/ts_faq_licensing.htm#revoke_licenses
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "DEI" <dei(a)nospam.com> wrote on 21 mar 2008 in
> microsoft.public.windows.terminal_services:
>
>> I don't mean to steal his post, just want a clarification. If I
>> use device CAL's and replace my workstations will I have to buy
>> additional CAL's since they were issued to the other
>> workstations? Is there a way to clear or delete them to keep
>> them from consuming license? What about user license? (with
>> employee attrition)


From: Vera Noest [MVP] on 21 Mar 2008 11:20
First of all, the Licensing Server itself does never expire.
It's the Terminal Server which has a grace period, and it can only
have that once. So if you move your TS to a new domain, you will
not get a new grace period. It will need to connect to a LS with
valid TS CALs, or otherwise it will refuse connections.
Activating a new LS has no effect on any existing LS. You can have
as many activated Licensing Servers as you want (2 is common, for
redundancy reasons).
You can not, however, install the same license pacj which was
installed on the first LS onto your second LS. You will need to
call the Clearinghouse to get a new license pack if you need to
move your licenses from one LS to another.

Now to your current situation: Per User licenses are unmanaged, so
the "Issued" count will always say N/A. As long as your TS is
configured to use the Per User licensing mode and it can locate the
LS, everything is as it should.
The high number of Per Device TS CALs that you see in LS Manager
have probably been issued before you switched the TS to Per User
licensing mode. You can verify this by looking at the dates they
were issued.

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

"DEI" <dei(a)nospam.com> wrote on 21 mar 2008 in
microsoft.public.windows.terminal_services:

> I've read your FAQ. I saw something that raises the question,
> if I move my TS from one domain to another will my current LS
> expire the moment I activate my new LS or am I allowed a grace
> period? Or is it honor system?
>
> I have a feeling my current one isn't issuing them correctly
> anyhow. I have 'not applicable' under issued for user CAL and
> that is the license mode on my TS, however I have a very large
> number issued under device cals. We use thin clients and we
> have the write filter turned off, meaning nothing is retained
> after shutdown.
>
>
> "Vera Noest [MVP]" <vera.noest(a)remove-this.hem.utfors.se> wrote
> in message
> news:Xns9A6873024DCE5veranoesthemutforsse(a)207.46.248.16...
>> No need to do anything at all. Details are explained here:
>>
>> How can I revoke an issued license to make it available for a
>> new client?
>> http://ts.veranoest.net/ts_faq_licensing.htm#revoke_licenses
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "DEI" <dei(a)nospam.com> wrote on 21 mar 2008 in
>> microsoft.public.windows.terminal_services:
>>
>>> I don't mean to steal his post, just want a clarification. If
>>> I use device CAL's and replace my workstations will I have to
>>> buy additional CAL's since they were issued to the other
>>> workstations? Is there a way to clear or delete them to keep
>>> them from consuming license? What about user license? (with
>>> employee attrition)
From: DEI on 21 Mar 2008 12:01
Under Temporary License I looked at the dates and it is showing current
dates such as this month. It appears that some are getting a new license
every time it is turned on!

If the issued field shows NA how will I know if I'm about to run out of TS
license?

So if I have only a total of 130 TS license and I want to have two TS
servers (renduncey purpose), will I need to split the 130 (if possible) and
put part of them on one server and the rest on another server or will I need
to purchase more? Sorry if I'm asking a lot of questions, I just want to be
in compliance.

Thanks!


From: Vera Noest [MVP] on 22 Mar 2008 07:29
comments inline.

"DEI" <dei(a)nospam.com> wrote on 21 mar 2008 in
microsoft.public.windows.terminal_services:

> Under Temporary License I looked at the dates and it is showing
> current dates such as this month.

But when did you changed the TS to use the Per User licensing mode?
Have new temporary licenses been issued *after* that date?

> It appears that some are
> getting a new license every time it is turned on!

Didn't you write in a previous post that your clients are thin
clients? A new license for every connection is a known problem with
some thin clients. But that will stop now, since Per User licenses
are not issued at all.

> If the issued field shows NA how will I know if I'm about to run
> out of TS license?

You will have to keep track of the total number of connecting users
by hand. One way to do this is to keep strict control over who is a
member of the Remote Desktop Users group, and make sure you have a
TS CAL for every member. Another way is to do some scripting and
generate logs over who connects.

> So if I have only a total of 130 TS license and I want to have
> two TS servers (renduncey purpose), will I need to split the 130
> (if possible) and put part of them on one server and the rest on
> another server or will I need to purchase more? Sorry if I'm
> asking a lot of questions, I just want to be in compliance.

You don't have to buy more licenses to create a redundant Licensing
Server.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Cannot anymore connect on TS 2003 from remote office
Next: Printer Settings not saving/RDPDR Key Problem