RJenkins
Joined: 30 Mar 2006
Posts: 5
Location: UK
|
 Posted:
Wed Apr 05, 2006 3:06 pm Post subject:
|
|
|
The answer to this depends if this is the only domain controller on your network or not.
Basically this is an extreme thing to do and should only be used as a last resort. If it were me, I would try to fix the problem first and if that didnt work, only then would I do the reinstall of AD.
if you were to do it, and if it was your only dc:
The best bit of advice I would give in this scenario is to back up everything on your DC, -particularly the system state (which contains the active directory database), the boot/system partitions (may be the same volume) plus any other data you have on any other drives relating to the system.
Next I would back up again. just to be sure. Make sure you verify both backups before proceeding.
If possible, image the server onto another hard disk, even if its a temporary one, at least you can revert to that if needed if it all goes wrong. -you may also consider putting new disks in the server to do the install on if budget allows, thus you can keep your old disks as backups and a rollback plan.
reinstall the OS. when its back up, reboot and on startup, enter directory services restore mode, restore the backup of the boot files, system files and system state and the from your backup file/tape (make sure you have the drivers for the backup drive if applicable, before doing the os re-install!).
The Microsoft Technet site has some useful articles on doing this.
If you have other domain controllers for this domain then its a different scenario altogether.
Hope this helps! |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in
