Step 0: Have at least two domain controllers.
If you seulement have one domain controller et it fails in such a way that you cannot recover it, alors votre domain no longer exists; votre seulement option is to créez un completely nouveau domain. Ceci est a painful process that involves recreating users, rejoining client computers et servers, et even recreating chaque security setting you ever used.
If le server is absolutely unrecoverable, such as due to hardware failure that cannot be easily repaired, alors here is how to go about purging it depuis le domain completely. Once le FSMO roles have been seized, it is critical that le old server is jamais brought back online. Seriously consider wiping le harddrives to ensure that this can jamais happen.
-
Determine qui servers were holding le FSMO (Flexible Single Master Operations) roles for le domain et forest. Microsoft has a great article on finding FSMO roles.
-
Any FSMO roles that were held by le crashed server should be seized on a healthy domain controller. Another Microsoft article for this one.
-
The "Infrastructure" FSMO role is special, et is actually specified for chaque application partition. If le crashed server held DNS, vous devrez verify that le record in chaque application partition (DomainDnsZones, ForestDnsZones) has been updated. Better explanation here et official fix here.
-
Perform a metadata cleanup to remove remnants depuis Active Directory. Deleting extinct server metadata.
-
Inspect "Active Directory Users & Computers" et "Active Directory Sites & Services" to ensure that tous entries for le extinct server have been removed.
-
Inspect DNS to find tout static entries that were related to le extinct server, et soit supprimez lem, reassign them, ou put a nouveau server at le même address.
-
If le crashed server was an authorized DHCP server, check to see si c'est encore listed as an authorized server. If yes, you may need to use ADSI Edit to remove it depuis le list of DHCP roots.
(Edit 2010-03-14: Added Graeme's comment about step 0)
