The Microsoft Exchange Server Best Practices Analyzer Tool automatically examines an Exchange Server deployment and determines if the configuration is set according to Microsoft best practices. You can install the tool on a client computer that is running Microsoft .NET Framework 1.1. With the proper network access, the tool can examine all your Active Directory directory service and Exchange servers to:
Generate a list of issues, such as suboptimal configuration settings or unsupported or nonrecommended options.
Judge the general health of a system
Help troubleshoot specific problems
You can run the tool against an entire deployment, just a specific server, or a set of servers.
Exchange Server Best Practices Analyzer examines servers running Exchange 2000 Server and Exchange Server 2003 as well as Exchange Server 5.5 servers when they are part of a mixed-mode topology. It cannot examine a pure Exchange Server 5.5 deployment.
Download Exchange Server Best Practices Analyzer from the Microsoft Download Center.
State-of-the-Art Expert System Analysis
Exchange Server Best Practices Analyzer has several components that act together as an expert system to verify a deployment’s overall health. This component model produces a highly flexible and adaptable tool. What those components are and how they fit together is illustrated in the following diagram.
Figure 1.1 Components of Exchange Server Best Practices Analyzer
See full-sized image.
Exchange Server Best Practices Analyzer is composed of a core set of libraries that contain:
A dispatcher
A set of collectors for gathering data from a deployment
An analyzer that processes rules on the collected data and generates issues based on the results
The dispatcher is driven by a configuration file that contains:
All the settings it needs to gather
The rules it needs to analyze the settings
The dispatcher then creates a data file that contains all the data gathered and the issues found. These libraries are wrapped in a user interface (UI) so that you can easily execute a scan and examine the results. The UI also has online Help links to assist you both in using the tool and troubleshooting any reported issues.
Component Descriptions
Exchange Server Best Practices Analyzer is composed of the following components.
Configuration. This is an XML file that contains information about all the:
Configuration settings and tests that the tool accesses
Rules that determine whether the data retrieved meets Microsoft best practices
This configuration file is modified on a frequent basis as the data and rules are refined over time. You can set Exchange Server Best Practices Analyzer to automatically look for and download the latest version of the configuration file prior to a run. Or, for closed networks that do not have Internet access, you can use a local copy of the configuration file.
Help. The Help file is a standard Help document, but like the configuration file, the tool can be configured to download the latest version prior to a run or to use a local copy.
Detailed articles. Several hundred detailed articles have been created to explain the various errors and warnings that this tool generates. You can use Exchange Server Best Practices Analyzer to access the articles on the Web, or you can use local copies.
Dispatcher. The dispatcher is the core of Exchange Server Best Practices Analyzer and is responsible for four steps:
Runs through the configuration file
Initializes collectors, which retrieve data or run tests
Starts the analyzer, which executes the rules contained in the configuration file
Generates a list of issues based on the rules
Collectors. For each type of data you retrieve, a collector does the retrieval. For example, the Directory collector retrieves properties from Active Directory. A collector can also execute tests rather than retrieve configuration information. An example of this kind of collector is the Protocol collector, which you can use to send verbs over specific ports and to save the response.
Analyzer. The analyzer is the rules engine. Using XPath-type references, it can compare retrieved values across several properties and generate messages based on those values. For instance, you might use it to look at the amount of RAM on a server and check to see if the /3GB operating system setting is correct for the hardware configuration.
ExBPA core engine. ExBPA is the name of the binary. The core engine consists of the dispatcher, a set of collectors, and the analyzer.
UI. You can execute the core engine through one of two UIs:
Command line version, which you can use for scripting the execution
Graphical user interface (GUI) to execute a run and examine the results
Data file. All the data that this tool retrieves and all the messages that it generates based on its analysis are saved in an XML data file. This file can then be viewed immediately or at a later time for historical information. You can use the GUI to view the analysis as well as all the data that led to the analysis, creating a system snapshot for capturing a point-in-time configuration of a deployment.