Active Directory server integrity after a crash

Recently I asked about checking the integrity of SQL and Exchange databases after a crash that results from a sudden and absolute power loss.  With a server running Active Directory however, is there anything to check after such a crash other than event logs and drive integrity?  
Who is Participating?
Mike KlineConnect With a Mentor Commented:
You can use ntdsutil to check the integrity

step 7 is where you want to start

***from the link
Type ntdsutil and then press ENTER.

At the ntdsutil: prompt, type files and then press ENTER.

At the file maintenance: prompt, type integrity and then press ENTER.

If the integrity check fails, the likely cause is that an error occurred during the copy operation in step 6.c. Repeat steps 6.c through step 9. If the integrity check fails again:

Which version and type of Windows Server are you using?

You knew what I was getting at.

Was going to lead him through OS specific procedures for the ntdsutil.

Cheers you rascal. =D
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

james_axtonAuthor Commented:
ok123, for this example let's use Windows Server 2003.  Am I set to run mkline's instructions then?
ok123jumpConnect With a Mentor Commented:

Yep. He gave you the MS procedure for Server 2003.

If you are running Server 2008, use this one:

That should answer your question. ntdsutil.

james_axtonAuthor Commented:
This is in addition to checking event logs and drive integrity?  If all three of those items pass, the server suffered no errors during the crash?
Mike KlineCommented:
yeah if all are ok no issues; it is rare that you have an issue with ntds.dit
Short of comparing snapshots of the Active Directory (before and after), we can't actually say whether or not it suffered damage - there can be internal code issues after a severe crash like that. R/W operations can go awry when disrupted midstream.  

These checks will eliminate 95% of all of that errors that might have occurred during the crash. In the future, you should have a scheme in place where you take periodic snapshots of the Active Directory and store them on a storage drive somewhere else. If you ever experience a devastating crash, you can always recall the last prior snapshot.
james_axtonAuthor Commented:
Thanks to both of you!  This was very helpful.  I doubled the points and will split them.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.