Topic Last Modified: 2007-05-16

In addition to running Microsoft® Exchange Server Best Practices Analyzer Tool with an account that has the required permissions on Active Directory® directory service, and an account that has the required permissions on the Exchange servers, you need to check some additional prerequisites to run the tool successfully.

Prerequisites

For Exchange Server Best Practices Analyzer to run correctly, the following must be true:

  • .NET Framework 1.1 must be installed on the computer on which Exchange Server Best Practices Analyzer will run.

  • Internet Information Services (IIS) Common Files (or Common HTTP Features for Windows Vista™) must be installed on the computer on which Exchange Server Best Practices Analyzer will run, to allow remote metabase access.

    Note:
    If Internet Information Services, Internet Information Services Admin, or Exchange System Manager are installed, Internet Information Services Common Files will be installed automatically.
  • The computer on which Exchange Server Best Practices Analyzer will run must have at least 256 megabytes (MB) of random access memory (RAM). This amount of memory is sufficient for scanning up to 50 Exchange servers. For each addition of up to 50 servers in the Exchange organization, you will need an additional 256 MB of RAM on the computer that is running the tool. For example, if you have between 50 and 100 Exchange servers in your organization, you must have at least 512 MB of RAM on the computer that is running the tool. If you have between 100 and 150 Exchange servers in your organization, you must have at least 768 MB of RAM on the computer that is running the tool.

  • For each Exchange server in the organization that you will scan, you must have at least 2 MB of disk space on the computer on which the Exchange Server Best Practices Analyzer will run.

  • Active Directory must be installed in the topology, on either Microsoft Windows 2000 Server or Windows Server™ 2003.

  • At least one Exchange 2003 or Exchange 2000 server must be installed within Active Directory.

  • Remote Registry (RemoteRegistry) service must be running on both the Active Directory server and the Exchange servers.

  • Windows Management Instrumentation (WMI) (winmgmt) service must be running on both the Active Directory server and the Exchange servers.

  • Exchange Management (MSExchangeMGMT) service must be running on all Exchange servers that are Exchange 2000 Server or later versions.

  • The user who is logged on and running Exchange Server Best Practices Analyzer must have read/write permission to the folder from which the tool runs.

  • To collect Host Bus Adapter (HBA) information, an HBA API-compliant driver and remoting service (such as Emulex's HBAnywhere service) must be installed on any server from which you want to collect HBA information. Additionally, the HBA API Managed Object Format (MOF) installer must be run on both the computer on which the Exchange Server Best Practices Analyzer will run and the target server where the HBA is installed. If an HBA API-compliant driver and remoting service are not installed, Exchange Server Best Practices Analyzer will run, but will not collect HBA information.

Supported Environments

Exchange Server Best Practices Analyzer can be run in the following environments:

  • Exchange Server 5.5 on Windows 2000 Server SP3 and later versions

Note:
The Exchange Server 5.5 server must be part of a mixed-mode Exchange organization, represented in Active Directory.
  • Exchange 2000 Server (all service packs) on Windows 2000 Server SP3 and later versions

Note:
Neither Windows 2000 Server nor Exchange 2000 Server support extensive WMI providers. Data collection and analysis may be limited.
  • Exchange 2003 Server (all service packs) on Windows 2000 Server SP3 and later versions

Note:
Windows 2000 Server does not support extensive WMI providers. Data collection and analysis may be limited.
  • Exchange Server 2003 (all service packs) on Windows Server 2003

  • Exchange Server 2007 on Windows Server 2003

See Also

Concepts

Permissions