
132 MetaFrame Solutions Guide
Event log Description Event selection process
System Errors, warnings, or information
generated by the MetaFrame
server.
Selection of events is preset by the
operating system.
Security Valid and invalid logon attempts
and events related to resource
use such as creating, opening, or
deleting files or other objects.
Control of security event auditing is
set in the Local Policies folder in the
Local Security Policy MMC.
Control of file and directory access
audits is set through Windows NT
Explorer.
Application Errors, warnings, or information
generated by application
software, such as an electronic
mail or database program.
Application developers decide which
events to monitor.
System and application logs are available to be viewed by all users, while security
logs are accessible only to system administrators. With appropriate administrative
rights, you can also view logs on other computers.
Using Event Logs to Troubleshoot
Each entry in an event log can include the following information:
K
Date
K
Time
K
Source
K
Type
K
Category
K
Event ID
K
User
K
Computer Name
In addition, most events generate a text description and sometimes binary data,
which are available by double-clicking a single entry. The binary data is generated
by the application that was the source of the event record. Because the data
appears in hexadecimal format, interpreting it may require consulting someone
who is familiar with the source application. Binary data is displayed in words or in
bytes.
Careful monitoring of event logs can help you predict and identify the sources of
system problems. For example, if log warnings show that a disk driver can only
read or write to a sector after several retries, it indicates that the sector will
eventually become corrupt. Log files can also confirm problems with application
Comentarios a estos manuales