license problem

[Guest Patti]

hello,

i need help i know very little about terminal Services can someone please

help on what this error means

"The terminal server client Computername has been disconnected because its

license could not be renewed. The license server Name was contacted to get

Windows Server 2003 - Terminal Server Per Device CAL Token. license for this

client.“

thanks for your help in advance

[Guest Vera Noest [MVP]]

Re: license problem

 

To be able to connect to a Terminal Server, each client or user needs

a TS CAL (Terminal Services Client Access License). You have to

purchase them, install a Terminal Services Licensing Server on one of

your servers, and install the TS CALs on the TS LS.

 

_________________________________________________________

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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 26

nov 2007 in microsoft.public.windows.terminal_services:

> hello,

> i need help i know very little about terminal Services can

> someone please help on what this error means

> "The terminal server client Computername has been disconnected

> because its license could not be renewed. The license server

> Name was contacted to get Windows Server 2003 - Terminal Server

> Per Device CAL Token. license for this client.“

> thanks for your help in advance

[Guest Patti]

Re: license problem

 

the server is all ready setup with TS CAL. do you think there is not enough

licenses?

 

thanks for your help

Patti

 

"Vera Noest [MVP]" wrote:

> To be able to connect to a Terminal Server, each client or user needs

> a TS CAL (Terminal Services Client Access License). You have to

> purchase them, install a Terminal Services Licensing Server on one of

> your servers, and install the TS CALs on the TS LS.

>

> _________________________________________________________

> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 26

> nov 2007 in microsoft.public.windows.terminal_services:

>

> > hello,

> > i need help i know very little about terminal Services can

> > someone please help on what this error means

> > "The terminal server client Computername has been disconnected

> > because its license could not be renewed. The license server

> > Name was contacted to get Windows Server 2003 - Terminal Server

> > Per Device CAL Token. license for this client.“

> > thanks for your help in advance

>

[Guest Vera Noest [MVP]]

Re: license problem

 

Only you can tell us :-)

Start the TS Licensing Manager and check the numbers under

"Issued", "Total" and "Available".

_________________________________________________________

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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 27

nov 2007 in microsoft.public.windows.terminal_services:

> the server is all ready setup with TS CAL. do you think there is

> not enough licenses?

>

> thanks for your help

> Patti

>

> "Vera Noest [MVP]" wrote:

>

>> To be able to connect to a Terminal Server, each client or user

>> needs a TS CAL (Terminal Services Client Access License). You

>> have to purchase them, install a Terminal Services Licensing

>> Server on one of your servers, and install the TS CALs on the

>> TS LS.

>>

>> _________________________________________________________

>> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on

>> 26 nov 2007 in microsoft.public.windows.terminal_services:

>>

>> > hello,

>> > i need help i know very little about terminal Services can

>> > someone please help on what this error means

>> > "The terminal server client Computername has been

>> > disconnected because its license could not be renewed. The

>> > license server Name was contacted to get Windows Server 2003

>> > - Terminal Server Per Device CAL Token. license for this

>> > client.“ thanks for your help in advance

[Guest Patti]

Re: license problem

 

ok this is what i have

windows server 2003 Terminal server per Device Cal Token Volune License

Total 10 Available 10 Issued 0

winodows server 2003 Terminal server per user Cal Token Volume License

Total 10 Available 10 Issued Not Applicable

also I thought Temp License where given out if there were not enough

licenses, but again i really do not know enough about all of this

again thanks for your help!

 

"Vera Noest [MVP]" wrote:

> Only you can tell us :-)

> Start the TS Licensing Manager and check the numbers under

> "Issued", "Total" and "Available".

> _________________________________________________________

> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 27

> nov 2007 in microsoft.public.windows.terminal_services:

>

> > the server is all ready setup with TS CAL. do you think there is

> > not enough licenses?

> >

> > thanks for your help

> > Patti

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> To be able to connect to a Terminal Server, each client or user

> >> needs a TS CAL (Terminal Services Client Access License). You

> >> have to purchase them, install a Terminal Services Licensing

> >> Server on one of your servers, and install the TS CALs on the

> >> TS LS.

> >>

> >> _________________________________________________________

> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on

> >> 26 nov 2007 in microsoft.public.windows.terminal_services:

> >>

> >> > hello,

> >> > i need help i know very little about terminal Services can

> >> > someone please help on what this error means

> >> > "The terminal server client Computername has been

> >> > disconnected because its license could not be renewed. The

> >> > license server Name was contacted to get Windows Server 2003

> >> > - Terminal Server Per Device CAL Token. license for this

> >> > client.“ thanks for your help in advance

>

[Guest Vera Noest [MVP]]

Re: license problem

 

So you have 10 Per Device TS CALs and 10 Per User TS CALs.

That's usually not a good idea, since a single terminal server can

only use one type of licenses.

The fact that you don't see any temporary licenses issued probably

means that your Terminal Server is configured to use the Per user

licensing mode. Check this in Terminal Services Configuration -

Server settings.

Per User licenses are currently unmanaged, that's why they are

listed as "Not Applicable" under the "Issued" count. That means

that you will have to keep track of the number of connecting users

by hand.

You should also call the Clearinghouse and switch your Per Device

licenses into Per User licenses (assuming that you want all

Terminal Servers to use Per user licensing). This is allowed when

you renew your Software Assurance Agreement.

 

Now to solve your problem: I assume that it occurred only on a

single client? If so, delete the locally stored license from the

client. Here's how that is done:

 

187614 - Removing Terminal Server Licenses from an RDP Client

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

_________________________________________________________

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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 28

nov 2007 in microsoft.public.windows.terminal_services:

> ok this is what i have

> windows server 2003 Terminal server per Device Cal Token Volune

> License Total 10 Available 10 Issued 0

> winodows server 2003 Terminal server per user Cal Token Volume

> License Total 10 Available 10 Issued Not Applicable

> also I thought Temp License where given out if there were not

> enough licenses, but again i really do not know enough about all

> of this again thanks for your help!

>

> "Vera Noest [MVP]" wrote:

>

>> Only you can tell us :-)

>> Start the TS Licensing Manager and check the numbers under

>> "Issued", "Total" and "Available".

>> _________________________________________________________

>> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on

>> 27 nov 2007 in microsoft.public.windows.terminal_services:

>>

>> > the server is all ready setup with TS CAL. do you think there

>> > is not enough licenses?

>> >

>> > thanks for your help

>> > Patti

>> >

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

>> >

>> >> To be able to connect to a Terminal Server, each client or

>> >> user needs a TS CAL (Terminal Services Client Access

>> >> License). You have to purchase them, install a Terminal

>> >> Services Licensing Server on one of your servers, and

>> >> install the TS CALs on the TS LS.

>> >>

>> >> _________________________________________________________

>> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote

>> >> on 26 nov 2007 in

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

>> >>

>> >> > hello,

>> >> > i need help i know very little about terminal Services can

>> >> > someone please help on what this error means

>> >> > "The terminal server client Computername has been

>> >> > disconnected because its license could not be renewed. The

>> >> > license server Name was contacted to get Windows Server

>> >> > 2003 - Terminal Server Per Device CAL Token. license for

>> >> > this client.“ thanks for your help in

>> >> > advance

[Guest Patti]

Re: license problem

 

thank you so much! i have one more, i looked at Terminal Server is configured

has Remoter Desktop for Administration. is the same has pre user mode?

 

Patti

 

"Vera Noest [MVP]" wrote:

> So you have 10 Per Device TS CALs and 10 Per User TS CALs.

> That's usually not a good idea, since a single terminal server can

> only use one type of licenses.

> The fact that you don't see any temporary licenses issued probably

> means that your Terminal Server is configured to use the Per user

> licensing mode. Check this in Terminal Services Configuration -

> Server settings.

> Per User licenses are currently unmanaged, that's why they are

> listed as "Not Applicable" under the "Issued" count. That means

> that you will have to keep track of the number of connecting users

> by hand.

> You should also call the Clearinghouse and switch your Per Device

> licenses into Per User licenses (assuming that you want all

> Terminal Servers to use Per user licensing). This is allowed when

> you renew your Software Assurance Agreement.

>

> Now to solve your problem: I assume that it occurred only on a

> single client? If so, delete the locally stored license from the

> client. Here's how that is done:

>

> 187614 - Removing Terminal Server Licenses from an RDP Client

> http://support.microsoft.com/?kbid=187614

> _________________________________________________________

> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 28

> nov 2007 in microsoft.public.windows.terminal_services:

>

> > ok this is what i have

> > windows server 2003 Terminal server per Device Cal Token Volune

> > License Total 10 Available 10 Issued 0

> > winodows server 2003 Terminal server per user Cal Token Volume

> > License Total 10 Available 10 Issued Not Applicable

> > also I thought Temp License where given out if there were not

> > enough licenses, but again i really do not know enough about all

> > of this again thanks for your help!

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Only you can tell us :-)

> >> Start the TS Licensing Manager and check the numbers under

> >> "Issued", "Total" and "Available".

> >> _________________________________________________________

> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on

> >> 27 nov 2007 in microsoft.public.windows.terminal_services:

> >>

> >> > the server is all ready setup with TS CAL. do you think there

> >> > is not enough licenses?

> >> >

> >> > thanks for your help

> >> > Patti

> >> >

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

> >> >

> >> >> To be able to connect to a Terminal Server, each client or

> >> >> user needs a TS CAL (Terminal Services Client Access

> >> >> License). You have to purchase them, install a Terminal

> >> >> Services Licensing Server on one of your servers, and

> >> >> install the TS CALs on the TS LS.

> >> >>

> >> >> _________________________________________________________

> >> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote

> >> >> on 26 nov 2007 in

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

> >> >>

> >> >> > hello,

> >> >> > i need help i know very little about terminal Services can

> >> >> > someone please help on what this error means

> >> >> > "The terminal server client Computername has been

> >> >> > disconnected because its license could not be renewed. The

> >> >> > license server Name was contacted to get Windows Server

> >> >> > 2003 - Terminal Server Per Device CAL Token. license for

> >> >> > this client.“ thanks for your help in

> >> >> > advance

>

[Guest Patti]

Re: license problem

 

Hi,

ok i hope this will be the last time i bug you. we have aquired a company

this is currently being migrated into my company domain. they all ready have

a windows 2000 server with terminal server on it. about 40 licenses. is there

anyway i can migrate there 40 license over to my comapany terminal server?

 

again you have been a great help

 

"Vera Noest [MVP]" wrote:

> So you have 10 Per Device TS CALs and 10 Per User TS CALs.

> That's usually not a good idea, since a single terminal server can

> only use one type of licenses.

> The fact that you don't see any temporary licenses issued probably

> means that your Terminal Server is configured to use the Per user

> licensing mode. Check this in Terminal Services Configuration -

> Server settings.

> Per User licenses are currently unmanaged, that's why they are

> listed as "Not Applicable" under the "Issued" count. That means

> that you will have to keep track of the number of connecting users

> by hand.

> You should also call the Clearinghouse and switch your Per Device

> licenses into Per User licenses (assuming that you want all

> Terminal Servers to use Per user licensing). This is allowed when

> you renew your Software Assurance Agreement.

>

> Now to solve your problem: I assume that it occurred only on a

> single client? If so, delete the locally stored license from the

> client. Here's how that is done:

>

> 187614 - Removing Terminal Server Licenses from an RDP Client

> http://support.microsoft.com/?kbid=187614

> _________________________________________________________

> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 28

> nov 2007 in microsoft.public.windows.terminal_services:

>

> > ok this is what i have

> > windows server 2003 Terminal server per Device Cal Token Volune

> > License Total 10 Available 10 Issued 0

> > winodows server 2003 Terminal server per user Cal Token Volume

> > License Total 10 Available 10 Issued Not Applicable

> > also I thought Temp License where given out if there were not

> > enough licenses, but again i really do not know enough about all

> > of this again thanks for your help!

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Only you can tell us :-)

> >> Start the TS Licensing Manager and check the numbers under

> >> "Issued", "Total" and "Available".

> >> _________________________________________________________

> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on

> >> 27 nov 2007 in microsoft.public.windows.terminal_services:

> >>

> >> > the server is all ready setup with TS CAL. do you think there

> >> > is not enough licenses?

> >> >

> >> > thanks for your help

> >> > Patti

> >> >

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

> >> >

> >> >> To be able to connect to a Terminal Server, each client or

> >> >> user needs a TS CAL (Terminal Services Client Access

> >> >> License). You have to purchase them, install a Terminal

> >> >> Services Licensing Server on one of your servers, and

> >> >> install the TS CALs on the TS LS.

> >> >>

> >> >> _________________________________________________________

> >> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote

> >> >> on 26 nov 2007 in

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

> >> >>

> >> >> > hello,

> >> >> > i need help i know very little about terminal Services can

> >> >> > someone please help on what this error means

> >> >> > "The terminal server client Computername has been

> >> >> > disconnected because its license could not be renewed. The

> >> >> > license server Name was contacted to get Windows Server

> >> >> > 2003 - Terminal Server Per Device CAL Token. license for

> >> >> > this client.“ thanks for your help in

> >> >> > advance

>

[Guest Vera Noest [MVP]]

Re: license problem

 

No, Remote Desktop for Administration is the mode in which you can

connect with a maximum of 2 sessions, by default only for

Administrators. This is the default mode on any 2003 server.

If your server is in this mode, it means that it is not a Terminal

Server at all, Terminal Services is not installed on this server.

Then you don't need any TS CALs either, at least not to connect to

this server. But maybe there's another server on the network which

is a real Terminal Server?

 

_________________________________________________________

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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 29

nov 2007 in microsoft.public.windows.terminal_services:

> thank you so much! i have one more, i looked at Terminal Server

> is configured has Remoter Desktop for Administration. is the

> same has pre user mode?

>

> Patti

>

> "Vera Noest [MVP]" wrote:

>

>> So you have 10 Per Device TS CALs and 10 Per User TS CALs.

>> That's usually not a good idea, since a single terminal server

>> can only use one type of licenses.

>> The fact that you don't see any temporary licenses issued

>> probably means that your Terminal Server is configured to use

>> the Per user licensing mode. Check this in Terminal Services

>> Configuration - Server settings.

>> Per User licenses are currently unmanaged, that's why they are

>> listed as "Not Applicable" under the "Issued" count. That means

>> that you will have to keep track of the number of connecting

>> users by hand.

>> You should also call the Clearinghouse and switch your Per

>> Device licenses into Per User licenses (assuming that you want

>> all Terminal Servers to use Per user licensing). This is

>> allowed when you renew your Software Assurance Agreement.

>>

>> Now to solve your problem: I assume that it occurred only on a

>> single client? If so, delete the locally stored license from

>> the client. Here's how that is done:

>>

>> 187614 - Removing Terminal Server Licenses from an RDP Client

>> http://support.microsoft.com/?kbid=187614

>> _________________________________________________________

>> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on

>> 28 nov 2007 in microsoft.public.windows.terminal_services:

>>

>> > ok this is what i have

>> > windows server 2003 Terminal server per Device Cal Token

>> > Volune License Total 10 Available 10 Issued 0

>> > winodows server 2003 Terminal server per user Cal Token

>> > Volume License Total 10 Available 10 Issued Not Applicable

>> > also I thought Temp License where given out if there were not

>> > enough licenses, but again i really do not know enough about

>> > all of this again thanks for your help!

>> >

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

>> >

>> >> Only you can tell us :-)

>> >> Start the TS Licensing Manager and check the numbers under

>> >> "Issued", "Total" and "Available".

>> >> _________________________________________________________

>> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote

>> >> on 27 nov 2007 in

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

>> >>

>> >> > the server is all ready setup with TS CAL. do you think

>> >> > there is not enough licenses?

>> >> >

>> >> > thanks for your help

>> >> > Patti

>> >> >

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

>> >> >

>> >> >> To be able to connect to a Terminal Server, each client

>> >> >> or user needs a TS CAL (Terminal Services Client Access

>> >> >> License). You have to purchase them, install a Terminal

>> >> >> Services Licensing Server on one of your servers, and

>> >> >> install the TS CALs on the TS LS.

>> >> >>

>> >> >> _________________________________________________________

>> >> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com>

>> >> >> wrote on 26 nov 2007 in

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

>> >> >>

>> >> >> > hello,

>> >> >> > i need help i know very little about terminal Services

>> >> >> > can someone please help on what this error means

>> >> >> > "The terminal server client Computername has been

>> >> >> > disconnected because its license could not be renewed.

>> >> >> > The license server Name was contacted to get Windows

>> >> >> > Server 2003 - Terminal Server Per Device CAL Token.

>> >> >> > license for this

>> >> >> > client.“ thanks for

>> >> >> > your help in advance

[Guest Vera Noest [MVP]]

Re: license problem

 

According to your previous post, you don't *have* a Terminal

Server.

At this stage, I would recommend you to hire a consultant to

investigate the current situation and help you to design the

network according to your requirements. There's a lot that can be

misconfigured with TS, and it's often very difficult to repair

afterwards, without starting all over.

_________________________________________________________

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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on 29

nov 2007 in microsoft.public.windows.terminal_services:

> Hi,

> ok i hope this will be the last time i bug you. we have aquired

> a company this is currently being migrated into my company

> domain. they all ready have a windows 2000 server with terminal

> server on it. about 40 licenses. is there anyway i can migrate

> there 40 license over to my comapany terminal server?

>

> again you have been a great help

>

> "Vera Noest [MVP]" wrote:

>

>> So you have 10 Per Device TS CALs and 10 Per User TS CALs.

>> That's usually not a good idea, since a single terminal server

>> can only use one type of licenses.

>> The fact that you don't see any temporary licenses issued

>> probably means that your Terminal Server is configured to use

>> the Per user licensing mode. Check this in Terminal Services

>> Configuration - Server settings.

>> Per User licenses are currently unmanaged, that's why they are

>> listed as "Not Applicable" under the "Issued" count. That means

>> that you will have to keep track of the number of connecting

>> users by hand.

>> You should also call the Clearinghouse and switch your Per

>> Device licenses into Per User licenses (assuming that you want

>> all Terminal Servers to use Per user licensing). This is

>> allowed when you renew your Software Assurance Agreement.

>>

>> Now to solve your problem: I assume that it occurred only on a

>> single client? If so, delete the locally stored license from

>> the client. Here's how that is done:

>>

>> 187614 - Removing Terminal Server Licenses from an RDP Client

>> http://support.microsoft.com/?kbid=187614

>> _________________________________________________________

>> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote on

>> 28 nov 2007 in microsoft.public.windows.terminal_services:

>>

>> > ok this is what i have

>> > windows server 2003 Terminal server per Device Cal Token

>> > Volune License Total 10 Available 10 Issued 0

>> > winodows server 2003 Terminal server per user Cal Token

>> > Volume License Total 10 Available 10 Issued Not Applicable

>> > also I thought Temp License where given out if there were not

>> > enough licenses, but again i really do not know enough about

>> > all of this again thanks for your help!

>> >

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

>> >

>> >> Only you can tell us :-)

>> >> Start the TS Licensing Manager and check the numbers under

>> >> "Issued", "Total" and "Available".

>> >> _________________________________________________________

>> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com> wrote

>> >> on 27 nov 2007 in

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

>> >>

>> >> > the server is all ready setup with TS CAL. do you think

>> >> > there is not enough licenses?

>> >> >

>> >> > thanks for your help

>> >> > Patti

>> >> >

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

>> >> >

>> >> >> To be able to connect to a Terminal Server, each client

>> >> >> or user needs a TS CAL (Terminal Services Client Access

>> >> >> License). You have to purchase them, install a Terminal

>> >> >> Services Licensing Server on one of your servers, and

>> >> >> install the TS CALs on the TS LS.

>> >> >>

>> >> >> _________________________________________________________

>> >> >> 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?UGF0dGk=?= <Patti@discussions.microsoft.com>

>> >> >> wrote on 26 nov 2007 in

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

>> >> >>

>> >> >> > hello,

>> >> >> > i need help i know very little about terminal Services

>> >> >> > can someone please help on what this error means

>> >> >> > "The terminal server client Computername has been

>> >> >> > disconnected because its license could not be renewed.

>> >> >> > The license server Name was contacted to get Windows

>> >> >> > Server 2003 - Terminal Server Per Device CAL Token.

>> >> >> > license for this

>> >> >> > client.“ thanks for

>> >> >> > your help in advance