Preventive maintenance will help you identify potential errors before any one of these errors cause problems
with the operation of your Exchange organization. Preventive maintenance combined with disaster recovery
planning and regular backups will help minimize problems if they occur. Monitoring your Exchange organization
also set alerts to notify administrators when problems occur. Microsoft\u00ae Windows Server\u2122 2003 and Exchange
Server 2003 provide you with many monitoring tools and services to ensure that your Exchange Server 2003
organization is running smoothly. The key advantages to daily monitoring are as follows:
The following daily maintenance tasks let you establish criteria for what is normal for your organization and to
detect any abnormal activity. It is important to implement these daily maintenance tasks so that you can
capture and maintain data about your Exchange organization, such as usage levels, possible performance
bottlenecks, and administrative changes. The following tasks are discussed in detail this topic:
\u2022Performing physical environmental checks
\u2022Checking disk usage
\u2022Checking the Event Viewer
\u2022Checking connector and server status
\u2022Monitoring server performance
\u2022Checking message paths
\u2022Performing daily database maintenance
\u2022Monitoring network performance
\u2022Monitoring Exchange and Windows services
\u2022Monitoring cluster resources
\u2022Enforcing security measures
Before you check performance, availability, and functionality of your Exchange organization, you should check the physical environment. For example, the server room temperature might need to be lowered, or a network cable might need to be replaced. You should perform the following physical environmental inspections:
You can use Event Viewer to obtain information about service failures, replication errors in the Microsoft Active
Directory\u00ae directory service, and warnings about system resources such as virtual memory and disk space.
Use Event Viewer to view and manage event logs; obtain information about hardware, software, and system
Event Viewer maintains logs about application, security, and system events on your computer. Both Exchange
Server and Windows report warnings and error conditions to the event logs. Therefore, make sure that you
review event logs daily. For more information about Event Viewer, see the Windows Server 2003 Help
documentation. You can also use Event Viewer as a troubleshooting tool. For more information about using
Event Viewer as a troubleshooting tool, see Microsoft Knowledge Base article 302542, "How to Diagnose
System Problems with Event Viewer in Windows Server 2000" (http: / / go.microsoft.com/ fwlink/ ?
Product Support Services. Maximum logging drains significant resources and can give many "false positives,"
that is, errors that get logged only at maximum logging but are really expected and are not a cause for
concern. It is also recommended that you do not keep diagnostic logging on permanently. It should be used
only when troubleshooting.
logs closely to track the types of transactions being conducted on your Exchange servers. You should
periodically archive the logs or use automatic rollover to avoid running out of space. Because log files can
occupy a finite amount of space, increase the log size (for example, to 50 MB) and set it to overwrite, so that
Server 2003 Management Pack extends Microsoft Operations Manager by providing specialized monitoring for servers that are running Exchange Server 2003. This management pack includes a definition of health for an Exchange 2003 server and will raise an alert message to the administrator if it detects a state that requires intervention. For more information about Exchange 2003 Management Pack, see the Microsoft Operations Manager Web site (http: / / go,microsoft.com/ fwlink/ ?linkid= 16198).
This action might not be possible to undo. Are you sure you want to continue?