Temporary client license

[Guest jeffk]

I installed a terminal server (member server) on a SBS network and am now

getting the following pop up on the desktops: "Your terminal services

temporary client license will expire in 7 days. Please contact your system

administrator to get a permanent license." Is this anything that I need to

worry about? Will the permanent licenses start working without having to do

anything? If there is something I need to do, what is it? Help!

[Guest Lanwench [MVP - Exchange]]

Re: Temporary client license

 

jeffk <jeffk@discussions.microsoft.com> wrote:

> I installed a terminal server (member server) on a SBS network and am

> now getting the following pop up on the desktops: "Your terminal

> services temporary client license will expire in 7 days. Please

> contact your system administrator to get a permanent license." Is

> this anything that I need to worry about? Will the permanent

> licenses start working without having to do anything? If there is

> something I need to do, what is it? Help!

 

Did you buy TS CALs and install the Terminal Service Licensing bits on your

SBS box? (that's where I'd put them). Then you need to launch & activate

them/it. Then you point the TS box at the TS licensing server.

[Guest Vera Noest [MVP]]

Re: Temporary client license

 

"Lanwench [MVP - Exchange]"

<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote

on 19 mar 2008 in microsoft.public.windows.terminal_services:

> jeffk <jeffk@discussions.microsoft.com> wrote:

>> I installed a terminal server (member server) on a SBS network

>> and am now getting the following pop up on the desktops: "Your

>> terminal services temporary client license will expire in 7

>> days. Please contact your system administrator to get a

>> permanent license." Is this anything that I need to worry

>> about? Will the permanent licenses start working without

>> having to do anything? If there is something I need to do, what

>> is it? Help!

>

> Did you buy TS CALs and install the Terminal Service Licensing

> bits on your SBS box? (that's where I'd put them). Then you need

> to launch & activate them/it. Then you point the TS box at the

> TS licensing server.

 

And if you already installed permanent TS CALs on an LS (which your

post seems to suggest), does the licensing mode of your TS match the

type of licenses that you installed, i.e. Per User / Per Device?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

[Guest jeffk]

Re: Temporary client license

 

I haven't looked at the CALs since December, do they say whether they are

device r user?

 

"Vera Noest [MVP]" wrote:

> "Lanwench [MVP - Exchange]"

> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote

> on 19 mar 2008 in microsoft.public.windows.terminal_services:

>

> > jeffk <jeffk@discussions.microsoft.com> wrote:

> >> I installed a terminal server (member server) on a SBS network

> >> and am now getting the following pop up on the desktops: "Your

> >> terminal services temporary client license will expire in 7

> >> days. Please contact your system administrator to get a

> >> permanent license." Is this anything that I need to worry

> >> about? Will the permanent licenses start working without

> >> having to do anything? If there is something I need to do, what

> >> is it? Help!

> >

> > Did you buy TS CALs and install the Terminal Service Licensing

> > bits on your SBS box? (that's where I'd put them). Then you need

> > to launch & activate them/it. Then you point the TS box at the

> > TS licensing server.

>

> And if you already installed permanent TS CALs on an LS (which your

> post seems to suggest), does the licensing mode of your TS match the

> type of licenses that you installed, i.e. Per User / Per Device?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

[Guest jeffk]

Re: Temporary client license

 

I just looked on my server. The temp CALs are device CALs and the actual CALs

are per user. Is this going to cause any problems, and if so, can I change

the CALs to device CALs?

 

"Vera Noest [MVP]" wrote:

> "Lanwench [MVP - Exchange]"

> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote

> on 19 mar 2008 in microsoft.public.windows.terminal_services:

>

> > jeffk <jeffk@discussions.microsoft.com> wrote:

> >> I installed a terminal server (member server) on a SBS network

> >> and am now getting the following pop up on the desktops: "Your

> >> terminal services temporary client license will expire in 7

> >> days. Please contact your system administrator to get a

> >> permanent license." Is this anything that I need to worry

> >> about? Will the permanent licenses start working without

> >> having to do anything? If there is something I need to do, what

> >> is it? Help!

> >

> > Did you buy TS CALs and install the Terminal Service Licensing

> > bits on your SBS box? (that's where I'd put them). Then you need

> > to launch & activate them/it. Then you point the TS box at the

> > TS licensing server.

>

> And if you already installed permanent TS CALs on an LS (which your

> post seems to suggest), does the licensing mode of your TS match the

> type of licenses that you installed, i.e. Per User / Per Device?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

[Guest Vera Noest [MVP]]

Re: Temporary client license

 

Yes, that's a problem.

If you want Per Device TS CALs instead, you will have to call the

Clearinghouse to get a new license pack. Note that such a change is

only allowed if you have valid Software Assurance on your existing

licenses.

 

The other solution is to change the licensing mode of your Terminal

Server to Per User licensing. This is done in Terminal Services

Configuration - Server settings.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?amVmZms=?= <jeffk@discussions.microsoft.com> wrote on 19

mar 2008 in microsoft.public.windows.terminal_services:

> I just looked on my server. The temp CALs are device CALs and

> the actual CALs are per user. Is this going to cause any

> problems, and if so, can I change the CALs to device CALs?

>

> "Vera Noest [MVP]" wrote:

>

>> "Lanwench [MVP - Exchange]"

>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com>

>> wrote on 19 mar 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > jeffk <jeffk@discussions.microsoft.com> wrote:

>> >> I installed a terminal server (member server) on a SBS

>> >> network and am now getting the following pop up on the

>> >> desktops: "Your terminal services temporary client license

>> >> will expire in 7 days. Please contact your system

>> >> administrator to get a permanent license." Is this anything

>> >> that I need to worry about? Will the permanent licenses

>> >> start working without having to do anything? If there is

>> >> something I need to do, what is it? Help!

>> >

>> > Did you buy TS CALs and install the Terminal Service

>> > Licensing bits on your SBS box? (that's where I'd put them).

>> > Then you need to launch & activate them/it. Then you point

>> > the TS box at the TS licensing server.

>>

>> And if you already installed permanent TS CALs on an LS (which

>> your post seems to suggest), does the licensing mode of your TS

>> match the type of licenses that you installed, i.e. Per User /

>> Per Device?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

[Guest jeffk]

Re: Temporary client license

 

Will changing the TS to user CALs make a difference? I've changed it, but I

don't know what the ramifications will be.

 

"Vera Noest [MVP]" wrote:

> Yes, that's a problem.

> If you want Per Device TS CALs instead, you will have to call the

> Clearinghouse to get a new license pack. Note that such a change is

> only allowed if you have valid Software Assurance on your existing

> licenses.

>

> The other solution is to change the licensing mode of your Terminal

> Server to Per User licensing. This is done in Terminal Services

> Configuration - Server settings.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?amVmZms=?= <jeffk@discussions.microsoft.com> wrote on 19

> mar 2008 in microsoft.public.windows.terminal_services:

>

> > I just looked on my server. The temp CALs are device CALs and

> > the actual CALs are per user. Is this going to cause any

> > problems, and if so, can I change the CALs to device CALs?

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> "Lanwench [MVP - Exchange]"

> >> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com>

> >> wrote on 19 mar 2008 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > jeffk <jeffk@discussions.microsoft.com> wrote:

> >> >> I installed a terminal server (member server) on a SBS

> >> >> network and am now getting the following pop up on the

> >> >> desktops: "Your terminal services temporary client license

> >> >> will expire in 7 days. Please contact your system

> >> >> administrator to get a permanent license." Is this anything

> >> >> that I need to worry about? Will the permanent licenses

> >> >> start working without having to do anything? If there is

> >> >> something I need to do, what is it? Help!

> >> >

> >> > Did you buy TS CALs and install the Terminal Service

> >> > Licensing bits on your SBS box? (that's where I'd put them).

> >> > Then you need to launch & activate them/it. Then you point

> >> > the TS box at the TS licensing server.

> >>

> >> And if you already installed permanent TS CALs on an LS (which

> >> your post seems to suggest), does the licensing mode of your TS

> >> match the type of licenses that you installed, i.e. Per User /

> >> Per Device?

> >>

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

> >> TS troubleshooting: http://ts.veranoest.net

> >> ___ please respond in newsgroup, NOT by private email ___

> >>

>

[Guest Vera Noest [MVP]]

Re: Temporary client license

 

Yes, it can make a big difference. Be sure to choose the licensing

mode which is cheapest for you.

 

Per Device means: you need a TS CAL for every connecting device

(not concurrent)

Per User means: ou need a TS CAL for every connecting user (not

concurrent)

 

So if you have more devices than users (when most users connect

from multiple devices, like their office pc, their home pc and a

laptop), then Per User is cheaper.

If you have more users than devices (when people are working in

shifts and sharing clients, or in a classroom), then Per Device is

cheapest.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

=?Utf-8?B?amVmZms=?= <jeffk@discussions.microsoft.com> wrote on 20

mar 2008:

> Will changing the TS to user CALs make a difference? I've

> changed it, but I don't know what the ramifications will be.

>

> "Vera Noest [MVP]" wrote:

>

>> Yes, that's a problem.

>> If you want Per Device TS CALs instead, you will have to call

>> the Clearinghouse to get a new license pack. Note that such a

>> change is only allowed if you have valid Software Assurance on

>> your existing licenses.

>>

>> The other solution is to change the licensing mode of your

>> Terminal Server to Per User licensing. This is done in Terminal

>> Services Configuration - Server settings.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?amVmZms=?= <jeffk@discussions.microsoft.com> wrote on

>> 19 mar 2008 in microsoft.public.windows.terminal_services:

>>

>> > I just looked on my server. The temp CALs are device CALs and

>> > the actual CALs are per user. Is this going to cause any

>> > problems, and if so, can I change the CALs to device CALs?

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> "Lanwench [MVP - Exchange]"

>> >> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com>

>> >> wrote on 19 mar 2008 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > jeffk <jeffk@discussions.microsoft.com> wrote:

>> >> >> I installed a terminal server (member server) on a SBS

>> >> >> network and am now getting the following pop up on the

>> >> >> desktops: "Your terminal services temporary client

>> >> >> license will expire in 7 days. Please contact your system

>> >> >> administrator to get a permanent license." Is this

>> >> >> anything that I need to worry about? Will the permanent

>> >> >> licenses start working without having to do anything? If

>> >> >> there is something I need to do, what is it? Help!

>> >> >

>> >> > Did you buy TS CALs and install the Terminal Service

>> >> > Licensing bits on your SBS box? (that's where I'd put

>> >> > them). Then you need to launch & activate them/it. Then

>> >> > you point the TS box at the TS licensing server.

>> >>

>> >> And if you already installed permanent TS CALs on an LS

>> >> (which your post seems to suggest), does the licensing mode

>> >> of your TS match the type of licenses that you installed,

>> >> i.e. Per User / Per Device?

>> >>

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

>> >> TS troubleshooting: http://ts.veranoest.net

>> >> ___ please respond in newsgroup, NOT by private email ___

[Guest DEI]

Re: Temporary client license

 

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)

[Guest Vera Noest [MVP]]

Re: Temporary client license

 

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@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)

[Guest DEI]

Re: Temporary client license

 

WOW thanks for the link! I just found killer site to add to my arsenal!

hehe

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A6873024DCE5veranoesthemutforsse@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@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)

[Guest DEI]

Re: Temporary client license

 

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@remove-this.hem.utfors.se> wrote in message

news:Xns9A6873024DCE5veranoesthemutforsse@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@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)

[Guest Vera Noest [MVP]]

Re: Temporary client license

 

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@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@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9A6873024DCE5veranoesthemutforsse@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@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)

[Guest DEI]

Re: Temporary client license

 

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!

[Guest Vera Noest [MVP]]

Re: Temporary client license

 

comments inline.

 

"DEI" <dei@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 ___

[Guest Piet van Dongen]

Re: Temporary client license

 

Vera means that you don't have to divide the TSCAL's over two servers to

make the TS licencing redundant.

 

When an user does a login on a terminal server:

 

- Terminal Server checks if there is a TS license server configured (with

e.g. HKLM regkey or GPO)

- If it does => it checks if there is a free license available

- If it does => it generates a random number between 56 and 89 (this is

your leasetime of the license like with DHCP)

 

Maybe the TS (per device/user) changes by an action on the terminal server:

See below KB-article from M$...

 

 

--

Regards,

 

_____________________________

Piet van Dongen

 

MCSA, MCSE, MCTS, MCDBA, MCP

CCA, CCEA, CCSP

RPFCP, RWCP, RCP

_____________________________

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> schreef in bericht

news:Xns9A697F0A3B21Cveranoesthemutforsse@207.46.248.16...

> comments inline.

>

> "DEI" <dei@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 ___