Article Summary: This article provides information on recovering an Active Directory domain controller that won't boot into normal mode.
If an Active Directory domain controller (DC) fails in such a way that the server will not boot normally, you should first attempt to boot the DC into Directory Services Restore/Repair Mode to determine whether the issue is caused by a problem with the DC's local copy of the AD database.
If the server is able to boot into DSRM, see Repair a Corrupt Active Directory Database on a Domain Controller that Won't Boot into Normal Mode for instructions on attempting to repair the database.
Assuming the DC is unable to boot to DSRM and the problem is not caused by a corrupt AD database, the procedure for recovering the failed DC depends in part on whether there are additional operational DCs in the domain. If at least one other DC exists in the domain, there are two options available for recovery of the failed DC:
Note: The procedures below are not intended to troubleshoot the underlying cause of the failure. These procedures assume that the underlying issue has been diagnosed and repaired or that the only path to resolution involves restoring or rebuilding the server.
If a valid system-state backup is available, you may use to it recover the failed DC. The procedure for restoring a failed DC from a backup depends on the version of Windows running on the DC:
If no valid backup is available or you do not wish to restore it, you may simply rebuild the failed DC from scratch and re-promote it. The other DCs will ensure that the domain remains accessible while the failed DC is being rebuilt and that the DC's local copy of the AD database is brought up to date after recovery. The procedure for rebuilding a failed DC from scratch is as follows:
Datum der letzten Änderung: 09/03/2014 01:36 PM
Vielen Dank für Ihr Feedback.