Re: Configuring Single Termainal Services License Server for Domain
- From: "Will" <westes-usc@xxxxxxxxxxxxxx>
- Date: Tue, 18 Jul 2006 23:40:07 -0700
So this is weird: the DC is running Windows 2000 and the Windows 2003
client works fine. That seems to contradict your suggestion below.
The licensing server refuses to give the Windows 2000 client a license.
How do get access to a debug log or other information that tells me why the
license server is unable to give the client its license? Other Windows
2000 clients work.
I"ll go through the other documents this week.
--
Will
"Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:555F1438-99DA-40C2-9B32-399E256DB15D@xxxxxxxxxxxxxxxx
If you have both 2003 and 2000 TS, the TSLS must be on a 2003 server.There
are resource kit utilities to query the TSLS, i.e. lsview.exe andif
lsreport.exe. You can point the TS to the TSLS via registry edit, however
the TSLS is on a DC, it will be located automatically.http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en
http://www.sessioncomputing.com/licensing.htm
Windows Server 2003 Resource Kit Tools:
2003
How to override the license server discovery process in Windows Server
Terminal Services:
http://support.microsoft.com/?kbid=279561
Establishing Preferred Windows 2000 Terminal Services License Server:
http://support.microsoft.com/kb/q239107/
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com
.
- Follow-Ups:
- Re: Configuring Single Termainal Services License Server for Domai
- From: Patrick Rouse
- Re: Configuring Single Termainal Services License Server for Domai
- References:
- Prev by Date: Re: Always same "SessionID" with a user account
- Next by Date: Re: stop ie use
- Previous by thread: Configuring Single Termainal Services License Server for Domain
- Next by thread: Re: Configuring Single Termainal Services License Server for Domai
- Index(es):
Relevant Pages
|