Server name case mismatch
[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 queries the Active Directory® directory service to determine the value stored in Active Directory for the name of the Exchange server (CN=<ExchangeServerName>). After the Exchange Server Analyzer retrieves this name, the Exchange Server Analyzer counts the number of characters in the name.
The Exchange Server Analyzer also reads the following registry entry to determine the value stored in the Exchange Server computer's registry for the host name of the Exchange server:
The Exchange Server Analyzer also queries the Win32_Service Microsoft Windows® Management Instrumentation (WMI) class to determine the value of the Started key for ClusSvc, the Windows® Cluster service.
The Exchange Server Analyzer displays a non-default configuration message if all the following conditions are true:
The value for CN=<ExchangeServerName> does not match the case for the value in Hostname. For example, CN=ComputerName and Hostname is set to COMPUTERNAME.
Although changing the case of the server name in the registry is supported, it is not recommended.
The Exchange server name is 15 characters or less.
The Exchange server is not running in a Windows cluster.
The most common cause of this error is that the name of the Exchange server has been changed manually in the registry.