Export (0) Print
Expand All

Restoring a Domain Controller Through Reinstallation

Updated: March 2, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Restoring a domain controller through reinstallation is the same process as creating a new domain controller. It does not involve restoring from backup media. This method relies on Active Directory replication to restore a domain controller to a working state, and it is valid only if another healthy domain controller exists in the same domain. This method is normally used on computers that function only as a domain controller.

Restoring through reinstallation is the only method by which a domain controller that is not part of the backup set can be restored. In addition, you might choose to use this method instead of a nonauthoritative restore because backup media is inaccessible or because this method is more convenient. Restoring a domain controller through reinstallation should not be a substitute for regular backup routines.

This method of restoring a domain controller requires a complete reinstallation of the operating system. It is recommended that before you install the operating system, you format the entire system disk, which will remove all information on the system disk. Ensure that any important or relevant data is moved or backed up before you perform these actions.

Bandwidth is the primary consideration for restoring a domain controller through reinstallation. The bandwidth that is required is directly proportional to the size of the Active Directory database and the time in which the domain controller is required to be in a functioning state. Ideally, the existing functional domain controller should be located in the same Active Directory site as the replicating domain controller (the new domain controller) to reduce the impact on the network and the time that the reinstallation takes to complete.

noteNote
Before you restore a domain controller through reinstallation, ensure that hardware failure is not the cause of the problem. If faulty hardware is not changed, restoring through reinstallation might not solve the problems with the domain controller.

Task requirements

The following tools are required to perform the procedures for this task:

  • Ntdsutil.exe

  • Netdiag.exe

  • Dcdiag.exe

  • Dcpromo.exe

To complete this task, perform the following procedures:

  1. If you plan to give the newly reinstalled domain controller the same name as the failed computer, use the following procedure to clean up server metadata to remove the NTDS Settings object of the failed domain controller:

    Clean up server metadata

    If you plan to give the new domain controller a different name, in addition to cleaning up server metadata, perform the following additional procedures:

    Delete a Server object from a site

    Delete a Computer object from the Domain Controllers OU

  2. Install Windows Server 2003

    It is assumed that you will perform a fresh installation of Windows Server 2003. Prepare for installation of the operating system by partitioning or reformatting your hard disk drive, if necessary.

  3. Verify DNS registration and functionality

  4. Verify communication with other domain controllers

  5. Verify the availability of the operations masters

  6. Install Active Directory

    During the installation process, replication occurs, which ensures that the domain controller has an accurate and up-to-date copy of Active Directory. You have the option to use the same information for this domain controller as the domain controller that it is replacing: site placement, domain controller name, and domain membership should remain the same. If you plan to install the domain controller under a different name, see Installing a Domain Controller in an Existing Domain.

  7. Verifying Active Directory Installation

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft