Licensing Issue/Questions

[Guest compsosinc@gmail.com]

We have a Windows 2003 Server that is a Terminal Server and the

LIcensing Server is also running on this system. We purchased 10 TS

CALs - Per Device. We had 10 XP clients connecting via RDP, then we

added another client. We forgot about purchasing another CAL, so the

temporary license for the "11th" XP client has expired and it cannot

connect. In figuring out what had happened we came across some

questions in the TS Licensing Manager:

 

1) In TS Lic.Mrg. for the "Windows Server 2003 - Terminal Server Per

Device" we see columns for "Issued To", "Issued On", Expires On,

Quantity. There are (10) Client PCs listed, most with issue dates in

Feb 2008. However, the "Expires On" dates are in July 2008. Why would

these show they are going to expire if they are permanent?

 

2) Do we have to purchase new CALs in block of 5, or can we just

purchase (1)?

 

3) Once we install the new CAL license, will the "11th" client pick it

up automatically? Right now we are getting the "License Protocol"

error (KB187614) after deleting the MSLicensing key from the registry

before we new we were short a license because the temporary had

expired.

 

4) A vendor connected to the TS Server and used one of the (2)

Temporary licenses and it shows it will expire in Sept 2008. How do we

make this temporary license available again?

 

5) How do we make the temporary license available again that the

"11th" client was using?

 

Thanks!

[Guest Vera Noest [MVP]]

Re: Licensing Issue/Questions

 

comments inline

 

compsosinc@gmail.com wrote on 12 jun 2008 in

microsoft.public.windows.terminal_services:

> We have a Windows 2003 Server that is a Terminal Server and the

> LIcensing Server is also running on this system. We purchased 10

> TS CALs - Per Device. We had 10 XP clients connecting via RDP,

> then we added another client. We forgot about purchasing another

> CAL, so the temporary license for the "11th" XP client has

> expired and it cannot connect. In figuring out what had happened

> we came across some questions in the TS Licensing Manager:

>

> 1) In TS Lic.Mrg. for the "Windows Server 2003 - Terminal Server

> Per Device" we see columns for "Issued To", "Issued On", Expires

> On, Quantity. There are (10) Client PCs listed, most with issue

> dates in Feb 2008. However, the "Expires On" dates are in July

> 2008. Why would these show they are going to expire if they are

> permanent?

 

This is a feature, not a bug :-)

All licenses expire, 52-89 days after issueing. This feature was

implemented in W2K SP3, to avoid that a license was permanently

lost when a client was discarded alltogether or reinstalled from

scratch. Starting 7 days prior to the expiration date, the client

will automatically renew it's lease of the license. This process is

completely transparent to the user or the Administrator.

If the client doen't connect to the TS anymore (because the client

doesn't exist anymore), the expirated license will be returned to

the available licenses on the TS Licensing Server and become

available for a new client.

> 2) Do we have to purchase new CALs in block of 5, or can we just

> purchase (1)?

 

Don't know, that depends on your vendor.

> 3) Once we install the new CAL license, will the "11th" client

> pick it up automatically? Right now we are getting the "License

> Protocol" error (KB187614) after deleting the MSLicensing key

> from the registry before we new we were short a license because

> the temporary had expired.

 

Yes, the client should pick up the new license automatically.

> 4) A vendor connected to the TS Server and used one of the (2)

> Temporary licenses and it shows it will expire in Sept 2008. How

> do we make this temporary license available again?

 

You can't, and you needn't. The number of temporary licenses is

unlimited. But each client can only receive a temporary license

once.

Note that if you occasionaly have vendors connecting to your TS,

chances are that they pick up a real license, if one is available.

That's no big deal in the long run, because of the automatic

expiration of licenses. But in the short run, it might be a good

idea to have 1 or 2 extra licenses available for such clients.

> 5) How do we make the temporary license available again that the

> "11th" client was using?

 

Same as above, under point 4.

> Thanks!

 

You're welcome!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

[Guest compsosinc@gmail.com]

Re: Licensing Issue/Questions

 

On Jun 12, 3:49 pm, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> comments inline

>

> compsos...@gmail.com wrote on 12 jun 2008 in

> microsoft.public.windows.terminal_services:

>

> > We have a Windows 2003 Server that is a Terminal Server and the

> > LIcensing Server is also running on this system. We purchased 10

> > TS CALs - Per Device. We had 10 XP clients connecting via RDP,

> > then we added another client. We forgot about purchasing another

> > CAL, so the temporary license for the "11th" XP client has

> > expired and it cannot connect. In figuring out what had happened

> > we came across some questions in the TS Licensing Manager:

>

> > 1) In TS Lic.Mrg. for the "Windows Server 2003 - Terminal Server

> > Per Device" we see columns for "Issued To", "Issued On", Expires

> > On, Quantity.  There are (10) Client PCs listed, most with issue

> > dates in Feb 2008. However, the "Expires On" dates are in July

> > 2008. Why would these show they are going to expire if they are

> > permanent?

>

> This is a feature, not a bug :-)

> All licenses expire, 52-89 days after issueing. This feature was

> implemented in W2K SP3, to avoid that a license was permanently

> lost when a client was discarded alltogether or reinstalled from

> scratch. Starting 7 days prior to the expiration date, the client

> will automatically renew it's lease of the license. This process is

> completely transparent to the user or the Administrator.

> If the client doen't connect to the TS anymore (because the client

> doesn't exist anymore), the expirated license will be returned to

> the available licenses on the TS Licensing Server and become

> available for a new client.

>

> > 2) Do we have to purchase new CALs in block of 5, or can we just

> > purchase (1)?

>

> Don't know, that depends on your vendor.

>

> > 3) Once we install the new CAL license, will the "11th" client

> > pick it up automatically? Right now we are getting the "License

> > Protocol" error (KB187614) after deleting the MSLicensing key

> > from the registry before we new we were short a license because

> > the temporary had expired.

>

> Yes, the client should pick up the new license automatically.

>

> > 4) A vendor connected to the TS Server and used one of the (2)

> > Temporary licenses and it shows it will expire in Sept 2008. How

> > do we make this temporary license available again?

>

> You can't, and you needn't. The number of temporary licenses is

> unlimited. But each client can only receive a temporary license

> once.

> Note that if you occasionaly have vendors connecting to your TS,

> chances are that they pick up a real license, if one is available.

> That's no big deal in the long run, because of the automatic

> expiration of licenses. But in the short run, it might be a good

> idea to have 1 or 2 extra licenses available for such clients.

>

> > 5) How do we make the temporary license available again that the

> > "11th" client was using?

>

> Same as above, under point 4.

>

> > Thanks!

>

> You're welcome!

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

 

Super information -thanks so much!