Oh man am I in trouble.\nIn an effort to simply add another drive to my server in order to fix an\nexchange 55 database corruption, I installed the nearest drive under the\nimpression that I would just format it and use it.\nIt turned our to be a cloned drive from a couple years ago and installing it\nremapped my drive letters! I was able to correct that with a KB article and by\nbooting into Directory restore mode I was able to copy the "system" hive to\nanother machine, make the changes by editing the registry "DOS drive" entries\nput the hive back where it came from (renaming the original one) and got the\nletters back. whew!\nThen it seems that all the references to NTDS were to the "H" drive, so I\nwent through the registry and changed all those back.\nNow I am left with what seems to be a corrupted NTDS.DIT file. I used\nNTDSUTIL and it says there are inconsistencies and can't fix it.\nI renamed the original and copied one I found in the system32 directory\nfiguring I was hosed anyway and what did I have to lose. Well the error messages\nstopped but the machine sits there at the "preparing network connections"\nscreen. Thats better right?\n\nNow what can I do? I went from bad to worse! There are two other DC's and I\nthink they are all GC as well. I have another cloned drive from a year ago\naround that I was thinking I could pull the NTDS.DIT file from but I think it's\ntime to get someone to protect me from myself.