Licenses Expiration Explanation Please

[Guest rushjk@gmail.com]

I have 700 Windows Server 2003 Terminal Server Per Device CAL Tokens.

Currently, all 700 appear to be issued in Terminal Server Licensing,

and none are available. However, when I look through the lists of

tokens, many (almost 100) appear to be expired already. Why would

these not become available in the pool again? Am I not really out of

licenses? I bought 50 recently and added them to the pool when I

thought that they were out. Are they not really out? Do I need to keep

throwing money at MS? What am I to do?

Thanks in advance for any help.

[Guest Vera Noest [MVP]]

Re: Licenses Expiration Explanation Please

 

Check if this helps:

 

Expired TS CALs are not returned to the pool of available licenses

http://ts.veranoest.net/ts_faq_licensing.htm#release_expired_TSCALs

 

If it doesn't, can you please repost with the exact numbers that you

see in the TS Licensing Manager under "Total", "Available" and

"Issued", for both your purchased TS CALs and temporary TS CALs?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

rushjk@gmail.com wrote on 26 jan 2008 in

microsoft.public.windows.terminal_services:

> I have 700 Windows Server 2003 Terminal Server Per Device CAL

> Tokens. Currently, all 700 appear to be issued in Terminal

> Server Licensing, and none are available. However, when I look

> through the lists of tokens, many (almost 100) appear to be

> expired already. Why would these not become available in the

> pool again? Am I not really out of licenses? I bought 50

> recently and added them to the pool when I thought that they

> were out. Are they not really out? Do I need to keep throwing

> money at MS? What am I to do? Thanks in advance for any help.

[Guest rushjk@gmail.com]

Re: Licenses Expiration Explanation Please

 

On Jan 26, 8:34 am, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> Check if this helps:

>

> Expired TS CALs are not returned to the pool of available licenseshttp://ts.veranoest.net/ts_faq_licensing.htm#release_expired_TSCALs

>

> If it doesn't, can you please repost with the exact numbers that you

> see in the TS Licensing Manager under "Total", "Available" and

> "Issued", for both your purchased TS CALs and temporary TS CALs?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> rus...@gmail.com wrote on 26 jan 2008 in

> microsoft.public.windows.terminal_services:

>

> > I have 700 Windows Server 2003 Terminal Server Per Device CAL

> > Tokens. Currently, all 700 appear to be issued in Terminal

> > Server Licensing, and none are available. However, when I look

> > through the lists of tokens, many (almost 100) appear to be

> > expired already. Why would these not become available in the

> > pool again? Am I not really out of licenses? I bought 50

> > recently and added them to the pool when I thought that they

> > were out. Are they not really out? Do I need to keep throwing

> > money at MS? What am I to do? Thanks in advance for any help.

 

This fix does appear to solve the problem. Volume Shadow Copy service

is set as Manual startup and was not running, however. Why would that

still cause problems with the Licensing thread? I am now showing 117

available tokens. Thank you for your help.

[Guest Vera Noest [MVP]]

Re: Licenses Expiration Explanation Please

 

rushjk@gmail.com wrote on 28 jan 2008 in

microsoft.public.windows.terminal_services:

> On Jan 26, 8:34 am, "Vera Noest [MVP]" <vera.no...@remove-

> this.hem.utfors.se> wrote:

>> Check if this helps:

>>

>> Expired TS CALs are not returned to the pool of available

>> licenseshttp://ts.veranoest.net/ts_faq_licensing.htm#release_exp

>> ired_TSCALs

>>

>> If it doesn't, can you please repost with the exact numbers

>> that you see in the TS Licensing Manager under "Total",

>> "Available" and "Issued", for both your purchased TS CALs and

>> temporary TS CALs?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> rus...@gmail.com wrote on 26 jan 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > I have 700 Windows Server 2003 Terminal Server Per Device CAL

>> > Tokens. Currently, all 700 appear to be issued in Terminal

>> > Server Licensing, and none are available. However, when I

>> > look through the lists of tokens, many (almost 100) appear to

>> > be expired already. Why would these not become available in

>> > the pool again? Am I not really out of licenses? I bought 50

>> > recently and added them to the pool when I thought that they

>> > were out. Are they not really out? Do I need to keep throwing

>> > money at MS? What am I to do? Thanks in advance for any help.

>

> This fix does appear to solve the problem. Volume Shadow Copy

> service is set as Manual startup and was not running, however.

> Why would that still cause problems with the Licensing thread? I

> am now showing 117 available tokens. Thank you for your help.

 

My fault! I noticed that I referenced the wrong KB article in my

FAQ. Read this one, it explains why, how and under which

circumstances the problem occurs and how you can avoid it in the

future:

 

926935 - A Terminal Services client may be unable to connect to a

Terminal Services license server that is installed on a Windows

Server 2003-based computer

http://support.microsoft.com/?kbid=926935

 

Thanks for your feedback!

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___