Re: License Server Woes
- From: "James" <James@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 14 Jul 2005 12:51:04 -0700
So if I understand this correctly and if it would apply to a win2k domain,
you only need one lserver in the domain and all terminal servers do not need
to be activated, only the one holding all of the licenses? RIght?
"Vera Noest [MVP]" wrote:
> Good heavens! A Licensing Server on all 10 Terminal Servers? That's
> what I call redundancy :-)
> That could well be (part of) the problem, but only if some of them
> are also activated. Anyhow, I would uninstall the TS Licensing
> Server from all servers, except the server where the TS CALs are
> installed.
> (You can have a second LS for redundancy, but then you need to
> activate it and install part of your TS CALs on it as well.)
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> ___ please respond in newsgroup, NOT by private email ___
>
> Brendan Kwolek <someguy@xxxxxxxxxx> wrote on 01 jun 2005 in
> microsoft.public.windows.terminal_services:
>
> > Vera;
> >
> > Thanks for the response, I will go ahead and remove that
> > key...turns out we only had it on one or two of the servers as a
> > means of testing the resolution of this problem a year or so
> > back (oh yeah, it's been going on that long!)
> >
> > The other thing that I just noticed (can you tell I don't
> > normally admin these boxes) is that the Terminal Services
> > Licensing service is running on each and every one of the
> > servers....is this necessary, or could this potentially be what
> > is causing the problem (ie. Server requesting license from LS
> > and it finds one locally that isn't activated and has no
> > licenses installed on it)?
> >
> > I've not read anything that suggests you need to have this
> > running on EACH server that runs terminal services in an
> > enterprise, so I'm curious if this might be the culprit.
> >
> > Your thoughts would be appreciated
> >
> > Thanks
> >
> > B
> >
> > Vera Noest [MVP] wrote:
> >> Your accurate description of the problem makes it clear that
> >> the problem is the communication between the Terminal Servers
> >> and the Licensing Server:
> >>
> >> * on first connection, every client always receives a temporary
> >> license. The Terminal Server will try to issue a permanent
> >> license on the second connection. If that doesn't happen, the
> >> temporary license will work for 90 days.
> >> * when the temporary license expires and the Terminal Server is
> >> not able to retrieve a permanent license from the LS, it
> >> refuses connection. This is what your users now experience
> >> * when clients connect to the TS that is also the LS, they
> >> obviously *do* receive a permanent license. With that stored
> >> locally on the client, they are again able to connect to *all*
> >> Terminal Servers, until the permanent license expires (after
> >> 52-89 days). Then the whole process starts over again.
> >>
> >> There must be something wrong with the license server discovery
> >> process. I expect that the EventLog on your Terminal Servers
> >> will confirm this (EventID 1010 - "cannot locate LS").
> >> The fact that this domain is an NT4.0 domain only means that
> >> you can run the LS on a member server (which wouldn't be
> >> possible in a W2K or 2003 domain). It does not interfere with
> >> the automatic discovery process, which is done by broadcasting
> >> on a mailslot.
> >>
> >> So my advice is to delete the registry entry from all of your
> >> Terminal Servers, and rely on the automatic license server
> >> discovery. Alternatively, doublecheck the registry entry you
> >> made, and check your NetBIOS name resolution.
> >>
> >> 232520 - Description of Terminal Services License Server
> >> Discovery http://support.microsoft.com/?kbid=232520
> >>
> >> 239107 - Establishing Preferred Windows 2000 Terminal Services
> >> License Server
> >> http://support.microsoft.com/?kbid=239107
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> http://hem.fyristorg.com/vera/IT
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> Brendan Kwolek <bkwolek@xxxxxxxxx> wrote on 31 maj 2005 in
> >> microsoft.public.windows.terminal_services:
> >>
> >>
> >>>Good morning;
> >>>
> >>>We have a small Citrix farm (approx. 250 users spread across 10
> >>>servers) and seem to be having a problem with license
> >>>assignment, and temporary license expiration.
> >>>
> >>>The first time a user connects from a Citrix client
> >>>workstation, or a thin-client terminal device, they receive a
> >>>license, and can go about their business happily using their
> >>>device for a while.
> >>>
> >>>Eventually down the road, they start to receive notices that
> >>>their license will expire shortly.
> >>>
> >>>Once their license DOES expire, they are unable to connect to
> >>>any of the Terminal servers in the domain EXCEPT the one
> >>>license server we have (10 Terminal Servers running Windows
> >>>2000 SP4, one of which is an activated Terminal Services
> >>>Licensing Server with approx. 350 licenses installed)
> >>>
> >>>We get a variety of messages depending on which client we use
> >>>(Citrix usually says network connectivity, same with RDP client
> >>>on XP), however once you connect to the terminal services on
> >>>the licensing server, you can then go back and reconnect to ANY
> >>>of the other services without an issue.
> >>>
> >>>To me, this suggests there is a problem with license assignment
> >>>across the servers. We have set REG values so that each server
> >>>knows which server is the licensing server in the domain, but
> >>>this has not solved the issue.
> >>>
> >>>(Dunno if it matters, but this is an NT4 domain)
> >>>
> >>>If anyone has any input, it would be very much appreciated!
> >>>We have tried deactivating and reintalling and reacivating our
> >>>licensing server and TSCALS, to no avail.
> >>>
> >>>Citrix tech support insists that this is not a licensing issue,
> >>>but a technical issue, and wants me to open a support contact
> >>>to fix it (which I'd very much like to avoid thanks :))
> >>>
> >>>Appreciate any insight or input from someone who has
> >>>experienced a similar problem
> >>>
> >>>Thanks
> >>>
> >>>Brendan
>
.
- Follow-Ups:
- Re: License Server Woes
- From: Vera Noest [MVP]
- Re: License Server Woes
- Prev by Date: Re: SLOW
- Next by Date: Re: how to upgrade remote desktop client
- Previous by thread: Licenses not being renewed
- Next by thread: Re: License Server Woes
- Index(es):
Relevant Pages
|
