TS Licensing Server mishap

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We're just starting down the Terminal Services road, and have one Terminal
Server 2003 set up, but with minimal use so far. I installed Licensing Server
on a member server (not a DC) in the domain. This is our file server and is
also Win 2003. I activated it but haven't received the license numbers yet,
so left it as is. People started complaing that the file server was almost
usless at times shortly after that. About every 12-15 minutes it would be
virutally useless for awhile, then come out of it until the next 12-15
minutes. It happened all day, and I finally uninstalled it this morning. I
thought Licensing Server was low impact.

1) Does Licensing Server need to be on a Domain Controller?
2) Did the lack of licensing numbers cause this?
3) Is there any reason to or not to put the Licensing Server on the Termnal
Server itself? (I thought I read it isn't a good idea to.) There will be
another T Server sometime soon.

Thanks,
Darrell
 
A 2003 TS Licensing server can run on a member server, doesn't
need to run on a DC. So you can put it on the TS itself without
problems. You might have to hardcode the address or IPnumber of
the LS into the rgistry of every TS:

279561 - How to Override the License Server Discovery Process in
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561

The performance problems that you saw are not normal behaviour!
And the fact that you were running on temporary licenses should
not make a difference either.
In a way, it's a pitty that you uninstalled the LS (but I
understand that you had to take action to solve the immediate
problem).
It would have been interesting to monitor the system during these
periods of unresponsiveness, to see what caused it.
Is there anything in the EventLog that can shed some light on this
problem?
 
Thanks, Vera.

The only things noetworthy in Event Viewer were:
1) ID 1030 Windows cannot query for the list of Group Policy objects. Check
event log for possible messages previously logged...

2) ID 1015 TraceLevel parameter not located in registry. Default trace level
uses is 32.

Do thses amke any sense to you, and are they related to my performace problem?

Thanks.
 
EventID 1015 from EvntAgnt doesn't seem to have anything to do
with this issue. But you migth want to fix it anyway, I at least
like to have a clean EventLog. Check here for tips:

http://www.eventid.net/display.asp?eventid=1015&eventno=2612
&source=EvntAgnt&phase=1

EventID 1030 from SceCli sounds more promising, but there should
be a previous event as well, with more explanation.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Back
Top