An event is a specific occurrence of an activity of the WS2003 operating system, an installed component, or an application. Events are generated automatically and are recorded in event logs, which can then be viewed and analyzed using the Event Viewer console in Administrative Tools. The key is to use Event Viewer to regularly monitor the event logs on your servers and deal with any situations that arise. You can use Event Viewer to search for or filter particular types of events if the log becomes excessively large. It’s also important to configure the size limit and retention period for event logs as soon as you set up a new server. Logs can wrap (newer events start overwriting older ones) once they reach a certain size, but this may cause important information to be lost. It’s better to configure a decent chunk of disk space for each log and then archive and clear logs regularly, so that your information is saved but disk space is freed up.
Three event logs are present on every WS2003 computer:
This log contains events generated by activities of the operating system. Examples of system events include the activities of services such as the Net-Logon service, failures of drivers to initialize properly, changes in the role of a server from member server to domain controller, and so on. System events come in three flavors:
These events simply describe normal activites that have occurred, such as the successful ...