Re: Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
- From: "Dave Morschhauser" <someone@xxxxxxxxxxxxx>
- Date: Thu, 6 Oct 2005 09:52:29 -0400
Vera --
Thanks again.
After adding the "TS-Enterprise-LicenseServer" Active Directory object as
described in >> http://support.microsoft.com/?kbid=895151, the problem
notifications have gone away, although the TS configuration still does not
automatically identify the license server.
Dave.
"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns96E6E9E213D13veranoesthemutforsse@xxxxxxxxxxxxxxxx
> You can delete the locally stored license from a client. But this
> will mean that you will "loose" 1 license, at least for a period of
> max. 89 days. So don't do this if you don't have an extra license
> available.
>
> 187614 - Removing Terminal Server Licenses from an RDP Client
> http://support.microsoft.com/?kbid=187614
>
> You can also run the TS Client License Dump utility from the
> Resource Kit on your clients. It will show you the details of the
> locally stored license (which server issued the license, which type
> it is, etc). Run "tsctst.exe /a"
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Dave Morschhauser" <someone@xxxxxxxxxxxxx> wrote on 05 okt 2005
> in microsoft.public.windows.terminal_services:
>
> >
> > Vera --
> >
> > Thanks for the information you sent. I am trying the workaround
> > indicated in the first link, and should know today, after
> > replication, if that has solved the problem.
> >
> > I am unable to try the testing you suggest as I do not have any
> > unlicensed clients left to test the operation per your
> > description - Is there a way to make one of my existing clients
> > "new" again, so that the LS will treat it as if it had never
> > requested a license before?
> >
> > Thanks for your help. I'll let you know how the current
> > workaround attempt works out.
> >
> > Dave.
> >
> > "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> > in message
> > news:Xns96E5DF85B3C78veranoesthemutforsse@xxxxxxxxxxxxxxxx
> >> I would definitively hardcode the name of the LS into the
> >> registry of the TS, because of this:
> >>
> >> 895151 - Windows Server 2003-based or Windows 2000-based
> >> terminal servers do not automatically discover a license server
> >> that is designated as an enterprise license server
> >> http://support.microsoft.com/?kbid=895151
> >>
> >> So you *only* get the warning in the System tray on the TS, but
> >> there is *no* EventID 1009 on the TS?
> >> Might be a "false alarm", similar to this one:
> >>
> >> 831716 - You receive a "No Terminal Services License server was
> >> found on the network" error message when you run the Manage
> >> Your Server Wizard on a Windows Server 2003-based computer
> >> http://support.microsoft.com/?kbid=831716
> >>
> >> Have you tested with a client which has never connected before?
> >> Try connecting twice (on first connection, all clients receive
> >> a temporary license, on second connection you get a permanent
> >> license), and monitor the Licensing Manager on the LS.
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> "Dave Morschhauser" <someone@xxxxxxxxxxxxx> wrote on 04 okt
> >> 2005 in microsoft.public.windows.terminal_services:
> >>
> >> > I am running Win2K3 on two machines at two different
> >> > locations. The two locations are connected by an ISDN link
> >> > and by a VPN over DSL and Cable Modem. Both connections are
> >> > available, and appear to be working (ping, traceroute, the
> >> > RDP connections themselves). One machine is running SP-1 the
> >> > other has not been upgraded (yet).
> >> >
> >> > Each Win2K3 machine is running TS, and one of them is running
> >> > TSLS. The second one has been operational for about 90 days.
> >> > Within the last week, the second TS has been complaining that
> >> > there is no TSLS, and that the grace period is going to
> >> > expire. The "complaint" is in the form of a balloon in the
> >> > SysTray. Checking with the TSLS Management Console, there are
> >> > several Permanent Licenses that have been issued to clients
> >> > that would have no reason to connect to the first machine, so
> >> > it appears that the TSLS is correctly providing licenses for
> >> > the second TS
> >> >
> >> > On the second TS, I have run TS Config, and have tried both
> >> > Automatic Discovery, and a hardwired TSLS. In automatic
> >> > discovery, the TSLS server name is reported under "In
> >> > Enterprise role". If I hardwire a TSLS, and press Check
> >> > Names, it reports back that "The specified LS are valid
> >> > Win2K3 TSLS's" The complaints persist regardless of
> >> > automatic/hardwired mode.
> >> >
> >> > From the second TS, I have run lsview.exe, and it reports
> >> > the TSLS as type "Enterprise", with the time off by a few
> >> > minutes.
> >> >
> >> > From the second TS, I have run lsreport.exe, and it reports
> >> > the same permanent and temporary licenses as are listed in
> >> > the TSLS Management Console on the TSLS itself.
> >> >
> >> > The Event Log does not have any TSLS error messages, and the
> >> > only TS error or warning messages are related to printers.
> >> >
> >> > Any ideas on what's wrong, and is TS about to stop working?
> >> >
> >> > Dave Morschhauser
> >> > Mystic Valley Communications.
.
- References:
- Prev by Date: Re: Supplemental
- Next by Date: Re: TSWEB and resolution question
- Previous by thread: Re: Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
- Next by thread: How to deny logon for already logged on user
- Index(es):
Relevant Pages
|
