AD Corruption

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello all,

My client has a 2000 server serving a small network of 10 local users and 3
remote users (via TS). It is the only server in the AD. It encountered the
exact LSASS error listed at the top of KB Article no. 258062. My users could
not log in; neither could the Administrator. I rebooted into Directory
Services Restore Mode, and I went through all of the steps listed (verifying
the files and permissions, doing integrity and semantic checks on the
database, and doing an offine defrag of the database). I went through Step
12, the offline defrag.

Ntdsutil reports that there are still too many references (?). However, my
users can now log in. Should I continue with the lossy repair? Should I
create a new AD by demoting and then promoting? If so, is it possible to use
ADMT (or something) to make it easier? And, oh, before you ask, there's no
backup.

Thanks in advance,

-Bruce D
 
create a new forest and migrate all the existing resources to the new one
using ADMT (it will be very simple for you as you have a small number of
users).
It's just now worthing to keep a corrupted AD database.
 
Back
Top