replacing a DC after one blue screens

[bookouri]

I have two DC's and yesterday one of them blue screened and I havnt been able to get it to boot again. It was within a few days of being replaced though so I have its replacement in place and ready to configure. I want to configure the new server with the same name and IP addresses, etc. that the old server had. I dont have the option of gracefully demoting the old DC. What I'm wondering is if there could be any problems with bringing up the new machine with the same name and all as the old dead machine? There's two DC's on this domain, both of them running their own dns and pointing to each other's dns. The one DC that is still alive was the first DC in the forest.

Does anybody know of any reason why this wont work or have any other suggestions about getting this new DC in place?

thanks

 

[technome]

Since the problem DC has not been demoted,if you use the same name on the new machine you will have issues due to the old and new machine having different SIDS. You could do a metadata cleanup with ntdsutil to remove the problem DC from AD.

http://technet2.microsoft.com/windo...5e8c-4a5c-9f66-4a486a7114fd1033.mspx?mfr=true

"The one DC that is still alive was the first DC in the forest"
Check all the AD roles are on this server before cleanup. You may need to seize roles (unlikely, but check)

Make sure the problem DC is disconnected from the network and formatted before reconnecting it to the network.

It just might be easier to figure out the blue screen, then demote it.

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[bookouri]

Yeah, ill probably keep at it until i get it back on line and then do demote it. I rather not take any chances of screwing up AD...Ive got another DC up and running so at least I have some redundance if anything else happens..

thanks

 

[technome]

Try safe mode, if it works delete all unecessary drivers, you need the keyboard, mouse , network, it may startup after that. If not, try a an over the top "repair" install, this will bring you to the default device drivers, you may need to have the NIC driver on the hard drive or on a CD to get connected to the network.
Good luck

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[bookouri]

i guess im down to trying some kind of OS installation on top of the old OS. I still havnt managed to get into safe mode.. just up to the starting windows screen and then an automatic reboot...

 

[bookouri]

I finally installed a new instance of Win2k on another drive and now i can boot the machine in the new instance. I restored a backup of my original winnt directory taken before the DC crashed but i still cant boot the original win2k instance. My boot.ini shows me both instances and i can select the old instance and the machine will give me the starting win2k status screen and progress bar, but then the machine reboots itself when the bar reaches 100%. Can anybody give me some idea where to go from here to try to get that old instance to boot? I cant get into safe mode with the original OS instance. All the boot files I know of seem to be in place. I dont have any idea what's missing/bad/corrupted and causing the machine to reboot itself.

thanks for any suggestions

 

[technome]

In the original instance's safe mode I would delete ALL hardware in device manager, remove or disable any software which is normally resident, reboot.


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[Freestone]

Have you tried booting into the Recovery console from CD? From there I would try running chkdsk, and I think the fix switch is /f, so chkdsk /f

 

[Freestone]

Sorry, the /f switch is not valid in Recovery console chkdsk. /r and /p are the accepted parameters. Review this to see what these two switches do before using them:

http://support.microsoft.com/kb/229716

 

[bookouri]

yeah, first thing i usually do to fix stuff is boot to recovery console and run checkdisk.. this time it didnt work.. even tried the fixboot and fixmbr but none of them had any effect at all. I still cant boot into safe mode or anything.. just a starting windows and then the machine reboots itself... im baffled by this one.

 

[bookouri]

Well, I've given up on resurrecting the dead DC. Since I cant get it back online and demote it what do i have to do to clean up ad to get rid of it? If i just remove its account from ad through users and computers what else would i have to do to get rid of references to it so that the other domain controllers will stop trying to replicate with it, etc..

 

[Freestone]

How to remove data in Active Directory after an unsuccessful domain controller demotion

http://support.microsoft.com/kb/216498