Jump to content

Licensing problem...


Recommended Posts

Posted

I have a win2k terminal server that XP Pro clients connect to.

My DC is a Windows 2003 SBS & I had purchased 5 TS licenses.

I had read somewhere that XP Pro clients connecting to a Win2k TS had built

in licenses, so I really didn't need to buy the licenses.

All that aside, my current problem is that every 3 or 4 months, some of the

clients start getting the message that the connection couldn't be made

because of an error in the licensing protocol, or something like that. I

have always been able to talk the user through deleting the LICENSE000 key,

which is a labor in itself, but I would like this fixed once and for all.

Where do I start?!?!?

 

--

The intelligent man wins his battles with pointed words.

I'm sorry -- I meant sticks. Pointed sticks.

Guest Jeff Pitsch
Posted

Re: Licensing problem...

 

Check the permissions on the key to make sure the users have full control.

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

Mike wrote:

> I have a win2k terminal server that XP Pro clients connect to.

> My DC is a Windows 2003 SBS & I had purchased 5 TS licenses.

> I had read somewhere that XP Pro clients connecting to a Win2k TS had built

> in licenses, so I really didn't need to buy the licenses.

> All that aside, my current problem is that every 3 or 4 months, some of the

> clients start getting the message that the connection couldn't be made

> because of an error in the licensing protocol, or something like that. I

> have always been able to talk the user through deleting the LICENSE000 key,

> which is a labor in itself, but I would like this fixed once and for all.

> Where do I start?!?!?

>

Posted

Re: Licensing problem...

 

Permissions on the key?!?!

The labor is trying to talk someone, who acts like they have never

seen a couputer before in their life, through the process of deleting

the key!

I want to know how I can have this work right all the time!

 

 

On Oct 3, 1:52 pm, Jeff Pitsch <J...@Jeffpitschconsulting.com> wrote:

> Check the permissions on the key to make sure the users have full control.

>

> Jeff Pitsch

> Microsoft MVP - Terminal Server

> Citrix Technology Professional

> Provision Networks VIP

>

> Forums not enough?

> Get support from the experts at your businesshttp://jeffpitschconsulting.com

>

> Mike wrote:

> > I have a win2k terminal server that XP Pro clients connect to.

> > My DC is a Windows 2003 SBS & I had purchased 5 TS licenses.

> > I had read somewhere that XP Pro clients connecting to a Win2k TS had built

> > in licenses, so I really didn't need to buy the licenses.

> > All that aside, my current problem is that every 3 or 4 months, some of the

> > clients start getting the message that the connection couldn't be made

> > because of an error in the licensing protocol, or something like that. I

> > have always been able to talk the user through deleting the LICENSE000 key,

> > which is a labor in itself, but I would like this fixed once and for all.

> > Where do I start?!?!?

Guest Jeff Pitsch
Posted

Re: Licensing problem...

 

And I'm telling you how. There is a problem with Windows XP not having

the correct permissions on that particular key. Let me ask you this,

are the users admin on the boxes or normal users?

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

Mikey wrote:

> Permissions on the key?!?!

> The labor is trying to talk someone, who acts like they have never

> seen a couputer before in their life, through the process of deleting

> the key!

> I want to know how I can have this work right all the time!

>

>

> On Oct 3, 1:52 pm, Jeff Pitsch <J...@Jeffpitschconsulting.com> wrote:

>> Check the permissions on the key to make sure the users have full control.

>>

>> Jeff Pitsch

>> Microsoft MVP - Terminal Server

>> Citrix Technology Professional

>> Provision Networks VIP

>>

>> Forums not enough?

>> Get support from the experts at your businesshttp://jeffpitschconsulting.com

>>

>> Mike wrote:

>>> I have a win2k terminal server that XP Pro clients connect to.

>>> My DC is a Windows 2003 SBS & I had purchased 5 TS licenses.

>>> I had read somewhere that XP Pro clients connecting to a Win2k TS had built

>>> in licenses, so I really didn't need to buy the licenses.

>>> All that aside, my current problem is that every 3 or 4 months, some of the

>>> clients start getting the message that the connection couldn't be made

>>> because of an error in the licensing protocol, or something like that. I

>>> have always been able to talk the user through deleting the LICENSE000 key,

>>> which is a labor in itself, but I would like this fixed once and for all.

>>> Where do I start?!?!?

>

>

Posted

Re: Licensing problem...

 

They are admins.

 

On Oct 4, 11:06 am, Jeff Pitsch <J...@Jeffpitschconsulting.com> wrote:

> And I'm telling you how. There is a problem with Windows XP not having

> the correct permissions on that particular key. Let me ask you this,

> are the users admin on the boxes or normal users?

>

> Jeff Pitsch

> Microsoft MVP - Terminal Server

> Citrix Technology Professional

> Provision Networks VIP

>

> Forums not enough?

> Get support from the experts at your businesshttp://jeffpitschconsulting.com

>

> Mikey wrote:

> > Permissions on the key?!?!

> > The labor is trying to talk someone, who acts like they have never

> > seen a couputer before in their life, through the process of deleting

> > the key!

> > I want to know how I can have this work right all the time!

>

> > On Oct 3, 1:52 pm, Jeff Pitsch <J...@Jeffpitschconsulting.com> wrote:

> >> Check the permissions on the key to make sure the users have full control.

>

> >> Jeff Pitsch

> >> Microsoft MVP - Terminal Server

> >> Citrix Technology Professional

> >> Provision Networks VIP

>

> >> Forums not enough?

> >> Get support from the experts at your businesshttp://jeffpitschconsulting.com

>

> >> Mike wrote:

> >>> I have a win2k terminal server that XP Pro clients connect to.

> >>> My DC is a Windows 2003 SBS & I had purchased 5 TS licenses.

> >>> I had read somewhere that XP Pro clients connecting to a Win2k TS had built

> >>> in licenses, so I really didn't need to buy the licenses.

> >>> All that aside, my current problem is that every 3 or 4 months, some of the

> >>> clients start getting the message that the connection couldn't be made

> >>> because of an error in the licensing protocol, or something like that. I

> >>> have always been able to talk the user through deleting the LICENSE000 key,

> >>> which is a labor in itself, but I would like this fixed once and for all.

> >>> Where do I start?!?!?

Guest Vera Noest [MVP]
Posted

Re: Licensing problem...

 

Let's try to cover the basics first:

You never told us if you have a Terminal Services Licensing Server

installed and activated. That would be on your SBS2003 DC.

 

You are right that you don't have to buy and install TS CALs on the

TS Licensing Server, but you are not right in your assumption that

XP Pro clients have a built-in TS license. In stead, they get one

for free from the built-in pool of "Existing Windows 2000 Per

Device TS CALs" which is present on a TS Licensing Server. So the

TS *must* be able to connect to an activated LS.

If you have an activated LS, have you verified that the TS can

locate it?

Are there any error messages or warnings concerning licensing on

the TS?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

Mikey <texan767@hotmail.com> wrote on 05 okt 2007 in

microsoft.public.windows.terminal_services:

> They are admins.

>

> On Oct 4, 11:06 am, Jeff Pitsch <J...@Jeffpitschconsulting.com>

> wrote:

>> And I'm telling you how. There is a problem with Windows XP

>> not having the correct permissions on that particular key. Let

>> me ask you this, are the users admin on the boxes or normal

>> users?

>>

>> Jeff Pitsch

>> Microsoft MVP - Terminal Server

>> Citrix Technology Professional

>> Provision Networks VIP

>>

>> Forums not enough?

>> Get support from the experts at your

>> businesshttp://jeffpitschconsulting.com

>>

>> Mikey wrote:

>> > Permissions on the key?!?!

>> > The labor is trying to talk someone, who acts like they have

>> > never seen a couputer before in their life, through the

>> > process of deleting the key!

>> > I want to know how I can have this work right all the time!

>>

>> > On Oct 3, 1:52 pm, Jeff Pitsch

>> > <J...@Jeffpitschconsulting.com> wrote:

>> >> Check the permissions on the key to make sure the users have

>> >> full control.

>>

>> >> Jeff Pitsch

>> >> Microsoft MVP - Terminal Server

>> >> Citrix Technology Professional

>> >> Provision Networks VIP

>>

>> >> Forums not enough?

>> >> Get support from the experts at your

>> >> businesshttp://jeffpitschconsulting.com

>>

>> >> Mike wrote:

>> >>> I have a win2k terminal server that XP Pro clients connect

>> >>> to. My DC is a Windows 2003 SBS & I had purchased 5 TS

>> >>> licenses. I had read somewhere that XP Pro clients

>> >>> connecting to a Win2k TS had built in licenses, so I really

>> >>> didn't need to buy the licenses. All that aside, my current

>> >>> problem is that every 3 or 4 months, some of the clients

>> >>> start getting the message that the connection couldn't be

>> >>> made because of an error in the licensing protocol, or

>> >>> something like that. I have always been able to talk the

>> >>> user through deleting the LICENSE000 key, which is a labor

>> >>> in itself, but I would like this fixed once and for all.

>> >>> Where do I start?!?!?

Posted

Re: Licensing problem...

 

Yes, I have a licensing server installed & activated & it is my SBS2003 DC.

Event viewer on TS shows multiple instances of : Replication of license

information failed because the License Logging Service on server \\SERVER

could not be contacted.

And LSView finds it ok.

Usually it can be fixed by deleting the HardwardID & Store folders in the

registry, but why do I have this problem every 3 months, or so?

 

--

The intelligent man wins his battles with pointed words.

I'm sorry -- I meant sticks. Pointed sticks.

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

news:Xns99C0EAE925138veranoesthemutforsse@207.46.248.16...

> Let's try to cover the basics first:

> You never told us if you have a Terminal Services Licensing Server

> installed and activated. That would be on your SBS2003 DC.

>

> You are right that you don't have to buy and install TS CALs on the

> TS Licensing Server, but you are not right in your assumption that

> XP Pro clients have a built-in TS license. In stead, they get one

> for free from the built-in pool of "Existing Windows 2000 Per

> Device TS CALs" which is present on a TS Licensing Server. So the

> TS *must* be able to connect to an activated LS.

> If you have an activated LS, have you verified that the TS can

> locate it?

> Are there any error messages or warnings concerning licensing on

> the TS?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> Mikey <texan767@hotmail.com> wrote on 05 okt 2007 in

> microsoft.public.windows.terminal_services:

>

>> They are admins.

>>

>> On Oct 4, 11:06 am, Jeff Pitsch <J...@Jeffpitschconsulting.com>

>> wrote:

>>> And I'm telling you how. There is a problem with Windows XP

>>> not having the correct permissions on that particular key. Let

>>> me ask you this, are the users admin on the boxes or normal

>>> users?

>>>

>>> Jeff Pitsch

>>> Microsoft MVP - Terminal Server

>>> Citrix Technology Professional

>>> Provision Networks VIP

>>>

>>> Forums not enough?

>>> Get support from the experts at your

>>> businesshttp://jeffpitschconsulting.com

>>>

>>> Mikey wrote:

>>> > Permissions on the key?!?!

>>> > The labor is trying to talk someone, who acts like they have

>>> > never seen a couputer before in their life, through the

>>> > process of deleting the key!

>>> > I want to know how I can have this work right all the time!

>>>

>>> > On Oct 3, 1:52 pm, Jeff Pitsch

>>> > <J...@Jeffpitschconsulting.com> wrote:

>>> >> Check the permissions on the key to make sure the users have

>>> >> full control.

>>>

>>> >> Jeff Pitsch

>>> >> Microsoft MVP - Terminal Server

>>> >> Citrix Technology Professional

>>> >> Provision Networks VIP

>>>

>>> >> Forums not enough?

>>> >> Get support from the experts at your

>>> >> businesshttp://jeffpitschconsulting.com

>>>

>>> >> Mike wrote:

>>> >>> I have a win2k terminal server that XP Pro clients connect

>>> >>> to. My DC is a Windows 2003 SBS & I had purchased 5 TS

>>> >>> licenses. I had read somewhere that XP Pro clients

>>> >>> connecting to a Win2k TS had built in licenses, so I really

>>> >>> didn't need to buy the licenses. All that aside, my current

>>> >>> problem is that every 3 or 4 months, some of the clients

>>> >>> start getting the message that the connection couldn't be

>>> >>> made because of an error in the licensing protocol, or

>>> >>> something like that. I have always been able to talk the

>>> >>> user through deleting the LICENSE000 key, which is a labor

>>> >>> in itself, but I would like this fixed once and for all.

>>> >>> Where do I start?!?!?

Guest Vera Noest [MVP]
Posted

Re: Licensing problem...

 

The Event that you report means that you have a problem with server

CALs.

Verify that you have enough SBS server CALs and then stop and

disable the Licensing Logging Service on the TS (but *not* on the

SBS2003).

The Licensing Logging Service is responsible for keeping track of

server CALs, and on a Windows 2003, the recommendation is to

disable it, because it isn't accurate. This is documented here:

 

824196 - Description of the License Logging Service in Windows

Server Operating Systems

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

 

Regarding your TS Licensing problem: can you post here what exactly

you see in the TS Licensing Manager?

You should have an entry there for "Existing Windows 2000 Per

Device TS CALs", with Type: "Built-in" and Available: Unlimited.

What is the "Issued" count of them?

And do you see an entry for temporary licenses? If so, how

*exactly* are they called, and what is the Issued count?

Any other entries that you see in LS Manager?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Mike" <mikey117@hotmail.com> wrote on 06 okt 2007 in

microsoft.public.windows.terminal_services:

> Yes, I have a licensing server installed & activated & it is my

> SBS2003 DC. Event viewer on TS shows multiple instances of :

> Replication of license information failed because the License

> Logging Service on server \\SERVER could not be contacted.

> And LSView finds it ok.

> Usually it can be fixed by deleting the HardwardID & Store

> folders in the registry, but why do I have this problem every 3

> months, or so?

×
×
  • Create New...