Thanks for your help. HP replaced the motherboard. Everything is sweet. My server is backup and humming. Just for interest, I did restore the system state to another machine. Worked and at least allowed my users could authenticate and access other network resources. For anyone who restores the system state of a DC to different hardware, dont bother installing the drivers for the hardware until after the restore. Process: 1) I installed Windows 2003 on the hardware; 2) Installed drivers for hardware windows missed (it was a white box machine I had lying around); 3) restored system state of DC that went down; 4) System state had hardware drivers of old DC, windows had to re-recognise all hardware.
Step 4 wasted about 30-45 mins of my time. Skip 2 as you will do it again in 4, if u are rushed for time. Cheers all. On Mon, Jun 23, 2008 at 10:44 PM, TNN <[EMAIL PROTECTED]> wrote: > Thanks guys. Any gotchas to watch for ? > > On Mon, Jun 23, 2008 at 10:13 PM, KenM <[EMAIL PROTECTED]> wrote: > >> If you only had a single DC I would recomend to try and recover the box >> first. If that does not work rebuild the same server with same name and >> restore the system state backup. If that is not an option you will neeed to >> build a new server with the same name and follow this KB >> http://support.microsoft.com/kb/263532 >> >> Once you get everything back up and running the first thing you need to do >> is get another DC. >> >> >> >> >> >> On Mon, Jun 23, 2008 at 3:49 PM, TNN <[EMAIL PROTECTED]> wrote: >> >>> Hi >>> >>> My Domain controller (Win2003 R2 SP2) has died. Is there anyway to make a >>> member server, the new DC? I have the system state data backed up? >>> >>> TIA >>> >>> >> > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
