How to use Legacydn.exe to correct Exchange organization names or Administrative Group names in Exchange Server 2003 or in Exchange 2000 Server

Legacydn.exe is a tool that you can use to perform the following tasks:

• Change the Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 organization name.
• Change the administrative group names.
• View the legacyExchangeDN values.
• Change the legacyExchangeDN values.

Note We support using the Legacydn.exe tool only in a lab environment. The tool works only in an environment that uses a single domain controller.

If you use this tool to help recover databases in an Exchange Server system recovery scenario, the server that is running Exchange Server will be in an unsupported state.

To bring the Exchange Server server back to a supported state, export the data in the mailboxes to personal folders (.pst) files by using the Exmerge tool. Uninstall and then reinstall Exchange Server, and then import the .pst data into the Exchange Server mailboxes by using the Exmerge tool.

For more information about the Exmerge tool, click the following article number to view the article in the Microsoft Knowledge Base: We recommend that you always perform a system state backup before you run any tool that modifies Active Directory directory service attributes.

Legacydn.exe is a graphical interface tool that you can use to change the Exchange organization name or the administrative group name and to resolve MSExchangeIS 1088 events that may be logged in the Event Viewer Application log in a lab environment. The following is an example of the event:

Event ID: 1088
Source: MSExchangeIS
Type: Error
Category: General
Description: The information store could not be loaded because the distinguished name (DN) of message database /O=old_org_name/OU=old_site_name/CN=RECIPIENTS/CN= does not match the DN of directory /O=new_org_name/OU=new_site_name/CN=RECIPIENTS/CN=.

For more information about ways to resolve this issue in a production environment, click the following article numbers to view the articles in the Microsoft Knowledge Base: To use Legacydn.exe, follow these steps:

1. Obtain a copy of Legacydn.exe from the Microsoft Download Center. To do this, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?familyid=5ef7786b-a699-4aad-b104-bf9de3f473e5&displaylang=en
2. For detailed information about the tool, review the Legacydn.doc file that is included with Legacydn.exe.
3. Copy the Legacydn.exe file to the Exchange 2000 Server or Exchange Server 2003 computer, and then double-click the file to open the graphical user interface (GUI).
   
   If you use Legacydn to make changes to the legacyExchangeDN values in a production environment, you can no longer start any Exchange database.
4. If Legacydn.exe is not running in read-only mode, this means that you are working in a lab environment and have used the FORCEWRITE command-line option. In this scenario, you can make changes to the legacyExchangeDN values by using the Legacydn interface.
5. When you run Legacydn.exe, a log file named LegacyDN.log is created to record the startup search information and any changes that you make.
   
   You can change the logging level of Legacydn.exe from Normal (0) to Verbose (1). Normal (0) is the default setting.

The following list describes the command-line options for Legacydn.exe:

LegacyDN [/DUMPAGS] [/LOGLEVEL <logging level>] [/SERVER <preferred server name>] [/USER <username>] [/PASSWORD <password>] [/FORCEWRITE

• /DUMPAGS. This option dumps the administrative group list to the log file.
• /LOGLEVEL. The default logging level is 0 (Normal), and you can also set the logging level to 1 (Verbose).
• /SERVER. Fully Qualified Domain Name (FQDN) of preferred Windows domain controller
• /USER. User name
• /PASSWORD. Password
• /FORCEWRITE. Must be used to run in edit mode.

Note To view this list, you can also run Legacydn.exe with the /? command-line option