Topic Last Modified: 2006-12-03

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine whether the Name attribute and the cn attribute of a server (object of class msExchExchangeServer) match. If the Exchange Server Analyzer finds that these attributes differ, an error message is displayed.

Exchange uses the cn value of the server object to identify the server internally. It uses the Name value to identify the server in the Microsoft Exchange System Manager user interface.

This error can occur if an administrator changed the Name value using a tool such as Active Directory Service Interfaces (ADSI) Edit or the LDP (ldp.exe) tool. While this action does change the server name in the user interface, it creates a discrepancy that generates store and system attendant events. You must correct the value using a tool such as the ADSI Edit snap-in, the LDP tool, or any other Lightweight Directory Access Protocol (LDAP) version 3 client.

Caution:
If you incorrectly modify the attributes of Active Directory objects when you use ADSI Edit, the LDP tool, or another LDAP version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003 or Exchange Server 2007 or both. Modify Active Directory object attributes at your own risk.

To correct this error

  1. Using ADSI Edit or a similar tool, locate the server object in Active Directory.

    The CN and Name attribute can be found at:

    Copy Code
    CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups,CN=Administrative group,CN=Servers,CN=Server
    
  2. For the Name attribute, type a new string value that matches the value of the CN attribute.

For more information about using the LDP tool, see the Microsoft Knowledge Base article 260745, "XADM: Using the LDP Utility to Modify Active Directory Object Attributes" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=260745).

For more information about working with ADSI Edit, see the topic "Adsiedit.msc: ADSI Edit" in the Windows Server Help.