Re: Corrupt Active Directory 2003
- From: Narnian <Narnian@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 28 Jan 2008 17:05:02 -0800
Woo Hooo!
You are the man!
I don't understand what those parameters are, but that subtle change made
the difference. I followed your instructions to the letter and now I'm back
in business. I'm SO glad I don't need to start from scratch.
I went out and bought a new UPS drive, so I'm going to run a system backup
RIGHT now.
With the lab configuration I have, would there be value in adding Active
Directory to the web server in case something like this happens again, or do
you think the standard OS backup with system state is sufficient? I didn't
put Active Directory on the web server previously because it has select ports
open to the internet and I wanted to avoid and security risks.
"Jorge Silva" wrote:
At the moment I don't have a machine to test those options, try the.
following:
Do a backup of the original NTDS.dit database, and work on the other one:
To perform the integrity check, start a command prompt, type the following
command (including the quotation marks), and then press ENTER:
esentutl /g "path\ntds.dit" /!10240 /8 /o
To repair the database, type the following command (including the quotation
marks), and then press ENTER:
esentutl /p "path\ntds.dit" /!10240 /8 /o
if repair is successful, delete all the files inside NTDS folder (.log and
.chk)
Reboot the server.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
- Follow-Ups:
- Re: Corrupt Active Directory 2003
- From: Jorge Silva
- Re: Corrupt Active Directory 2003
- References:
- Re: Corrupt Active Directory 2003
- From: Jorge Silva
- Re: Corrupt Active Directory 2003
- From: Jorge Silva
- Re: Corrupt Active Directory 2003
- Prev by Date: Re: w2k3 and XP media center sp2
- Next by Date: Re: Utility to append AD user info?
- Previous by thread: Re: Corrupt Active Directory 2003
- Next by thread: Re: Corrupt Active Directory 2003
- Index(es):
Relevant Pages
|