Best Practices

The following are best practices from this chapter:

• Manage Exchange Server 2003 based on server roles and responsibilities.

• Audit the messaging environment, using Windows Server 2003 auditing.

• Use Exchange Server 2003's protocol logging and diagnostic logging for troubleshooting purposes.

• Install the ESM on a client computer to remotely administer Exchange Server 2003. Use the same version of Exchange Server 2003 and service pack level of the servers being managed.

• Keep AD well-tuned using ntdsutil, because Exchange Server 2003 directly relies on it.

• Avoid possible adverse affects with the AD database by running ntdsutil in Directory Service Repair mode.

• Perform an online and offline copy of the information stores prior to running offline maintenance tasks.

• Use isinteg in test mode unless there is a specific problem reported.

• Never manually modify Exchange Server 2003 databases and transaction log files.

• Document the Exchange Server 2003 messaging environment configuration and create a change log to document changes and maintenance procedures.

• If you are experiencing problems with OAL generation, enable diagnostic logging and review the Application Log for any OAL Generator category events.

• Document the process of restoring Exchange Server 2003 databases. If documentation already exists, verify that the existing process has not changed. If it has changed, update the documentation.

• Create post-maintenance procedures to minimize time needed for restoration.

• Include the System State data in daily backup routines.

• Reduce management and maintenance efforts, using the MOM Application Management Pack.