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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Which version and type of Windows Server are you using?
Mike KlineCommented:
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:


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial

You knew what I was getting at.

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

Cheers you rascal. =D
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

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

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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.