I would try to promote a second DC--it *might* be able to initialize a healthy instance from the existing single DC--then add yet another DC for redundancy, and demote the bad one. If that doesn't work, the DIT is quite possibly too messed up for a standard migration to work either. Try an ntdsutil repair; if that doesn't work, restore from backup. Or, skip all the above and contact PSS.
--Steve On Tue, Oct 9, 2012 at 10:27 AM, Jimmy Tran <[email protected]> wrote: > As I was doing adprep /forestprep on an existing windows server 2003 domain, > I was getting some errors about checksum mismatch for ntds.dit. I’ve done > everything I can do to get past this but was not successful. The latest > backups are most likely backups of the corrupt ntds.dit file as well. What > are my options here? There is only one W2k3 server onsite. > > > > Create a new domain and migrate things over? > > Can I add a new W2k3 box and seize the roles? I don’t think this is a valid > option. > > > > Any ideas guys? > > > > Thanks, > > > > Jimmy > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
