ClientMonitoringReportLevel parameter is non-default
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool reads the following registry key to determine how Exchange Server 2003 monitors network performance data for Microsoft Office Outlook® 2003:
If the Exchange Server Analyzer finds that the value for the ClientMonitoringReportLevel registry key is not 1, the Exchange Server Analyzer displays a non-default configuration message.
Exchange Server uses the value of the ClientMonitoringReportLevel registry key to identify network errors and latency problems with Outlook 2003 clients. The value of the ClientMonitoringReportLevel registry key has three possible settings.
Do not collect any performance data from any Outlook 2003 client.
Collect performance data from Outlook 2003 clients that have high-speed network connectivity only.
Collect performance data from all Outlook 2003.
When you enable the ClientMonitoringReportLevel registry key with a value of 1 or 2, Outlook 2003 clients send data to the server. The data that is sent to the server indicates the status and state of the network connection. The data that is sent to the server includes information about failed remote procedure call (RPC) requests and error conditions. The server aggregates the information and exposes the information in event log entries.
Exchange Setup does not create the ClientMonitoringReportLevel registry key. However, the default behavior in Exchange Server 2003 is to collect performance data only from Outlook 2003 clients that have high-speed network connectivity. This default behavior of Exchange Server 2003 is functionally the same as the functionality when the value of the ClientMonitoringReportLevel registry key is set to 1.
The Exchange Server Analyzer reports this configuration for informational purposes only. No action is required. However, you can edit the value of the ClientMonitoringReportLevel registry key if you want to restore the default value.
This article contains information about editing the registry. Before you edit the registry, make sure that you understand how to restore the registry if a problem occurs. For information about how to restore the registry, see the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.
To restore the default configuration
Open a registry editor, such as Regedit.exe or Regedt32.exe.
Navigate to: HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
In the Value data field, type 1, and then click OK.
Close the registry editor.
The Microsoft Exchange Information Store service detects the changes in minutes. You do not have to restart the computer.
Before you edit the registry, and for information about how to edit the registry, see the Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).