Jump to content

Terminal Server Licensing Server issue


Recommended Posts

Posted

Hi,

 

All of a sudden i get the eventid error 22 on my Windows 2000 Licensing

Server.

When I check with the administrative tool everything seems OK.

How can I resolve this problem

"The Terminal Services Licensing server 'servername' has no license pack

registered for product 'Windows 2000 Terminal Services Client Access

License'. Use Terminal Services Licensing administrative tool to register

the licenses pack. "

 

When I check with the administrative tool everything seems OK.

I already reinstalled the Terminal Server Licensing Server, that didn't

change a thing.

How can I resolve this problem.

 

Thanks

Guest Vera Noest [MVP]
Posted

Re: Terminal Server Licensing Server issue

 

Can you specify "everything seems OK"?

When you start the TS Licensing Manager on your TS Licensing

Server, which licenses are recorded there?

Did you purchase and install any Licensing Packs?

Do you have down-level clients which need a purchased TS CAL?

Note that all clients except W2K Pro, XP Pro and Vista need one.

Are there expired temporary licenses?

Can clients still connect?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

 

"Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

> Hi,

>

> All of a sudden i get the eventid error 22 on my Windows 2000

> Licensing Server.

> When I check with the administrative tool everything seems OK.

> How can I resolve this problem

> "The Terminal Services Licensing server 'servername' has no

> license pack registered for product 'Windows 2000 Terminal

> Services Client Access License'. Use Terminal Services Licensing

> administrative tool to register the licenses pack. "

>

> When I check with the administrative tool everything seems OK.

> I already reinstalled the Terminal Server Licensing Server, that

> didn't change a thing.

> How can I resolve this problem.

>

> Thanks

Posted

Re: Terminal Server Licensing Server issue

 

"everything seems ok" i mean

the server is activated, license for Windows 2000 TSCAL is there with the

correct number of CAL's.

We are connecting from linux based ThinClients.

After reinstalling the Terminal Server Licensing server and activating and

adding the W2K TSCAL there aren't any expired licenses.

Most clients can connect, few can't

This LS was working since 2004, and all of a sudden it doesn't.

No fixes have been installed recently.

 

thanks

Kris

 

 

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

news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

> Can you specify "everything seems OK"?

> When you start the TS Licensing Manager on your TS Licensing

> Server, which licenses are recorded there?

> Did you purchase and install any Licensing Packs?

> Do you have down-level clients which need a purchased TS CAL?

> Note that all clients except W2K Pro, XP Pro and Vista need one.

> Are there expired temporary licenses?

> Can clients still connect?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>

>> Hi,

>>

>> All of a sudden i get the eventid error 22 on my Windows 2000

>> Licensing Server.

>> When I check with the administrative tool everything seems OK.

>> How can I resolve this problem

>> "The Terminal Services Licensing server 'servername' has no

>> license pack registered for product 'Windows 2000 Terminal

>> Services Client Access License'. Use Terminal Services Licensing

>> administrative tool to register the licenses pack. "

>>

>> When I check with the administrative tool everything seems OK.

>> I already reinstalled the Terminal Server Licensing Server, that

>> didn't change a thing.

>> How can I resolve this problem.

>>

>> Thanks

Guest Vera Noest [MVP]
Posted

Re: Terminal Server Licensing Server issue

 

OK, thanks, now I've got a better picture of the situation.

You might have to delete the locally stored license from the

clients which can't connect. On thin clients, this is usually

achieved by resetting them to the factory defaults.

 

http://www.eventid.net/display.asp?eventid=22&eventno=3268

&source=TermServLicensing&phase=1

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007 in

microsoft.public.windows.terminal_services:

> "everything seems ok" i mean

> the server is activated, license for Windows 2000 TSCAL is there

> with the correct number of CAL's.

> We are connecting from linux based ThinClients.

> After reinstalling the Terminal Server Licensing server and

> activating and adding the W2K TSCAL there aren't any expired

> licenses. Most clients can connect, few can't

> This LS was working since 2004, and all of a sudden it doesn't.

> No fixes have been installed recently.

>

> thanks

> Kris

>

>

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

> in message

> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>> Can you specify "everything seems OK"?

>> When you start the TS Licensing Manager on your TS Licensing

>> Server, which licenses are recorded there?

>> Did you purchase and install any Licensing Packs?

>> Do you have down-level clients which need a purchased TS CAL?

>> Note that all clients except W2K Pro, XP Pro and Vista need

>> one. Are there expired temporary licenses?

>> Can clients still connect?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>>

>>> Hi,

>>>

>>> All of a sudden i get the eventid error 22 on my Windows 2000

>>> Licensing Server.

>>> When I check with the administrative tool everything seems OK.

>>> How can I resolve this problem

>>> "The Terminal Services Licensing server 'servername' has no

>>> license pack registered for product 'Windows 2000 Terminal

>>> Services Client Access License'. Use Terminal Services

>>> Licensing administrative tool to register the licenses pack. "

>>>

>>> When I check with the administrative tool everything seems OK.

>>> I already reinstalled the Terminal Server Licensing Server,

>>> that didn't change a thing.

>>> How can I resolve this problem.

>>>

>>> Thanks

Posted

Re: Terminal Server Licensing Server issue

 

Hi,

 

This doesn' help the situation, i already installed hotfix KB827355.(update

Lserver.exe)

Nothing seems to do the trick.

 

Thanks

Kris

 

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

news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

> OK, thanks, now I've got a better picture of the situation.

> You might have to delete the locally stored license from the

> clients which can't connect. On thin clients, this is usually

> achieved by resetting them to the factory defaults.

>

> http://www.eventid.net/display.asp?eventid=22&eventno=3268

> &source=TermServLicensing&phase=1

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007 in

> microsoft.public.windows.terminal_services:

>

>> "everything seems ok" i mean

>> the server is activated, license for Windows 2000 TSCAL is there

>> with the correct number of CAL's.

>> We are connecting from linux based ThinClients.

>> After reinstalling the Terminal Server Licensing server and

>> activating and adding the W2K TSCAL there aren't any expired

>> licenses. Most clients can connect, few can't

>> This LS was working since 2004, and all of a sudden it doesn't.

>> No fixes have been installed recently.

>>

>> thanks

>> Kris

>>

>>

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

>> in message

>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>> Can you specify "everything seems OK"?

>>> When you start the TS Licensing Manager on your TS Licensing

>>> Server, which licenses are recorded there?

>>> Did you purchase and install any Licensing Packs?

>>> Do you have down-level clients which need a purchased TS CAL?

>>> Note that all clients except W2K Pro, XP Pro and Vista need

>>> one. Are there expired temporary licenses?

>>> Can clients still connect?

>>>

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>>>

>>>> Hi,

>>>>

>>>> All of a sudden i get the eventid error 22 on my Windows 2000

>>>> Licensing Server.

>>>> When I check with the administrative tool everything seems OK.

>>>> How can I resolve this problem

>>>> "The Terminal Services Licensing server 'servername' has no

>>>> license pack registered for product 'Windows 2000 Terminal

>>>> Services Client Access License'. Use Terminal Services

>>>> Licensing administrative tool to register the licenses pack. "

>>>>

>>>> When I check with the administrative tool everything seems OK.

>>>> I already reinstalled the Terminal Server Licensing Server,

>>>> that didn't change a thing.

>>>> How can I resolve this problem.

>>>>

>>>> Thanks

Guest Vera Noest [MVP]
Posted

Re: Terminal Server Licensing Server issue

 

When you delete the locally stored license, does the client get a

temporary license on first connection, as it should?

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Kris" <kris.van.wijmeersch@awe.be> wrote on 16 aug 2007 in

microsoft.public.windows.terminal_services:

> Hi,

>

> This doesn' help the situation, i already installed hotfix

> KB827355.(update Lserver.exe)

> Nothing seems to do the trick.

>

> Thanks

> Kris

>

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

> in message

> news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

>> OK, thanks, now I've got a better picture of the situation.

>> You might have to delete the locally stored license from the

>> clients which can't connect. On thin clients, this is usually

>> achieved by resetting them to the factory defaults.

>>

>> http://www.eventid.net/display.asp?eventid=22&eventno=3268

>> &source=TermServLicensing&phase=1

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> "everything seems ok" i mean

>>> the server is activated, license for Windows 2000 TSCAL is

>>> there with the correct number of CAL's.

>>> We are connecting from linux based ThinClients.

>>> After reinstalling the Terminal Server Licensing server and

>>> activating and adding the W2K TSCAL there aren't any expired

>>> licenses. Most clients can connect, few can't

>>> This LS was working since 2004, and all of a sudden it

>>> doesn't. No fixes have been installed recently.

>>>

>>> thanks

>>> Kris

>>>

>>>

>>> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>

>>> wrote in message

>>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>>> Can you specify "everything seems OK"?

>>>> When you start the TS Licensing Manager on your TS Licensing

>>>> Server, which licenses are recorded there?

>>>> Did you purchase and install any Licensing Packs?

>>>> Do you have down-level clients which need a purchased TS CAL?

>>>> Note that all clients except W2K Pro, XP Pro and Vista need

>>>> one. Are there expired temporary licenses?

>>>> Can clients still connect?

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

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

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

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

>>>>

>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>>>>

>>>>> Hi,

>>>>>

>>>>> All of a sudden i get the eventid error 22 on my Windows

>>>>> 2000 Licensing Server.

>>>>> When I check with the administrative tool everything seems

>>>>> OK. How can I resolve this problem

>>>>> "The Terminal Services Licensing server 'servername' has no

>>>>> license pack registered for product 'Windows 2000 Terminal

>>>>> Services Client Access License'. Use Terminal Services

>>>>> Licensing administrative tool to register the licenses pack.

>>>>> "

>>>>>

>>>>> When I check with the administrative tool everything seems

>>>>> OK. I already reinstalled the Terminal Server Licensing

>>>>> Server, that didn't change a thing.

>>>>> How can I resolve this problem.

>>>>>

>>>>> Thanks

Posted

Re: Terminal Server Licensing Server issue

 

No, can there be any influance that in a daughtercompany they installed an

additional W2K3 Domain controller and

activated a TSLS with 2003 TSCAL installed. Is it possible to have multiple

LS in the same domain?

Mine for 2000 TSCAL on a 2000DC and for them a 2003DC for 2003 TSCAL.

 

Thanks

Kris

 

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

news:Xns998EDEA2A7633veranoesthemutforsse@207.46.248.16...

> When you delete the locally stored license, does the client get a

> temporary license on first connection, as it should?

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Kris" <kris.van.wijmeersch@awe.be> wrote on 16 aug 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hi,

>>

>> This doesn' help the situation, i already installed hotfix

>> KB827355.(update Lserver.exe)

>> Nothing seems to do the trick.

>>

>> Thanks

>> Kris

>>

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

>> in message

>> news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

>>> OK, thanks, now I've got a better picture of the situation.

>>> You might have to delete the locally stored license from the

>>> clients which can't connect. On thin clients, this is usually

>>> achieved by resetting them to the factory defaults.

>>>

>>> http://www.eventid.net/display.asp?eventid=22&eventno=3268

>>> &source=TermServLicensing&phase=1

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> "everything seems ok" i mean

>>>> the server is activated, license for Windows 2000 TSCAL is

>>>> there with the correct number of CAL's.

>>>> We are connecting from linux based ThinClients.

>>>> After reinstalling the Terminal Server Licensing server and

>>>> activating and adding the W2K TSCAL there aren't any expired

>>>> licenses. Most clients can connect, few can't

>>>> This LS was working since 2004, and all of a sudden it

>>>> doesn't. No fixes have been installed recently.

>>>>

>>>> thanks

>>>> Kris

>>>>

>>>>

>>>> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>

>>>> wrote in message

>>>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>>>> Can you specify "everything seems OK"?

>>>>> When you start the TS Licensing Manager on your TS Licensing

>>>>> Server, which licenses are recorded there?

>>>>> Did you purchase and install any Licensing Packs?

>>>>> Do you have down-level clients which need a purchased TS CAL?

>>>>> Note that all clients except W2K Pro, XP Pro and Vista need

>>>>> one. Are there expired temporary licenses?

>>>>> Can clients still connect?

>>>>>

>>>>> _________________________________________________________

>>>>> Vera Noest

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

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

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

>>>>>

>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>>>>>

>>>>>> Hi,

>>>>>>

>>>>>> All of a sudden i get the eventid error 22 on my Windows

>>>>>> 2000 Licensing Server.

>>>>>> When I check with the administrative tool everything seems

>>>>>> OK. How can I resolve this problem

>>>>>> "The Terminal Services Licensing server 'servername' has no

>>>>>> license pack registered for product 'Windows 2000 Terminal

>>>>>> Services Client Access License'. Use Terminal Services

>>>>>> Licensing administrative tool to register the licenses pack.

>>>>>> "

>>>>>>

>>>>>> When I check with the administrative tool everything seems

>>>>>> OK. I already reinstalled the Terminal Server Licensing

>>>>>> Server, that didn't change a thing.

>>>>>> How can I resolve this problem.

>>>>>>

>>>>>> Thanks

Posted

Re: Terminal Server Licensing Server issue

 

I don't have a line in the admin tool that says "tempory license"

I only have "Existing W2K license : unlimited" and "W2K TSCAL"

Does that give any indication what might be wrong.

 

"Kris" <kris.van.wijmeersch@awe.be> wrote in message

news:OrYNjpJ4HHA.4436@TK2MSFTNGP03.phx.gbl...

> No, can there be any influance that in a daughtercompany they installed an

> additional W2K3 Domain controller and

> activated a TSLS with 2003 TSCAL installed. Is it possible to have

> multiple LS in the same domain?

> Mine for 2000 TSCAL on a 2000DC and for them a 2003DC for 2003 TSCAL.

>

> Thanks

> Kris

>

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

> news:Xns998EDEA2A7633veranoesthemutforsse@207.46.248.16...

>> When you delete the locally stored license, does the client get a

>> temporary license on first connection, as it should?

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 16 aug 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hi,

>>>

>>> This doesn' help the situation, i already installed hotfix

>>> KB827355.(update Lserver.exe)

>>> Nothing seems to do the trick.

>>>

>>> Thanks

>>> Kris

>>>

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

>>> in message

>>> news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

>>>> OK, thanks, now I've got a better picture of the situation.

>>>> You might have to delete the locally stored license from the

>>>> clients which can't connect. On thin clients, this is usually

>>>> achieved by resetting them to the factory defaults.

>>>>

>>>> http://www.eventid.net/display.asp?eventid=22&eventno=3268

>>>> &source=TermServLicensing&phase=1

>>>> _________________________________________________________

>>>> Vera Noest

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

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

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

>>>>

>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007 in

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

>>>>

>>>>> "everything seems ok" i mean

>>>>> the server is activated, license for Windows 2000 TSCAL is

>>>>> there with the correct number of CAL's.

>>>>> We are connecting from linux based ThinClients.

>>>>> After reinstalling the Terminal Server Licensing server and

>>>>> activating and adding the W2K TSCAL there aren't any expired

>>>>> licenses. Most clients can connect, few can't

>>>>> This LS was working since 2004, and all of a sudden it

>>>>> doesn't. No fixes have been installed recently.

>>>>>

>>>>> thanks

>>>>> Kris

>>>>>

>>>>>

>>>>> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>

>>>>> wrote in message

>>>>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>>>>> Can you specify "everything seems OK"?

>>>>>> When you start the TS Licensing Manager on your TS Licensing

>>>>>> Server, which licenses are recorded there?

>>>>>> Did you purchase and install any Licensing Packs?

>>>>>> Do you have down-level clients which need a purchased TS CAL?

>>>>>> Note that all clients except W2K Pro, XP Pro and Vista need

>>>>>> one. Are there expired temporary licenses?

>>>>>> Can clients still connect?

>>>>>>

>>>>>> _________________________________________________________

>>>>>> Vera Noest

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

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

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

>>>>>>

>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>>>>>>

>>>>>>> Hi,

>>>>>>>

>>>>>>> All of a sudden i get the eventid error 22 on my Windows

>>>>>>> 2000 Licensing Server.

>>>>>>> When I check with the administrative tool everything seems

>>>>>>> OK. How can I resolve this problem

>>>>>>> "The Terminal Services Licensing server 'servername' has no

>>>>>>> license pack registered for product 'Windows 2000 Terminal

>>>>>>> Services Client Access License'. Use Terminal Services

>>>>>>> Licensing administrative tool to register the licenses pack.

>>>>>>> "

>>>>>>>

>>>>>>> When I check with the administrative tool everything seems

>>>>>>> OK. I already reinstalled the Terminal Server Licensing

>>>>>>> Server, that didn't change a thing.

>>>>>>> How can I resolve this problem.

>>>>>>>

>>>>>>> Thanks

>

>

Guest Vera Noest [MVP]
Posted

Re: Terminal Server Licensing Server issue

 

Yes.

When a totally new client, or an existing client from which you

have deleted the locally stored license, connects for the first

time, it gets a temporary license. After the second connection, it

gets a permanent license.

 

If your client (after deleting the local license) can connect

*once*, it means that it must have received a temporary license. If

you don't see that temporary license on your TS Licensing Server,

chances are that it is indeed issued by the new 2003 TS LS. And if

that LS doesn't have permanent W2K TS CALs *AND* it has been

configured to not issue 2003 TS CALs to clients connecting to W2K

Terminal Servers, that would explain your situation.

 

It's perfectly possible to have multiple Licensing Servers in the

domain, but you have to design if and how they should cooperate.

If you want to keep them completely separate, then you should

configure your W2K Terminal Servers to only contact your W2K TS

Licensing Servers.

Described here:

 

239107 - Establishing Preferred Windows 2000 Terminal Services

License Server

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

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

 

"Kris" <kris.van.wijmeersch@awe.be> wrote on 17 aug 2007:

> I don't have a line in the admin tool that says "tempory

> license" I only have "Existing W2K license : unlimited" and "W2K

> TSCAL" Does that give any indication what might be wrong.

>

> "Kris" <kris.van.wijmeersch@awe.be> wrote in message

> news:OrYNjpJ4HHA.4436@TK2MSFTNGP03.phx.gbl...

>> No, can there be any influance that in a daughtercompany they

>> installed an additional W2K3 Domain controller and

>> activated a TSLS with 2003 TSCAL installed. Is it possible to

>> have multiple LS in the same domain?

>> Mine for 2000 TSCAL on a 2000DC and for them a 2003DC for 2003

>> TSCAL.

>>

>> Thanks

>> Kris

>>

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

>> in message

>> news:Xns998EDEA2A7633veranoesthemutforsse@207.46.248.16...

>>> When you delete the locally stored license, does the client

>>> get a temporary license on first connection, as it should?

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 16 aug 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hi,

>>>>

>>>> This doesn' help the situation, i already installed hotfix

>>>> KB827355.(update Lserver.exe)

>>>> Nothing seems to do the trick.

>>>>

>>>> Thanks

>>>> Kris

>>>>

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

>>>> wrote in message

>>>> news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

>>>>> OK, thanks, now I've got a better picture of the situation.

>>>>> You might have to delete the locally stored license from the

>>>>> clients which can't connect. On thin clients, this is

>>>>> usually achieved by resetting them to the factory defaults.

>>>>>

>>>>> http://www.eventid.net/display.asp?eventid=22&eventno=3268

>>>>> &source=TermServLicensing&phase=1

>>>>> _________________________________________________________

>>>>> Vera Noest

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

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

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

>>>>>

>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007 in

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

>>>>>

>>>>>> "everything seems ok" i mean

>>>>>> the server is activated, license for Windows 2000 TSCAL is

>>>>>> there with the correct number of CAL's.

>>>>>> We are connecting from linux based ThinClients.

>>>>>> After reinstalling the Terminal Server Licensing server and

>>>>>> activating and adding the W2K TSCAL there aren't any

>>>>>> expired licenses. Most clients can connect, few can't

>>>>>> This LS was working since 2004, and all of a sudden it

>>>>>> doesn't. No fixes have been installed recently.

>>>>>>

>>>>>> thanks

>>>>>> Kris

>>>>>>

>>>>>>

>>>>>> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>

>>>>>> wrote in message

>>>>>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>>>>>> Can you specify "everything seems OK"?

>>>>>>> When you start the TS Licensing Manager on your TS

>>>>>>> Licensing Server, which licenses are recorded there?

>>>>>>> Did you purchase and install any Licensing Packs?

>>>>>>> Do you have down-level clients which need a purchased TS

>>>>>>> CAL? Note that all clients except W2K Pro, XP Pro and

>>>>>>> Vista need one. Are there expired temporary licenses?

>>>>>>> Can clients still connect?

>>>>>>>

>>>>>>> _________________________________________________________

>>>>>>> Vera Noest

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

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

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

>>>>>>>

>>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>>>>>>>

>>>>>>>> Hi,

>>>>>>>>

>>>>>>>> All of a sudden i get the eventid error 22 on my Windows

>>>>>>>> 2000 Licensing Server.

>>>>>>>> When I check with the administrative tool everything

>>>>>>>> seems OK. How can I resolve this problem

>>>>>>>> "The Terminal Services Licensing server 'servername' has

>>>>>>>> no license pack registered for product 'Windows 2000

>>>>>>>> Terminal Services Client Access License'. Use Terminal

>>>>>>>> Services Licensing administrative tool to register the

>>>>>>>> licenses pack. "

>>>>>>>>

>>>>>>>> When I check with the administrative tool everything

>>>>>>>> seems OK. I already reinstalled the Terminal Server

>>>>>>>> Licensing Server, that didn't change a thing.

>>>>>>>> How can I resolve this problem.

>>>>>>>>

>>>>>>>> Thanks

Posted

Re: Terminal Server Licensing Server issue

 

I had already configured my Terminal Servers to contact my TSLS with that

registry change.

But how do I get my TSLS to give those temporary licenses instead of the

other one.

Does this gave me error "TermServlicensing Event id 22" on my TSLS?

 

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

news:Xns998F822CBB75Everanoesthemutforsse@207.46.248.16...

> Yes.

> When a totally new client, or an existing client from which you

> have deleted the locally stored license, connects for the first

> time, it gets a temporary license. After the second connection, it

> gets a permanent license.

>

> If your client (after deleting the local license) can connect

> *once*, it means that it must have received a temporary license. If

> you don't see that temporary license on your TS Licensing Server,

> chances are that it is indeed issued by the new 2003 TS LS. And if

> that LS doesn't have permanent W2K TS CALs *AND* it has been

> configured to not issue 2003 TS CALs to clients connecting to W2K

> Terminal Servers, that would explain your situation.

>

> It's perfectly possible to have multiple Licensing Servers in the

> domain, but you have to design if and how they should cooperate.

> If you want to keep them completely separate, then you should

> configure your W2K Terminal Servers to only contact your W2K TS

> Licensing Servers.

> Described here:

>

> 239107 - Establishing Preferred Windows 2000 Terminal Services

> License Server

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

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Kris" <kris.van.wijmeersch@awe.be> wrote on 17 aug 2007:

>

>> I don't have a line in the admin tool that says "tempory

>> license" I only have "Existing W2K license : unlimited" and "W2K

>> TSCAL" Does that give any indication what might be wrong.

>>

>> "Kris" <kris.van.wijmeersch@awe.be> wrote in message

>> news:OrYNjpJ4HHA.4436@TK2MSFTNGP03.phx.gbl...

>>> No, can there be any influance that in a daughtercompany they

>>> installed an additional W2K3 Domain controller and

>>> activated a TSLS with 2003 TSCAL installed. Is it possible to

>>> have multiple LS in the same domain?

>>> Mine for 2000 TSCAL on a 2000DC and for them a 2003DC for 2003

>>> TSCAL.

>>>

>>> Thanks

>>> Kris

>>>

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

>>> in message

>>> news:Xns998EDEA2A7633veranoesthemutforsse@207.46.248.16...

>>>> When you delete the locally stored license, does the client

>>>> get a temporary license on first connection, as it should?

>>>> _________________________________________________________

>>>> Vera Noest

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

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

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

>>>>

>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 16 aug 2007 in

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

>>>>

>>>>> Hi,

>>>>>

>>>>> This doesn' help the situation, i already installed hotfix

>>>>> KB827355.(update Lserver.exe)

>>>>> Nothing seems to do the trick.

>>>>>

>>>>> Thanks

>>>>> Kris

>>>>>

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

>>>>> wrote in message

>>>>> news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

>>>>>> OK, thanks, now I've got a better picture of the situation.

>>>>>> You might have to delete the locally stored license from the

>>>>>> clients which can't connect. On thin clients, this is

>>>>>> usually achieved by resetting them to the factory defaults.

>>>>>>

>>>>>> http://www.eventid.net/display.asp?eventid=22&eventno=3268

>>>>>> &source=TermServLicensing&phase=1

>>>>>> _________________________________________________________

>>>>>> Vera Noest

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

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

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

>>>>>>

>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007 in

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

>>>>>>

>>>>>>> "everything seems ok" i mean

>>>>>>> the server is activated, license for Windows 2000 TSCAL is

>>>>>>> there with the correct number of CAL's.

>>>>>>> We are connecting from linux based ThinClients.

>>>>>>> After reinstalling the Terminal Server Licensing server and

>>>>>>> activating and adding the W2K TSCAL there aren't any

>>>>>>> expired licenses. Most clients can connect, few can't

>>>>>>> This LS was working since 2004, and all of a sudden it

>>>>>>> doesn't. No fixes have been installed recently.

>>>>>>>

>>>>>>> thanks

>>>>>>> Kris

>>>>>>>

>>>>>>>

>>>>>>> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>

>>>>>>> wrote in message

>>>>>>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>>>>>>> Can you specify "everything seems OK"?

>>>>>>>> When you start the TS Licensing Manager on your TS

>>>>>>>> Licensing Server, which licenses are recorded there?

>>>>>>>> Did you purchase and install any Licensing Packs?

>>>>>>>> Do you have down-level clients which need a purchased TS

>>>>>>>> CAL? Note that all clients except W2K Pro, XP Pro and

>>>>>>>> Vista need one. Are there expired temporary licenses?

>>>>>>>> Can clients still connect?

>>>>>>>>

>>>>>>>> _________________________________________________________

>>>>>>>> Vera Noest

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

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

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

>>>>>>>>

>>>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007:

>>>>>>>>

>>>>>>>>> Hi,

>>>>>>>>>

>>>>>>>>> All of a sudden i get the eventid error 22 on my Windows

>>>>>>>>> 2000 Licensing Server.

>>>>>>>>> When I check with the administrative tool everything

>>>>>>>>> seems OK. How can I resolve this problem

>>>>>>>>> "The Terminal Services Licensing server 'servername' has

>>>>>>>>> no license pack registered for product 'Windows 2000

>>>>>>>>> Terminal Services Client Access License'. Use Terminal

>>>>>>>>> Services Licensing administrative tool to register the

>>>>>>>>> licenses pack. "

>>>>>>>>>

>>>>>>>>> When I check with the administrative tool everything

>>>>>>>>> seems OK. I already reinstalled the Terminal Server

>>>>>>>>> Licensing Server, that didn't change a thing.

>>>>>>>>> How can I resolve this problem.

>>>>>>>>>

>>>>>>>>> Thanks

Guest Vera Noest [MVP]
Posted

Re: Terminal Server Licensing Server issue

 

I think it's time for a call to Microsoft Support, Kris.

If your TS connects to your LS, but it doesn't issue temporary

licenses to new clients, there's something wrong beyond the

"normal" licensing problems.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Kris" <kris.van.wijmeersch@awe.be> wrote on 17 aug 2007 in

microsoft.public.windows.terminal_services:

> I had already configured my Terminal Servers to contact my TSLS

> with that registry change.

> But how do I get my TSLS to give those temporary licenses

> instead of the other one.

> Does this gave me error "TermServlicensing Event id 22" on my

> TSLS?

>

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

> in message

> news:Xns998F822CBB75Everanoesthemutforsse@207.46.248.16...

>> Yes.

>> When a totally new client, or an existing client from which you

>> have deleted the locally stored license, connects for the first

>> time, it gets a temporary license. After the second connection,

>> it gets a permanent license.

>>

>> If your client (after deleting the local license) can connect

>> *once*, it means that it must have received a temporary

>> license. If you don't see that temporary license on your TS

>> Licensing Server, chances are that it is indeed issued by the

>> new 2003 TS LS. And if that LS doesn't have permanent W2K TS

>> CALs *AND* it has been configured to not issue 2003 TS CALs to

>> clients connecting to W2K Terminal Servers, that would explain

>> your situation.

>>

>> It's perfectly possible to have multiple Licensing Servers in

>> the domain, but you have to design if and how they should

>> cooperate. If you want to keep them completely separate, then

>> you should configure your W2K Terminal Servers to only contact

>> your W2K TS Licensing Servers.

>> Described here:

>>

>> 239107 - Establishing Preferred Windows 2000 Terminal Services

>> License Server

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

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 17 aug 2007:

>>

>>> I don't have a line in the admin tool that says "tempory

>>> license" I only have "Existing W2K license : unlimited" and

>>> "W2K TSCAL" Does that give any indication what might be wrong.

>>>

>>> "Kris" <kris.van.wijmeersch@awe.be> wrote in message

>>> news:OrYNjpJ4HHA.4436@TK2MSFTNGP03.phx.gbl...

>>>> No, can there be any influance that in a daughtercompany they

>>>> installed an additional W2K3 Domain controller and

>>>> activated a TSLS with 2003 TSCAL installed. Is it possible to

>>>> have multiple LS in the same domain?

>>>> Mine for 2000 TSCAL on a 2000DC and for them a 2003DC for

>>>> 2003 TSCAL.

>>>>

>>>> Thanks

>>>> Kris

>>>>

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

>>>> wrote in message

>>>> news:Xns998EDEA2A7633veranoesthemutforsse@207.46.248.16...

>>>>> When you delete the locally stored license, does the client

>>>>> get a temporary license on first connection, as it should?

>>>>> _________________________________________________________

>>>>> Vera Noest

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

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

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

>>>>>

>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 16 aug 2007 in

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

>>>>>

>>>>>> Hi,

>>>>>>

>>>>>> This doesn' help the situation, i already installed hotfix

>>>>>> KB827355.(update Lserver.exe)

>>>>>> Nothing seems to do the trick.

>>>>>>

>>>>>> Thanks

>>>>>> Kris

>>>>>>

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

>>>>>> wrote in message

>>>>>> news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

>>>>>>> OK, thanks, now I've got a better picture of the

>>>>>>> situation. You might have to delete the locally stored

>>>>>>> license from the clients which can't connect. On thin

>>>>>>> clients, this is usually achieved by resetting them to the

>>>>>>> factory defaults.

>>>>>>>

>>>>>>> http://www.eventid.net/display.asp?eventid=22&eventno=3268

>>>>>>> &source=TermServLicensing&phase=1

>>>>>>> _________________________________________________________

>>>>>>> Vera Noest

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

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

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

>>>>>>>

>>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007

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

>>>>>>>

>>>>>>>> "everything seems ok" i mean

>>>>>>>> the server is activated, license for Windows 2000 TSCAL

>>>>>>>> is there with the correct number of CAL's.

>>>>>>>> We are connecting from linux based ThinClients.

>>>>>>>> After reinstalling the Terminal Server Licensing server

>>>>>>>> and activating and adding the W2K TSCAL there aren't any

>>>>>>>> expired licenses. Most clients can connect, few can't

>>>>>>>> This LS was working since 2004, and all of a sudden it

>>>>>>>> doesn't. No fixes have been installed recently.

>>>>>>>>

>>>>>>>> thanks

>>>>>>>> Kris

>>>>>>>>

>>>>>>>>

>>>>>>>> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>

>>>>>>>> wrote in message

>>>>>>>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>>>>>>>> Can you specify "everything seems OK"?

>>>>>>>>> When you start the TS Licensing Manager on your TS

>>>>>>>>> Licensing Server, which licenses are recorded there?

>>>>>>>>> Did you purchase and install any Licensing Packs?

>>>>>>>>> Do you have down-level clients which need a purchased TS

>>>>>>>>> CAL? Note that all clients except W2K Pro, XP Pro and

>>>>>>>>> Vista need one. Are there expired temporary licenses?

>>>>>>>>> Can clients still connect?

>>>>>>>>>

>>>>>>>>> _________________________________________________________

>>>>>>>>> Vera Noest

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

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

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

>>>>>>>>>

>>>>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug

>>>>>>>>> 2007:

>>>>>>>>>

>>>>>>>>>> Hi,

>>>>>>>>>>

>>>>>>>>>> All of a sudden i get the eventid error 22 on my

>>>>>>>>>> Windows 2000 Licensing Server.

>>>>>>>>>> When I check with the administrative tool everything

>>>>>>>>>> seems OK. How can I resolve this problem

>>>>>>>>>> "The Terminal Services Licensing server 'servername'

>>>>>>>>>> has no license pack registered for product 'Windows

>>>>>>>>>> 2000 Terminal Services Client Access License'. Use

>>>>>>>>>> Terminal Services Licensing administrative tool to

>>>>>>>>>> register the licenses pack. "

>>>>>>>>>>

>>>>>>>>>> When I check with the administrative tool everything

>>>>>>>>>> seems OK. I already reinstalled the Terminal Server

>>>>>>>>>> Licensing Server, that didn't change a thing.

>>>>>>>>>> How can I resolve this problem.

>>>>>>>>>>

>>>>>>>>>> Thanks

Posted

Re: Terminal Server Licensing Server issue

 

Thanks Vera for your support.

 

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

news:Xns998FEA4D92782veranoesthemutforsse@207.46.248.16...

>I think it's time for a call to Microsoft Support, Kris.

> If your TS connects to your LS, but it doesn't issue temporary

> licenses to new clients, there's something wrong beyond the

> "normal" licensing problems.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Kris" <kris.van.wijmeersch@awe.be> wrote on 17 aug 2007 in

> microsoft.public.windows.terminal_services:

>

>> I had already configured my Terminal Servers to contact my TSLS

>> with that registry change.

>> But how do I get my TSLS to give those temporary licenses

>> instead of the other one.

>> Does this gave me error "TermServlicensing Event id 22" on my

>> TSLS?

>>

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

>> in message

>> news:Xns998F822CBB75Everanoesthemutforsse@207.46.248.16...

>>> Yes.

>>> When a totally new client, or an existing client from which you

>>> have deleted the locally stored license, connects for the first

>>> time, it gets a temporary license. After the second connection,

>>> it gets a permanent license.

>>>

>>> If your client (after deleting the local license) can connect

>>> *once*, it means that it must have received a temporary

>>> license. If you don't see that temporary license on your TS

>>> Licensing Server, chances are that it is indeed issued by the

>>> new 2003 TS LS. And if that LS doesn't have permanent W2K TS

>>> CALs *AND* it has been configured to not issue 2003 TS CALs to

>>> clients connecting to W2K Terminal Servers, that would explain

>>> your situation.

>>>

>>> It's perfectly possible to have multiple Licensing Servers in

>>> the domain, but you have to design if and how they should

>>> cooperate. If you want to keep them completely separate, then

>>> you should configure your W2K Terminal Servers to only contact

>>> your W2K TS Licensing Servers.

>>> Described here:

>>>

>>> 239107 - Establishing Preferred Windows 2000 Terminal Services

>>> License Server

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

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 17 aug 2007:

>>>

>>>> I don't have a line in the admin tool that says "tempory

>>>> license" I only have "Existing W2K license : unlimited" and

>>>> "W2K TSCAL" Does that give any indication what might be wrong.

>>>>

>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote in message

>>>> news:OrYNjpJ4HHA.4436@TK2MSFTNGP03.phx.gbl...

>>>>> No, can there be any influance that in a daughtercompany they

>>>>> installed an additional W2K3 Domain controller and

>>>>> activated a TSLS with 2003 TSCAL installed. Is it possible to

>>>>> have multiple LS in the same domain?

>>>>> Mine for 2000 TSCAL on a 2000DC and for them a 2003DC for

>>>>> 2003 TSCAL.

>>>>>

>>>>> Thanks

>>>>> Kris

>>>>>

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

>>>>> wrote in message

>>>>> news:Xns998EDEA2A7633veranoesthemutforsse@207.46.248.16...

>>>>>> When you delete the locally stored license, does the client

>>>>>> get a temporary license on first connection, as it should?

>>>>>> _________________________________________________________

>>>>>> Vera Noest

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

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

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

>>>>>>

>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 16 aug 2007 in

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

>>>>>>

>>>>>>> Hi,

>>>>>>>

>>>>>>> This doesn' help the situation, i already installed hotfix

>>>>>>> KB827355.(update Lserver.exe)

>>>>>>> Nothing seems to do the trick.

>>>>>>>

>>>>>>> Thanks

>>>>>>> Kris

>>>>>>>

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

>>>>>>> wrote in message

>>>>>>> news:Xns998CE2766251Bveranoesthemutforsse@207.46.248.16...

>>>>>>>> OK, thanks, now I've got a better picture of the

>>>>>>>> situation. You might have to delete the locally stored

>>>>>>>> license from the clients which can't connect. On thin

>>>>>>>> clients, this is usually achieved by resetting them to the

>>>>>>>> factory defaults.

>>>>>>>>

>>>>>>>> http://www.eventid.net/display.asp?eventid=22&eventno=3268

>>>>>>>> &source=TermServLicensing&phase=1

>>>>>>>> _________________________________________________________

>>>>>>>> Vera Noest

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

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

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

>>>>>>>>

>>>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug 2007

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

>>>>>>>>

>>>>>>>>> "everything seems ok" i mean

>>>>>>>>> the server is activated, license for Windows 2000 TSCAL

>>>>>>>>> is there with the correct number of CAL's.

>>>>>>>>> We are connecting from linux based ThinClients.

>>>>>>>>> After reinstalling the Terminal Server Licensing server

>>>>>>>>> and activating and adding the W2K TSCAL there aren't any

>>>>>>>>> expired licenses. Most clients can connect, few can't

>>>>>>>>> This LS was working since 2004, and all of a sudden it

>>>>>>>>> doesn't. No fixes have been installed recently.

>>>>>>>>>

>>>>>>>>> thanks

>>>>>>>>> Kris

>>>>>>>>>

>>>>>>>>>

>>>>>>>>> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>

>>>>>>>>> wrote in message

>>>>>>>>> news:Xns998CA3CA7893Averanoesthemutforsse@207.46.248.16...

>>>>>>>>>> Can you specify "everything seems OK"?

>>>>>>>>>> When you start the TS Licensing Manager on your TS

>>>>>>>>>> Licensing Server, which licenses are recorded there?

>>>>>>>>>> Did you purchase and install any Licensing Packs?

>>>>>>>>>> Do you have down-level clients which need a purchased TS

>>>>>>>>>> CAL? Note that all clients except W2K Pro, XP Pro and

>>>>>>>>>> Vista need one. Are there expired temporary licenses?

>>>>>>>>>> Can clients still connect?

>>>>>>>>>>

>>>>>>>>>> _________________________________________________________

>>>>>>>>>> Vera Noest

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

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

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

>>>>>>>>>>

>>>>>>>>>> "Kris" <kris.van.wijmeersch@awe.be> wrote on 14 aug

>>>>>>>>>> 2007:

>>>>>>>>>>

>>>>>>>>>>> Hi,

>>>>>>>>>>>

>>>>>>>>>>> All of a sudden i get the eventid error 22 on my

>>>>>>>>>>> Windows 2000 Licensing Server.

>>>>>>>>>>> When I check with the administrative tool everything

>>>>>>>>>>> seems OK. How can I resolve this problem

>>>>>>>>>>> "The Terminal Services Licensing server 'servername'

>>>>>>>>>>> has no license pack registered for product 'Windows

>>>>>>>>>>> 2000 Terminal Services Client Access License'. Use

>>>>>>>>>>> Terminal Services Licensing administrative tool to

>>>>>>>>>>> register the licenses pack. "

>>>>>>>>>>>

>>>>>>>>>>> When I check with the administrative tool everything

>>>>>>>>>>> seems OK. I already reinstalled the Terminal Server

>>>>>>>>>>> Licensing Server, that didn't change a thing.

>>>>>>>>>>> How can I resolve this problem.

>>>>>>>>>>>

>>>>>>>>>>> Thanks

×
×
  • Create New...