White Papers

Troubleshooting
18 Dell EMC SC Series: Microsoft Exchange Server Best Practices | CML1037
Set the MaxSize and MaxAge parameters appropriate to the capacity available on the disk. Exchange will
delete the data as soon as it reaches the first of those two values. Microsoft Support recommends leaving
these settings at the default to collect the appropriate logging required for detailed troubleshooting operations.
For reference information on setting up and working with this new troubleshooting tool, see the
WindowsITPro
article.
4.3 Microsoft Exchange Troubleshooting Assistant (2007/2010)
The Exchange Troubleshooting Assistant is an integrated component of the Exchange Management Console
Toolbox in Exchange Server 2007/2010. It programmatically executes a set of troubleshooting steps to
identify the root cause of performance, mail flow, and database mounting issues.
This tool automatically determines what set of data is required to troubleshoot the identified symptoms and
collects configuration data, performance counters, event logs, and live tracing information from an Exchange
server and other appropriate sources. It also analyzes each subsystem to determine individual bottlenecks
and component failures, and then aggregates the information to provide root cause analysis. The output of
this report can assist customers and their hardware vendors in troubleshooting Exchange-related problems
prior to migration to Exchange Server 2013 or greater.
4.4 Microsoft Exchange Best Practices Analyzer (2007/2010)
The Exchange Best Practices Analyzer is available with Exchange Server 2007/2010. It is installed during
Exchange Setup and can be run from the Exchange Management Console Toolbox.
This tool programmatically collects settings and values from data repositories such as Active Directory,
registry, metabase, and Performance Monitor. Once collected, a set of comprehensive, best-practice rules are
applied to the topology. Administrators running this tool will get a detailed report listing the recommendations
that could be made to the environment to achieve greater performance, scalability, and uptime.
It is recommended to run this in the existing Exchange 2007 or 2010 environment prior to moving to
Exchange Server 2013 to have the best migration experience.