TS 2000 Workgroup server

[Guest DMorgan310]

We currently have a Win2K Terminal Server setup in its own Workgroup and it

is not a part of (and can't be) our windows 2003 Active Directory.

It has been working fine in this configuration and continues to work fine

for computers and users that have been on the network for a while, however,

as we get rid of old computers and set up the new computers something is

slipping through the cracks.

When we try to connect new computers to the terminal server through remote

desktop we get the error “The remote computer disconnected the session

because of an error in the licensing protocol. Please try connecting to the

remote computer again or contact your server administrator”

I have followed the instructions in TechKowledge article "Troubleshooting

Remote Desktop Licensing Error Messages

Updated: January 21, 2005" but that has not helped.

The TS is also the License server, and there are no errors in the Event

Logs. There are 30 TS Licenses and 30 devices on the License list however

some of them are old PCs that have been removed from the network for months.

Can those old PCs be removed from the list manually?

I haven't tried to Deactivate and reactivate the License server...yet.

Any troubleshooting advice would be greatly appreciated.

[Guest Frane]

Re: TS 2000 Workgroup server

 

Do you have any available license for new computers that are tryng to

connect?

If not then issued licenses would automatically expire after a random

period between 52-89 days and become part of the available license

pool.

If you need immediately CALs then I would suggest you to reactivate

server.

[Guest DMorgan310]

Re: TS 2000 Workgroup server

 

My concern is that this is a mission critical server running Dynamics GP

accounting. I can't afford to be down.

Some of the device licenses are even older than 90 days and they still

haven't been removed from the list.

If I reactivate the license server and have a problem, will my clients be

able to attach with a temporary license as if it was a brand new TS?

Unfortunately I don't have a test server to play with, this is an all or

nothing change so I can't afford to make a mistake.

 

"Frane" wrote:

> Do you have any available license for new computers that are tryng to

> connect?

> If not then issued licenses would automatically expire after a random

> period between 52-89 days and become part of the available license

> pool.

> If you need immediately CALs then I would suggest you to reactivate

> server.

>

[Guest Frane]

Re: TS 2000 Workgroup server

 

You will be able to use temporary cals on your server that are used in

grace period.

TSL server is easy to reactivate and it can be done in under five

minutes with all required data.

Choose to reactivate it on the end of the working day if possible.

 

_______________________________________________________

Frane Borozan

Terminal Services and Citrix Presentation Server user logging

http://www.terminalserviceslog.com

[Guest Vera Noest [MVP]]

Re: TS 2000 Workgroup server

 

I don't think that this is true!

It is the Terminal Server, not the TS Licensing Server, which has a

grace period. And once that is over, you can't get it back.

 

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

Frane <frane.borozan@gmail.com> wrote on 01 apr 2008 in

microsoft.public.windows.terminal_services:

> You will be able to use temporary cals on your server that are

> used in grace period.

> TSL server is easy to reactivate and it can be done in under

> five minutes with all required data.

> Choose to reactivate it on the end of the working day if

> possible.

[Guest Frane]

Re: TS 2000 Workgroup server

 

Then simple TSL reactivation will do the job.

 

The best would be to install temporary license server on other server

machine, override terminal services to use that temp LS(temp LS is in

grace period), then install local license server and reactivate it and

finally override terminal services to use again local LS.

 

 

_______________________________________________________

Frane Borozan

Terminal Services and Citrix Presentation Server user logging

http://www.terminalserviceslog.com

[Guest Vera Noest [MVP]]

Re: TS 2000 Workgroup server

 

There's something in this thread that I don't understand.

What OS are these new clients running? If they are running Windows

2000 Prof, XP Pro or Vista, you don't need a purchased TS CAL for

them at all.

These clients receive a free TS CAL from the built-in pool of

"Existing Windows 2000 TS CALs" on the TS Licensing Server. And

that pool is unlimited, so you can never have the problem of

running out of licenses.

 

I'm not sure exactly which troubleshooting steps you have

performed. Can you post a link to the page you mentioned, or detail

the steps?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

Frane <frane.borozan@gmail.com> wrote on 01 apr 2008 in

microsoft.public.windows.terminal_services:

> Do you have any available license for new computers that are

> tryng to connect?

> If not then issued licenses would automatically expire after a

> random period between 52-89 days and become part of the

> available license pool.

> If you need immediately CALs then I would suggest you to

> reactivate server.

[Guest DMorgan310]

Re: TS 2000 Workgroup server

 

Thanks for your input.

Here the TK link:

http://technet2.microsoft.com/windowsserver/en/library/159e6ff8-4edb-43fd-8767-3d9858897e2c1033.mspx?mfr=true

The new client PCs are all XP Pro. All PCs can ping the server by address

and Name. I have removed the Reg Key

(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing) and rebooted the clients

but still recieve the error described in my original post.

It's not a user permission problem because the admin can log on at one of

these new PCs and get the same error.

I look forward to your response.

 

"Vera Noest [MVP]" wrote:

> There's something in this thread that I don't understand.

> What OS are these new clients running? If they are running Windows

> 2000 Prof, XP Pro or Vista, you don't need a purchased TS CAL for

> them at all.

> These clients receive a free TS CAL from the built-in pool of

> "Existing Windows 2000 TS CALs" on the TS Licensing Server. And

> that pool is unlimited, so you can never have the problem of

> running out of licenses.

>

> I'm not sure exactly which troubleshooting steps you have

> performed. Can you post a link to the page you mentioned, or detail

> the steps?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> Frane <frane.borozan@gmail.com> wrote on 01 apr 2008 in

> microsoft.public.windows.terminal_services:

>

> > Do you have any available license for new computers that are

> > tryng to connect?

> > If not then issued licenses would automatically expire after a

> > random period between 52-89 days and become part of the

> > available license pool.

> > If you need immediately CALs then I would suggest you to

> > reactivate server.

>

[Guest Vera Noest [MVP]]

Re: TS 2000 Workgroup server

 

> (temp LS is in grace period)

Again: a LS doesn't have a grace period!

 

From:

813052 - Maximizing the Windows Server 2003 Terminal Services

Evaluation Period

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

 

Grace period: The period of time that a server that has Terminal

Services enabled allows unlimited connections without communicating

with a license server.

 

Sorry to be such a pain, but especially in licensing questions I

feel that it's important to give correct information.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

Frane <frane.borozan@gmail.com> wrote on 01 apr 2008 in

microsoft.public.windows.terminal_services:

> Then simple TSL reactivation will do the job.

>

> The best would be to install temporary license server on other

> server machine, override terminal services to use that temp

> LS(temp LS is in grace period), then install local license

> server and reactivate it and finally override terminal services

> to use again local LS.

[Guest Vera Noest [MVP]]

Re: TS 2000 Workgroup server

 

OK, let me get this straight:

after you deleted the licensing key from the registry of the

clients, where you able to connect once, or not at all?

Have you checked the firewall settings on the clients?

 

The best experiment to distinguish between a problem on the new

clients or on the server would be to delete the licensing key from

the registry of an old client, one which does *not* have a problem

to connect.

By deleting the key, you force the client to download a new license

from the LS. It doesn't cost you anything, because these licenses

are free and unlimited anyway.

If the test client gets a new license and connects without errors,

you know that the problem lies in the configuration of the new

clients.

If the test client now has the same problem, you know that the

cause lies with the licensing server itself.

 

_________________________________________________________

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?RE1vcmdhbjMxMA==?=

<DMorgan310@discussions.microsoft.com> wrote on 02 apr 2008 in

microsoft.public.windows.terminal_services:

> Thanks for your input.

> Here the TK link:

> http://technet2.microsoft.com/windowsserver/en/library/159e6ff8-4

> edb-43fd-8767-3d9858897e2c1033.mspx?mfr=true The new client PCs

> are all XP Pro. All PCs can ping the server by address and

> Name. I have removed the Reg Key

> (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing) and rebooted

> the clients but still recieve the error described in my original

> post. It's not a user permission problem because the admin can

> log on at one of these new PCs and get the same error.

> I look forward to your response.

>

> "Vera Noest [MVP]" wrote:

>

>> There's something in this thread that I don't understand.

>> What OS are these new clients running? If they are running

>> Windows 2000 Prof, XP Pro or Vista, you don't need a purchased

>> TS CAL for them at all.

>> These clients receive a free TS CAL from the built-in pool of

>> "Existing Windows 2000 TS CALs" on the TS Licensing Server. And

>> that pool is unlimited, so you can never have the problem of

>> running out of licenses.

>>

>> I'm not sure exactly which troubleshooting steps you have

>> performed. Can you post a link to the page you mentioned, or

>> detail the steps?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> Frane <frane.borozan@gmail.com> wrote on 01 apr 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > Do you have any available license for new computers that are

>> > tryng to connect?

>> > If not then issued licenses would automatically expire after

>> > a random period between 52-89 days and become part of the

>> > available license pool.

>> > If you need immediately CALs then I would suggest you to

>> > reactivate server.

[Guest DMorgan310]

Re: TS 2000 Workgroup server

 

The Firewall is turned off on all Client PCs.

 

The New PCs have not been able to connect at all, before or after the Reg

Key change.

 

I haven't tried to remove the license from a working PC because these are

mission critical accounting PCs and I can't afford to lose a TS connection.

 

I will try the license reactivation process after hours, but based on your

replies, it doesn't sound like the reactivation is the problem.

 

Do you have any other troubleshooting ideas?

 

 

Any further advice is greatly appreciated.

 

 

 

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

news:Xns9A74739A43E21veranoesthemutforsse@207.46.248.16...

> OK, let me get this straight:

> after you deleted the licensing key from the registry of the

> clients, where you able to connect once, or not at all?

> Have you checked the firewall settings on the clients?

>

> The best experiment to distinguish between a problem on the new

> clients or on the server would be to delete the licensing key from

> the registry of an old client, one which does *not* have a problem

> to connect.

> By deleting the key, you force the client to download a new license

> from the LS. It doesn't cost you anything, because these licenses

> are free and unlimited anyway.

> If the test client gets a new license and connects without errors,

> you know that the problem lies in the configuration of the new

> clients.

> If the test client now has the same problem, you know that the

> cause lies with the licensing server itself.

>

> _________________________________________________________

> 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?RE1vcmdhbjMxMA==?=

> <DMorgan310@discussions.microsoft.com> wrote on 02 apr 2008 in

> microsoft.public.windows.terminal_services:

>

>> Thanks for your input.

>> Here the TK link:

>> http://technet2.microsoft.com/windowsserver/en/library/159e6ff8-4

>> edb-43fd-8767-3d9858897e2c1033.mspx?mfr=true The new client PCs

>> are all XP Pro. All PCs can ping the server by address and

>> Name. I have removed the Reg Key

>> (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing) and rebooted

>> the clients but still recieve the error described in my original

>> post. It's not a user permission problem because the admin can

>> log on at one of these new PCs and get the same error.

>> I look forward to your response.

>>

>> "Vera Noest [MVP]" wrote:

>>

>>> There's something in this thread that I don't understand.

>>> What OS are these new clients running? If they are running

>>> Windows 2000 Prof, XP Pro or Vista, you don't need a purchased

>>> TS CAL for them at all.

>>> These clients receive a free TS CAL from the built-in pool of

>>> "Existing Windows 2000 TS CALs" on the TS Licensing Server. And

>>> that pool is unlimited, so you can never have the problem of

>>> running out of licenses.

>>>

>>> I'm not sure exactly which troubleshooting steps you have

>>> performed. Can you post a link to the page you mentioned, or

>>> detail the steps?

>>>

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> Frane <frane.borozan@gmail.com> wrote on 01 apr 2008 in

>>> microsoft.public.windows.terminal_services:

>>>

>>> > Do you have any available license for new computers that are

>>> > tryng to connect?

>>> > If not then issued licenses would automatically expire after

>>> > a random period between 52-89 days and become part of the

>>> > available license pool.

>>> > If you need immediately CALs then I would suggest you to

>>> > reactivate server.