Configure Diagnostic Logging

You can use diagnostic logging to record significant events related to authentication, connections, and user actions. You configure diagnostic logging separately for each server. Logging begins automatically when you start Exchange. If you enable protocol logging, all virtual servers for that protocol are logged at the level you set on the host server. By default, the logging is set to None, which logs only critical errors.

To set the logging level:

1. Start System Manager
   On the Start menu, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. In the console tree, double-click Servers, right-click a server, and then click Properties.
3. Click the Diagnostics Logging tab.
4. To log events for a specific feature, in Services, click one of the following:
   • IMAP4Svc. This service allows users to access mailboxes and public folders through Internet Message Protocol version 4 (IMAP4).
   • MSExchangeAL. This service allows users to address e-mail through Address Lists.
   • MSExchangeIS. This service allows access to Information Store.
   • MSExchangeMTA. This service allows X.400 connectors to see message transfer agent (MTA) is used.
   • MSExchangeSA. This counter records an entry when Exchange uses Windows 2000 Active Directory to store and share directory information.
   • MSExchangeSRS. This counter records an entry whenever Site Replication Services are used to replicate computers running Exchange 2000 Server with computers running Exchange 5.5.
   • MSExchangeTransport. This counter records an entry whenever Simple Mail Transfer Protocol (SMTP) is used to route messages.
   • POP3Svc. This counter records an entry whenever Post Office Protocol version 3 (POP3) is used to access e-mail.
5. In Categories, click a category, and then select one of the following Logging levels:
   • None. This level logs only critical events and errors.
   • Minimum. This level logs high-level events by writing one entry for each major task the service performs. This level of logging can help you identify where a problem might be occurring.
   • Medium. This level logs entries for each step taken to run a task. You should use this level of logging after you have identified where a problem is occurring to get more details.
   • Maximum. This level logs entries for each line of code in the service, providing a complete trail of the service's operations and logging all events. This level of logging creates a large amount of data, which can negatively affect server performance.