Logo ADS-Training Home   All Libraries and Lists   Site Management   Create (reserved)   Site Help   
Icon
ADS-Training InfoCenter
Knowledge Base and Tips: How to configure Active Directory diagnostic...
   
New New Item
|
Edit Edit Item
|
Delete Delete Item
|
Alert Me
|
Go Back to List
Title:
How to configure Active Directory diagnostic event logging in Windows Server
Body:
This step-by-step article describes how to configure Active Directory diagnostic event logging in Microsoft Windows 2000 and Microsoft Windows Server 2003.
 
Active Directory records events to the Directory Services log of Event Viewer. You can use the information that is collected in the log to help you diagnose and resolve possible problems or monitor the activity of Active Directory-related events on your server.
 
By default, Active Directory records only critical events and error events in the Directory Service log. To configure Active Directory to record other events, you must increase the logging level by editing the registry.
 
Active Directory Diagnostic Event Logging
The registry entries that manage diagnostic logging for Active Directory are stored in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
Each of the following REG_DWORD values under the Diagnostics subkey represent a type of event that can be written to the event log:

1 Knowledge Consistency Checker (KCC)
2 Security Events
3 ExDS Interface Events
4 MAPI Interface Events
5 Replication Events
6 Garbage Collection
7 Internal Configuration
8 Directory Access
9 Internal Processing
10 Performance Counters
11 Initialization/Termination
12 Service Control
13 Name Resolution
14 Backup
15 Field Engineering
16 LDAP Interface Events
17 Setup
18 Global Catalog
19 Inter-site Messaging

New to Windows Server 2003:
20 Group Caching
21 Linked-Value Replication
22 DS RPC Client
23 DS RPC Server
24 DS Schema

Logging Levels
Each entry can be assigned a value from 0 through 5, and this value determines the level of detail of the events that are logged. The logging levels are described as:

• 0 (None): Only critical events and error events are logged at this level. This is the default setting for all entries, and it should be modified only if a problem occurs that you want to investigate.


• 1 (Minimal): Very high-level events are recorded in the event log at this setting. Events may include one message for each major task that is performed by the service. Use this setting to start an investigation when you do not know the location of the problem. 


• 2 (Basic)


• 3 (Extensive): This level records more detailed information than the lower levels, such as steps that are performed to complete a task. Use this setting when you have narrowed the problem to a service or a group of categories.


• 4 (Verbose)


• 5 (Internal:): This level logs all events, including debug strings and configuration changes. A complete log of the service is recorded. Use this setting when you have traced the problem to a particular category of a small set of categories.

To access the full KB article, click this link:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314980&sd=tech

 

KB Article by ID Number:
314980
Directory Services Keywords:
Auditing W2000AUDIT
General Services Keywords:
AD GENERAL
Technologies Keywords:
Networking Keywords:
WINDOWS LOGON
Expires:
Attachments:
 
 
Created at 10/29/2004 7:20 AM by Jean-François APREA
Last modified at 10/29/2004 7:23 AM by Jean-François APREA