Terminal Services License Server Found and Not found at the same time

[Guest NikrusKram@gmail.com]

I've recently implemented a Terminal Server and Terminal Services

License Server in our environment. Both boxes are Windows Server 2003.

I've activated the license server successfully, and installed per user

CAL tokens on it. I set the Terminal Server to per user licensing, and

it can successfully see the license server. When Logging into the

Terminal Server, the Manage Your Server Window says "A Terminal

Services License Server has been found on the network." However, a

balloon pops up in the system tray that says "Cannot find windows 2003

terminal server license server." And tells me how many days I have

remaining on my grace period.

 

This seems rather contradictory to me, and I would hope that since it

claims to see the LS, it won't be an issue when the grace period ends.

However, I'm assuming that the LS failure will take precedence over

the LS success. Any guidance would be greatly appreciated.

 

I have run through a bunch of troubleshooting techniques, reinstalled

the LS on a different box, tried both manual and automatic discovery,

added the LS to the sites schema, etc etc etc. But the contradiction

remains, no matter what I do.

 

I have 41 days left! Please Help!!

[Guest Vera Noest [MVP]]

Re: Terminal Services License Server Found and Not found at the same time

 

Check if this solves the problem:

 

885013 - Event ID 1009 is logged on a Terminal Server License

server in a Windows Server 2003-based domain

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

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

NikrusKram@gmail.com wrote on 07 dec 2007 in

microsoft.public.windows.terminal_services:

> I've recently implemented a Terminal Server and Terminal

> Services License Server in our environment. Both boxes are

> Windows Server 2003. I've activated the license server

> successfully, and installed per user CAL tokens on it. I set the

> Terminal Server to per user licensing, and it can successfully

> see the license server. When Logging into the Terminal Server,

> the Manage Your Server Window says "A Terminal Services License

> Server has been found on the network." However, a balloon pops

> up in the system tray that says "Cannot find windows 2003

> terminal server license server." And tells me how many days I

> have remaining on my grace period.

>

> This seems rather contradictory to me, and I would hope that

> since it claims to see the LS, it won't be an issue when the

> grace period ends. However, I'm assuming that the LS failure

> will take precedence over the LS success. Any guidance would be

> greatly appreciated.

>

> I have run through a bunch of troubleshooting techniques,

> reinstalled the LS on a different box, tried both manual and

> automatic discovery, added the LS to the sites schema, etc etc

> etc. But the contradiction remains, no matter what I do.

>

> I have 41 days left! Please Help!!

[Guest NikrusKram@gmail.com]

Re: Terminal Services License Server Found and Not found at the sametime

 

Re: Terminal Services License Server Found and Not found at the sametime

 

Vera,

 

Your help is greatly appreciated! Unfortunately, the steps in the

document did not help to get rid of the balloon error claiming that no

LS has been found. I am not getting any error in the event log

pertaining to this, however that may be due to the fact that I still

have 37 days remaining on my grace period.

 

I have a feeling that it may continue functioning properly once my

grace period expires, because other parts of the TS can see the LS,

but because per user licenses are not managed, maybe this balloon is

just unavoidable?

 

I'd just rather not gamble with it! Any other advice would be much

appreciated...

 

Thanks

 

On Dec 7, 5:13 pm, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> Check if this solves the problem:

>

> 885013 - Event ID 1009 is logged on a Terminal Server License

> server in a Windows Server 2003-based domainhttp://support.microsoft.com/?kbid=885013

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> NikrusK...@gmail.com wrote on 07 dec 2007 in

> microsoft.public.windows.terminal_services:

>

> > I've recently implemented a Terminal Server and Terminal

> > Services License Server in our environment. Both boxes are

> > Windows Server 2003. I've activated the license server

> > successfully, and installed per user CAL tokens on it. I set the

> > Terminal Server to per user licensing, and it can successfully

> > see the license server. When Logging into the Terminal Server,

> > the Manage Your Server Window says "A Terminal Services License

> > Server has been found on the network." However, a balloon pops

> > up in the system tray that says "Cannot find windows 2003

> > terminal server license server." And tells me how many days I

> > have remaining on my grace period.

>

> > This seems rather contradictory to me, and I would hope that

> > since it claims to see the LS, it won't be an issue when the

> > grace period ends. However, I'm assuming that the LS failure

> > will take precedence over the LS success. Any guidance would be

> > greatly appreciated.

>

> > I have run through a bunch of troubleshooting techniques,

> > reinstalled the LS on a different box, tried both manual and

> > automatic discovery, added the LS to the sites schema, etc etc

> > etc. But the contradiction remains, no matter what I do.

>

> > I have 41 days left! Please Help!!

[Guest NikrusKram@gmail.com]

Re: Terminal Services License Server Found and Not found at the sametime

 

Re: Terminal Services License Server Found and Not found at the sametime

 

To follow up...

 

I switched over to per device licensing, and have eliminated the

issue.

 

Lesson learned: Per user licensing doesn't really work.

 

On Dec 11, 2:55 pm, NikrusK...@gmail.com wrote:

> Vera,

>

> Your help is greatly appreciated! Unfortunately, the steps in the

> document did not help to get rid of the balloon error claiming that no

> LS has been found. I am not getting any error in the event log

> pertaining to this, however that may be due to the fact that I still

> have 37 days remaining on my grace period.

>

> I have a feeling that it may continue functioning properly once my

> grace period expires, because other parts of the TS can see the LS,

> but because per user licenses are not managed, maybe this balloon is

> just unavoidable?

>

> I'd just rather not gamble with it! Any other advice would be much

> appreciated...

>

> Thanks

>

> On Dec 7, 5:13 pm, "Vera Noest [MVP]" <vera.no...@remove-

>

> this.hem.utfors.se> wrote:

> > Check if this solves the problem:

>

> > 885013 - Event ID 1009 is logged on a Terminal Server License

> > server in a Windows Server 2003-based domainhttp://support.microsoft.com/?kbid=885013

> > _________________________________________________________

> > Vera Noest

> > MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> > NikrusK...@gmail.com wrote on 07 dec 2007 in

> > microsoft.public.windows.terminal_services:

>

> > > I've recently implemented a Terminal Server and Terminal

> > > Services License Server in our environment. Both boxes are

> > > Windows Server 2003. I've activated the license server

> > > successfully, and installed per user CAL tokens on it. I set the

> > > Terminal Server to per user licensing, and it can successfully

> > > see the license server. When Logging into the Terminal Server,

> > > the Manage Your Server Window says "A Terminal Services License

> > > Server has been found on the network." However, a balloon pops

> > > up in the system tray that says "Cannot find windows 2003

> > > terminal server license server." And tells me how many days I

> > > have remaining on my grace period.

>

> > > This seems rather contradictory to me, and I would hope that

> > > since it claims to see the LS, it won't be an issue when the

> > > grace period ends. However, I'm assuming that the LS failure

> > > will take precedence over the LS success. Any guidance would be

> > > greatly appreciated.

>

> > > I have run through a bunch of troubleshooting techniques,

> > > reinstalled the LS on a different box, tried both manual and

> > > automatic discovery, added the LS to the sites schema, etc etc

> > > etc. But the contradiction remains, no matter what I do.

>

> > > I have 41 days left! Please Help!!

[Guest Vera Noest [MVP]]

Re: Terminal Services License Server Found and Not found at the same time

 

Re: Terminal Services License Server Found and Not found at the same time

 

No, the fact that you are using the Per user licensing mode

shouldn't cause the contradiction.

And you should *not* be in the grace period anymore, that is

supposed to end when the TS discovers an LS!

Details here:

 

813052 - Maximizing the Windows Server 2003 Terminal Services

Evaluation Period

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

 

I *think* that the problem is only with the warning and countdown

procedure, and then it should be harmless, but I wouldn't feel

completely comfortable in your situation.

 

The only thing that I can think of to do is to temporarily change

your TS to the Per device licensing mode, to see what happens

(preferably during off hours :-).

If you are still able to connect, and the LS issues a temporary TS

CAL for your workstation, then you know for sure that the grace

period is over and all is well, and you can change back to Per user

licensing mode.

But if you are able to connect and the LS does *not* issue a

temporary license, it means that your TS is still in the grace

period, and then I would call MS Support.

Likewise if you cannot connect at all, meaning that the grace

period is over, but the TS can't locate the LS for a temporary Per

Device TS CAL.

In all the tests above, be sure to closely monitor the LS, the

EventLog on both LS and TS for any info, and run lsview from the

Resource Kit (from the TS), to check if the TS sees the LS.

 

If you want to be 100% secure, you should call MS Support.

If you decide not to call them, keep your fingers crossed :-)

 

I'd appreciate it if you could follow-up here when you know how

things developed after 37 days.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

NikrusKram@gmail.com wrote on 11 dec 2007 in

microsoft.public.windows.terminal_services:

> Vera,

>

> Your help is greatly appreciated! Unfortunately, the steps in

> the document did not help to get rid of the balloon error

> claiming that no LS has been found. I am not getting any error

> in the event log pertaining to this, however that may be due to

> the fact that I still have 37 days remaining on my grace period.

>

> I have a feeling that it may continue functioning properly once

> my grace period expires, because other parts of the TS can see

> the LS, but because per user licenses are not managed, maybe

> this balloon is just unavoidable?

>

> I'd just rather not gamble with it! Any other advice would be

> much appreciated...

>

> Thanks

>

> On Dec 7, 5:13 pm, "Vera Noest [MVP]" <vera.no...@remove-

> this.hem.utfors.se> wrote:

>> Check if this solves the problem:

>>

>> 885013 - Event ID 1009 is logged on a Terminal Server License

>> server in a Windows Server 2003-based domain

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

>> _________________________________________________________

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

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

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

>>

>> NikrusK...@gmail.com wrote on 07 dec 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I've recently implemented a Terminal Server and Terminal

>> > Services License Server in our environment. Both boxes are

>> > Windows Server 2003. I've activated the license server

>> > successfully, and installed per user CAL tokens on it. I set

>> > the Terminal Server to per user licensing, and it can

>> > successfully see the license server. When Logging into the

>> > Terminal Server, the Manage Your Server Window says "A

>> > Terminal Services License Server has been found on the

>> > network." However, a balloon pops up in the system tray that

>> > says "Cannot find windows 2003 terminal server license

>> > server." And tells me how many days I have remaining on my

>> > grace period.

>>

>> > This seems rather contradictory to me, and I would hope that

>> > since it claims to see the LS, it won't be an issue when the

>> > grace period ends. However, I'm assuming that the LS failure

>> > will take precedence over the LS success. Any guidance would

>> > be greatly appreciated.

>>

>> > I have run through a bunch of troubleshooting techniques,

>> > reinstalled the LS on a different box, tried both manual and

>> > automatic discovery, added the LS to the sites schema, etc

>> > etc etc. But the contradiction remains, no matter what I do.

>>

>> > I have 41 days left! Please Help!!

[Guest Vera Noest [MVP]]

Re: Terminal Services License Server Found and Not found at the same time

 

Re: Terminal Services License Server Found and Not found at the same time

 

And afterwards changed back to Per user, I assume? Otherwise, you

will be running on temporary Per Device TS CALs, which will expire

in 90 days.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

NikrusKram@gmail.com wrote on 11 dec 2007 in

microsoft.public.windows.terminal_services:

> To follow up...

>

> I switched over to per device licensing, and have eliminated the

> issue.

>

> Lesson learned: Per user licensing doesn't really work.

>

> On Dec 11, 2:55 pm, NikrusK...@gmail.com wrote:

>> Vera,

>>

>> Your help is greatly appreciated! Unfortunately, the steps in

>> the document did not help to get rid of the balloon error

>> claiming that no LS has been found. I am not getting any error

>> in the event log pertaining to this, however that may be due to

>> the fact that I still have 37 days remaining on my grace

>> period.

>>

>> I have a feeling that it may continue functioning properly once

>> my grace period expires, because other parts of the TS can see

>> the LS, but because per user licenses are not managed, maybe

>> this balloon is just unavoidable?

>>

>> I'd just rather not gamble with it! Any other advice would be

>> much appreciated...

>>

>> Thanks

>>

>> On Dec 7, 5:13 pm, "Vera Noest [MVP]" <vera.no...@remove-

>>

>> this.hem.utfors.se> wrote:

>> > Check if this solves the problem:

>>

>> > 885013 - Event ID 1009 is logged on a Terminal Server License

>> > server in a Windows Server 2003-based

>> > domainhttp://support.microsoft.com/?kbid=885013

>> > _________________________________________________________

>> > Vera Noest

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

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

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

>>

>> > NikrusK...@gmail.com wrote on 07 dec 2007 in

>> > microsoft.public.windows.terminal_services:

>>

>> > > I've recently implemented a Terminal Server and Terminal

>> > > Services License Server in our environment. Both boxes are

>> > > Windows Server 2003. I've activated the license server

>> > > successfully, and installed per user CAL tokens on it. I

>> > > set the Terminal Server to per user licensing, and it can

>> > > successfully see the license server. When Logging into the

>> > > Terminal Server, the Manage Your Server Window says "A

>> > > Terminal Services License Server has been found on the

>> > > network." However, a balloon pops up in the system tray

>> > > that says "Cannot find windows 2003 terminal server license

>> > > server." And tells me how many days I have remaining on my

>> > > grace period.

>>

>> > > This seems rather contradictory to me, and I would hope

>> > > that since it claims to see the LS, it won't be an issue

>> > > when the grace period ends. However, I'm assuming that the

>> > > LS failure will take precedence over the LS success. Any

>> > > guidance would be greatly appreciated.

>>

>> > > I have run through a bunch of troubleshooting techniques,

>> > > reinstalled the LS on a different box, tried both manual

>> > > and automatic discovery, added the LS to the sites schema,

>> > > etc etc etc. But the contradiction remains, no matter what

>> > > I do.

>>

>> > > I have 41 days left! Please Help!!