Supplemental steps for using the Exchange Server Domain Rename Fixup tool together with the Windows Server 2003 domain rename tools (842116)

SUMMARY

INTRODUCTION

Documents and tools that you must have to rename the domain

• The Windows Server 2003 domain rename tools and the document that is named Step-by-Step Guide to Implementing Domain Rename. To download these tools and this document, visit the following Microsoft Web site:

  http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90a2a2e2/Domain-Rename-Procedure.doc

• This Microsoft Knowledge Base article. The information that is in this article supplements the procedures that are described in the Step-by-Step Guide to Implementing Domain Rename document. This article contains the steps that are specific to Exchange Server; these steps are named "Exchange-specific steps" in this article.
• The Exchange Domain Rename Fixup tool. The following file is available for download from the Microsoft Download Center:
  XDR-Fixup.exe. To download this tool, visit the following Microsoft Web site:

  http://www.microsoft.com/downloads/details.aspx?FamilyId=24B47D4A-C4B9-4031-B491-29839148A28C&displaylang=en

  Release Date: 5/25/2004
  
  For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

  119591 How to Obtain Microsoft Support Files from Online Services

  Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

What the Exchange Domain Rename Fixup tool does

What the Exchange Domain Rename Fixup tool does not do

Does not rename your e-mail domain

Does not rename your Exchange organization

Does not merge your Exchange organizations

Prerequisites to rename your domain

• All domain controllers must be running Windows Server 2003. Additionally, Active Directory must be at the Windows Server 2003 forest functional level. For more information about forest functional levels, see the Windows domain rename tools documentation and the Windows Server 2003 documentation. To view the current functional levels in Windows, follow these steps:
  1. Start the Active Directory Domains and Trusts tool. To do this, click Start, point to Administrative Tools, and then click Active Directory Domains and Trusts.
  2. Right-click your domain container, and then click Properties.
  3. View the information that appears on the General tab.
  4. If the forest functional level is not set to Windows Server 2003, you must raise the forest functional level.
     
     Note You cannot raise the forest functional level until your domains are running the Windows Server 2003 domain functional level.
     For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

     322692 How to raise domain and forest functional levels in Windows Server 2003

• All Exchange Server computers in the organization must be running Exchange Server 2003. You can use the domain rename tools and the Exchange Domain Rename Fixup tool with Exchange Server 2003 only.
  
  Important The Rendom.exe tool and the XDR-fixup.exe tools are not supported in Exchange 2000 Server or in Exchange Server 5.5. If the Rendom.exe tool detects Exchange 2000 Server computers, the domain rename operation does not continue. However, the Rendom.exe tool does not detect whether Exchange Server 5.5 computers exist. Therefore, do not rename your domain if a domain contains Exchange Server 5.5 computers. Additionally, if Site Replication Service (SRS) is running in the forest, you must remove SRS before you start the domain rename operation. For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

  822450 How to remove the last Exchange Server 5.5 computer from an Exchange Server 2003 administrative group

  260781 The Change Mode button is unavailable in the Organization Properties dialog box after you upgrade Exchange Server 5.5 Service Pack 3 to Exchange 2000 Server or to Exchange Server 2003

• To use the domain rename operation, Exchange Server must not be installed on any domain controllers. If a domain controller is running Exchange Server, you must move the Exchange data from the domain controller, and then remove Exchange Server.
• To perform the domain rename procedure, the account that you use must have Enterprise Admins user rights. The account that you use must also have Exchange Full Administrator permissions.

Preparing for the domain rename

• Create any necessary shortcut trusts and document all trusts.
• Prepare DNS zones.
• Make any Distributed File System (DFS) changes.
• Prepare member computers.
• Prepare Certification Authorities.

The XDR-fixup.exe command options

Command-line usage to run XDR-fixup.exe

Command-line usage to verify XDR-fixup.exe

Use XDR-fixup.exe together with the domain rename tools

• Two preparation steps that you must perform before you rename the domain.
• Two additional steps that you must perform during the domain rename operation.
• Three additional steps that you must perform after the domain rename operation is completed.

New Exchange-specific step A: Remove Exchange from domain controllers

New Exchange-specific step B: Stop Exchange Server configuration changes

Step 1: Back up all domain controllers

Step 2: Set up the control station

Step 3: Generate the current forest description

Step 4: Specify the new forest description

Step 5: Generate domain rename instructions

Step 6: Push domain rename instructions to all domain controllers and verify DNS

Step 7: Verify the readiness of domain controllers

Step 8: Run the domain rename instructions

New Exchange-specific step C: Update the Exchange Server configuration

1. Wait for all the domain controllers to restart and for domain controller replication to complete throughout the renamed domain.
2. On the control station computer where the XDR-fixup tool is installed, click Start, point to All Programs, point to Microsoft Exchange, point to Exchange Domain Rename Tool, and then click Exchange Domain Rename Tool.
3. At the command prompt, type the following command, and then press ENTER:

   XDR-fixup /s:start_domainlist.xml /e:end_domainlist.xml /trace:tracefile /changes:changescript.ldf /restore:restorescript.ldf

   For example, if you configured the XML files by using the default names that are specified in the Step-by-Step Guide to Implementing Domain Rename document, type the following command, and then press ENTER:

   xdr-fixup /s:c:\domainrename\domainlist-save.xml /e:c:\domainlist.xml /trace:tracefile /changes:changescript.ldf /restore:restorescript.ldf

   Note You have to run this step only one time in the forest, and not one time for each Exchange Server computer.
4. After the XDR-fixup command has completed successfully, log off the control station computer, and then log back on.
   
   Note The original domain may appear in the Log on to list when you log on the computer. In this scenario, click the newly renamed domain name in the Log on to list when you log on. When you open the Log on to list, the original domain name no longer appears.
5. Click Start, point to All Programs, point to Microsoft Exchange, point to Exchange Domain Rename Tool, and then click Exchange Domain Rename Tool.
6. At the command prompt, type the following command, and then press ENTER:

   LDIFDE -i -f changescript.ldf

7. On every server cluster in the renamed domain, run the following command:

   Cluster /priv MSExchange_Domain=DNS_Name_of_renamed_domain

8. On every cluster node computer, reset the logon account for the Cluster Service. To do this:
   1. Click Start, click Run, type services.msc in the Open box, and then click OK.
   2. Double-click Cluster Service, and then click the Log On tab.
   3. Under Log on as, type the user account by using the UNC format that references the new renamed domain. For example, in the This account box, type the Cluster Service user account in the following format:

      RenamedDomain\Clusteraccountname

   For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

   307532 How to troubleshoot the Cluster service account when it modifies computer objects

New Exchange-specific step D: Restart all Exchange Server computers

• Exchange Server computers.
• Computers that are running Exchange System Manager.

Step 9: Allow modifications to the forest configuration

Step 10: Re-establish external trusts

Step 11: Repair the Distributed File System topology

Step 12: Repair Group Policy objects and links

After the domain rename procedure is completed

• Verify certificate security after domain rename
• Miscellaneous tasks
• Back up domain controllers
• Restart member computers

• New Exchange-specific step E: Verify Exchange Server rename operation

  
  
  After the member computers are restarted, and after replication has completed throughout the domain, identify the Exchange Server computers that did not have their primary DNS suffix settings updated by the domain rename process. By default, domain members have their primary DNS suffix automatically updated when their domain membership changes. However, certain computers may be configured so that the primary DNS suffix does not automatically change when their domain membership changes or when their domain name changes. For additional information about these configuration settings, see the "How to Determine the Primary DNS Suffix Configuration" topic in the Step-by-Step Guide to Implementing Domain Rename document. This step verifies that the Exchange Server computers in your domain have a dynamically-configured primary DNS suffix. To verify the Exchange Server rename and complete the follow-up steps, follow these steps:
  1. Click Start, point to All Programs, point to Microsoft Exchange, point to Exchange Domain Rename Tool, and then click Exchange Domain Rename Tool.
  2. Type the following command, and then press ENTER:

     XDR-fixup /verify:restorescript.ldf /changes:verifycorrections.ldf

     Note This step identifies Exchange Server computers that were not renamed after the domain rename procedure. You have to perform this step only one time in the forest, and not one time for each Exchange Server computer.
  3. If the XDR-fixup tool returns results to indicate that one or more Exchange Server computers have a primary DNS suffix that is not automatically updated when the domain membership changes, use one of the following methods:
     • If you want the Exchange Server computers to remain configured so that they do not automatically change their primary DNS suffix settings when their domain membership changes, type the following command, and then press ENTER:

       ldifde -i -f verifycorrections.ldf

     • If you want the Exchange Server computer to automatically update the primary DNS suffix when their domain membership changes, follow these steps:
       1. On the Exchange Server computer, click Start, right-click My Computer, and then click Properties.
       2. Click the Computer Name tab, and then click Change.
       3. Click More, click to select the Change primary DNS suffix when domain membership changes check box, and then click OK.
       4. Restart the computer two times, and then allow sufficient time for all replication to complete. After the computer has restarted two times, and after replication has completed, run the XDR-fixup command from Step 1 again. When you run this command again, ignore the LDF file that the command created previously.
       Note If the XDR-fixup tool indicates that the Exchange Server computer has a static primary DNS suffix assigned, but the Change primary DNS suffix when domain membership changes check box is selected in the DNS Suffix and NetBIOS Computer Name dialog box, make sure that this computer was restarted two times after the Rendom /execute command was run to rename the domain, and that sufficient time has passed to allow replication to complete.
  4. On every RPC over HTTP proxy server, rename the computers that are specified in the ValidPorts registry entry. To do this:
     1. Click Start, click Run, type regedit in the Open box, and then click OK. Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
     2. Locate and click the following registry subkey:

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy

     3. In the right pane, double-click ValidPorts.
     4. In the Value data box, modify the computer entries to reflect the new renamed domain, and then click OK.

• New Exchange-specific step F: Update the Active Directory Connector

  If applicable, update the Active Directory Connector (ADC) in your organization. You can rename a domain where ADC is installed if ADC is used to connect two organizations. Because the domain rename operation is not supported when a forest contains Exchange Server 5.5 computers or Site Replication Service, you cannot rename a domain where ADC is used to connect Exchange Server 5.5 to Exchange Server 2003. If you run ADC with an inter-organizational connection agreement, you must update the trusts and logon accounts that are used by the inter-organizational connection agreement after you rename the domain. To do this:
  1. Remove existing trusts to the domain where the Exchange organization is located, and then create new trusts that reflect the new renamed domain.
  2. Update the ADC service account to reflect the new domain, and then restart the Active Directory Connector Service. To do this:
     1. On the computer where ADC is installed, click Start, click Run, type services.msc in the Open box, and then click OK.
     2. Double-click Microsoft Active Directory Connector, and then click the Log On tab.
     3. Under Log on as, modify the service account by using the UNC format that references the new renamed domain.
        
        For example, in the This account box, type the service account in the following format:

        RenamedDomain\ServiceAccountName

     4. Click OK, right-click Microsoft Active Directory Connector, and then click Restart.
  3. For every inter-organizational connection agreement, update the Active Directory account information. To do this:
     1. On the computer where ADC is installed, click Start, point to All Programs, point to Microsoft Exchange, and then click Active Directory Connector.
     2. Click Active Directory Connector (Servername).
     3. In the right pane, right-click an inter-organizational connection agreement, and then click Properties.
     4. Click the Connections tab, and then click Modify under Windows Server information.
     5. In the Connect as box, type the account credentials in the UNC format that reflects the new renamed domain. For example, in the Connect as box, type the account credentials in the following format:

        RenamedDomain\AccountName

     6. Type the account password in the Password box, and then click OK two times.
  4. For every connection agreement, update both the source computer container(s) and the destination computer container(s). To do this:
     1. On the computer where ADC is installed, click Start, point to All Programs, point to Microsoft Exchange, and then click Active Directory Connector.
     2. Click Active Directory Connector (Servername).
     3. In the right pane, right-click a connection agreement, and then click Properties.
     4. If the replication direction includes the From Windows to Exchange direction, click the From Windows tab, and make a note of the organizational units that appear in the Windows Organizational Units list. Click Remove to remove each organizational unit. Click Add to add each of the organizational units that you want to use from the new renamed domain. Click OK to close the properties of the inter-organizational connection agreement.
     5. If the replication direction includes the From Exchange to Windows direction, click the From Exchange tab , click Modify, click the organizational unit that you want to use from the new renamed domain, and then click OK two times.
• Attribute clean-up after domain rename (Rendom.exe /clean). Before you perform this procedure, review the prerequisites found in the "Attribute Clean-up After Domain Rename" section in the Step-by-Step Guide to Implementing Domain Rename document.
• Rename domain controllers (optional)

• New Exchange-specific step G: Domain controller rename operation follow-up

  If you rename your domain controllers as described in the "Rename Domain Controllers (Optional)" topic in the Step-by-Step Guide to Implementing Domain Rename document, follow these steps:
  1. Modify the Recipient Update Service to connect to the newly renamed domain controller to update objects in Active Directory. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

     288807 Troubleshooting the Recipient Update Service

  2. If any domain controllers are statically assigned as directory service (DSAccess) servers, repair the registry keys that specify these DSAccess domain controllers. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

     250570 Directory service server detection and DSAccess usage

  3. If e-mail messages remain in the message queues on one or more of your Exchange Server computers and appear to be "stuck" on those computers, restart the Simple Mail Transfer Protocol (SMTP) service on those affected computers. To restart the Simple Mail Transfer Protocol (SMTP) service:
     1. Click Start, click Run, type services.msc in the Open box, and then click OK.
     2. Right-click Simple Mail Transfer Protocol (SMTP), and then click Restart.

Errors and event logs

• Event source: DSAccess
  Event IDs: 2102, 2103, and 2104
• Event source: MSExchangeAL
  Event IDs: 8206 and 8260
• Event source: MSExchangeSA
  Event IDs: 9154 and 9188