Logs Overview

Microsoft® Windows® 2000 Scripting Guide

microsoft windows 2000 scripting guide

« Previous | Next »   

Financial institutions typically keep detailed records of each transaction they undertake. This record keeping serves at least two purposes. First, it allows the institutions to know, without question, where the money has been and where it is going; if a problem occurs, troubleshooters can go through archived records and retrace every transaction that has taken place in the past few hours, the past few days, and even the past few months. Second, by routinely analyzing these records, institutions are often alerted to trouble before it occurs. Many instances of fraud or embezzlement have been prevented because auditors noticed patterns of activity that were out of the ordinary and were able to put a stop to abuses before it was too late.

The Windows operating system also keeps detailed records of the activity that takes place on a computer. These records, typically stored in the event logs, provide system administrators with the same capabilities financial records provide financial institutions: The event logs help you trace the activity that has taken place on a computer and help you identify potential problems before it is too late. Few activities are as useful to a system administrator as a regular audit and analysis of the event logs for a computer.

Despite the acknowledged value of event logs, however, few system administrators routinely audit and analyze these logs. This is largely because the primary tool provided for working with event logs Event Viewer limits you to working with a single event log from a single computer at a time. Although it is recommended that you periodically analyze all the event logs for all your domain controllers, in practice this is tedious and time-consuming using Event Viewer. As a result, administrators rarely undertake this kind of analysis except in organizations that have gone to the trouble and expense of purchasing and installing third-party tools for working with event logs.

Fortunately, scripting provides you with the same capabilities that these third-party tools have.


send us your feedback Send us your feedback « Previous | Next »   


Microsoft Windows 2000 Scripting Guide(c) Automating System Administration 2003
Microsoft Windows 2000 Scripting Guide(c) Automating System Administration 2003
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 635

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net