See link below:
http://www.petri.co.il/delete_failed_dcs_from_ad.htm http://support.microsoft.com/kb/216498 Z Edward E. Ziots Network Engineer Lifespan Organization Email: [email protected] Phone: 401-639-3505 MCSE, MCP+I, ME, CCA, Security +, Network + ________________________________ From: Dennis Rogov [mailto:[email protected]] Sent: Thursday, February 12, 2009 8:29 AM To: NT System Admin Issues Subject: Re: Windows 2003 wont boot up help!!! here is the update it appears its the controller that went bad on the system. The only FSMO role it contained was PDC emulator which i transfered over to the primary.... We dont have any NT 4.0 boxes so i dont think anyone was effected at least it didnt make it up to me... Last question now i need to remove the fault DC from the active directory domain.. Does anyone have a reference to the article on techet how to do that with the NTDSUTIL metadata cleanup? ________________________________ From: Ben Scott <[email protected]> To: NT System Admin Issues <[email protected]> Sent: Wednesday, February 11, 2009 8:21:30 PM Subject: Re: Windows 2003 wont boot up help!!! On Wed, Feb 11, 2009 at 4:29 PM, Dennis Rogov <[email protected]> wrote: > If i try to load a windows 2003 CD it freezes once it says loading windows at the bottom Hardware fault of some kind. Others have suggested the disk subsystem, but if it was the disk subsystem I would not expect the CD to puke at that stage. It's not really looking at the disk yet, except maybe to get the partition table. If the partition table was poison, Windows wouldn't even get to the point where it could complain about a particular file. (Disk subsystem = IDE/SATA/SCSI/RAID controller, physical disks, cables, disk backplane if any.) Faulty CPU, RAM, or motherboard can cause just about any kind of symptom in the world. You say it's a Dell. Download Dell's diagnostics and run the full suite. > ... dies when it tries to load acpitabl.dat file... That *may* indicate a problem with the motherboard. That file name must be short for "ACPI table", and ACPI is how the OS talks to the motherboard and main BIOS services. However, I'm reasoning on really weak evidence here, so I wouldn't put much stock in it. It could easily be something else, and the file name is just a coincidence. -- Ben ~ 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/> ~
