Repair Active Directory database when having Blue Screen Of Death 2E2

Hello,

The other day I experienced a Active Directory database corruption that preventing me to boot up my lab. Because this was a lab, I only had one RWDC, and one RODC, so I couldn’t demote it and promote a new one without losing all my AD infrastructure. You can repair the database with a few line in DSRM :

cd c:WindowsSystem32
NTDSUtil
Activate Instance NTDS
Semantic Database Analysis
quit

In more serious case, you may want to perform an integrity check and repair if needed (please condiser backup first) :

cd c:WindowsSystem32
#Analyze
EsenTUtl /g C:WindowsNTDSNTDS.dit
#Repair
EsenTUtl /p C:WindowsNTDSNTDS.dit
#Remove log files
del C:WindowsNTDS*.log

And then, to check your database is fine, you can use :

cd c:WindowsSystem32
NTDSUtil
Activate Instance ntds
Files
Info

If you want to prevent future BSOD like this one, you may want to havea look at this :

http://blogs.technet.com/b/askpfeplat/archive/2013/09/10/clarifications-on-kb-2853952-server-2012-and-active-directory-error-c00002e2-or-c00002e3.aspx

Leave a Reply