what the is name and location of the log file for windows 2000 terminal server?

---

Clarification of Question by netserve-ga on 16 Mar 2006 18:23 PST

I'm not referring to the event viewer security log. I'm referring to a
logfile that keeps track of users that have accessed the server and it
usually has info like: connecting userID, IP address, time of
connection and time of logoff.
Again, I'm not referring to event viewer security listing.

I can find this out for you

Hi,

I don't believe that Windows Terminal Server does have a log file..
Citrix has the Resource Manager for this purpose only.

If there are any logfiles, i would guess it would be placed in the
c:\Windows\system32\logfiles directory, but i guess that's a long
shot..

If you would like to know when a user logged in, you will need to use
auditing on logon sessions and try to find a program that can search
through your event viewer for you (and i've seen your remark that you
don't want this, still my opnion is that this is the only way)

I will research this further for you

How to turn on the Terminal Services Session Directory logging service
View products that this article applies to.
Article ID : 327508 
Last Review : March 3, 2006 
Revision : 7.0 
This article was previously published under Q327508
Important This article contains information about how to modify the
registry. Make sure to back up the registry before you modify it. Make
sure that you know how to restore the registry if a problem occurs.
For more information about how to back up, restore, and modify the
registry, click the following article number to view the article in
the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the
Microsoft Windows registry
SUMMARY
To troubleshoot Session Directory for Terminal Services servers, you
can use the Terminal Services Session Directory logging feature. This
article describes how to turn on this feature.
MORE INFORMATION
Warning Serious problems might occur if you modify the registry
incorrectly by using Registry Editor or by using another method. These
problems might require that you reinstall your operating system.
Microsoft cannot guarantee that these problems can be solved. Modify
the registry at your own risk.1. Stop the Terminal Services Session
Directory service.
2. In the registry, locate the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tssdis\Parameters  
3. If the Parameters key does not exist, create it. 
4. Add the following DWORD value:
TraceOutputMode 
5. Select the option you want: ? 0 (no output) 
? 1 (output to debugger) 
? 3 (output to log file) 
 
6. Start the Terminal Services Session Directory service. If you
selected option 3 in step 5, Terminal Service Session Directory places
the output in a log file that is named Tssdis.log in the System32
folder.
The Terminal Services Session directory log file contains the
following entries: ? Session Directory service started
? Session Directory service stopped 
? Machine joins session directory 
? Machine leaves session directory 
? User logs in 
? User disconnects 
? User reconnects 
? User logs out 
? Session Directory-related event log messages. 
Important If you stop and then restart the Terminal Services Session
Directory service, you clear all Terminal Services Session Directory
data. Do this only if it is not a problem to do so.