users login

Quote:

SUMMARY
This step-by-step article describes how to use the Event Log Query Tool (Elogdmp.exe) to display event log information in Microsoft Windows 2000.

Elogdmp is available in the Windows 2000 Resource Kit. It is a command-line tool that you can use to display information from the Event Viewer logs of a local or remote Windows 2000-based computer. This tool "dumps" the contents of the log in comma-delimited format to the screen or to a file. You can then search the output to find and to view the information that you want. The information that Elogdmp displays include the following:
Date
Time
Source
Type
Category
Event ID
User
Computer
Any user on the network can use Elogdmp to view the contents of the Application log on any remote computer on the network. To view the contents of the System or Security log on a remote computer, you must be a member of the Domain Administrators or Administrators group on that computer.

back to the top
Overview of Elogdmp
Elogdmp uses the following syntax:
elogdmp ComputerName EventLog

You can use the following parameters with Elogdmp:
ComputerName: Use this parameter to specify the name of the computer whose event logs you want to query.
EventLog: Use this parameter to specify the event log that you want to display, where EventLog is Application, Security, System, DNS Server, Directory Service, or File Replication Service.

NOTE: The DNS Server log is available only on DNS servers, and the Directory Service and File Replication Service logs are available only on domain controllers.
back to the top
Examples
To display the contents of the Application log on a computer named Server1, type the following line at the command prompt, and then press ENTER:
elogdmp server1 application

NOTE: If the name of the log that you want to view contains a space, enclose the name of the log with quotation marks ("").

The contents of the Application log of Server1 are displayed in comma-delimited format in the Command Prompt window.
To display the contents of the DNS Server log on a computer named Server2 and to redirect the output to a file named Dnslog.txt, in the E:\Logs folder, type the following line at the command prompt, and then press ENTER:
elogdmp server2 DNS Server > e:\logs\dnslog.txt

NOTE: If the name of the log that you want to view contains a space, enclose the name of the log with quotation marks ("").

The contents of the DNS Server log of Server2 are written to the E:\Logs\Dnslog.txt file in comma-delimited format.
back to the top
REFERENCES
For additional information about how to view and to manage logs in Event Viewer, click the article numbers below to view the articles in the Microsoft Knowledge Base:
302542 Diagnose System Problems with Event Viewer in Microsoft Windows 2000

315417 HOW TO: Move Event Viewer Log Files to Another Location

For additional information about how to use the Event Query Script Tool (Eventquery.pl) to display events from Event Viewer logs, click the article number below to view the article in the Microsoft Knowledge Base:
317381 HOW TO: Use the Event Query Script (Eventquery.pl) Tool in Microsoft Windows 2000

For additional information about how to use the Event Logging Utility (Logevent.exe) to create and to log custom events, click the article number below to view the article in the Microsoft Knowledge Base:
315410 HOW TO: Create and Log Custom Events in Event Viewer by Using the Event Logging Utility (Logevent.exe)

For additional information about how to use the Event Log Management Script Tool (Eventlog.pl) to manage event logs , click the following article number to view the article in the Microsoft Knowledge Base:
318763 HOW TO: Use the Event Log Management Script Tool (Eventlog.pl) to Manage Event Logs in Windows 2000

For more information about the Windows 2000 Resource Kit, visit the following Microsoft Web site:
http://www.microsoft.com/windows2000...t.asp#section1

back to the top
Last Reviewed: 1/13/2003
Keywords: kbhowto kbHOWTOmaster KB323006
http://support.microsoft.com/default...en-us%3B323006

sorry that it's for 2000, i hope too much didn't change between 2000 and XP... couldn't find this article for XP... anyway- i hope this helps!

-take it easy :)