[ZrOuT]

2003 standard server, SP2
raid 1 - one disk failed, the other is now not booting , the windows loading screen never goes away
server was doing DNS, DHCP and Print serving, that's about it.
It held most of the FSMO roles.

There are multiple other DCs on the domain so I'm "ok" for now.

I have system state backups available that are few days old

Does this sound like the best route for success?
- reinstall 2003 server on new disks
- update it to SP2
- name it the same as before
- do not join it to the domain
- restore system state
- reboot

and then what happens? I am assuming the AD will be recovered as will DNS and DHCP? (after some period of synchronizing with the other DCs).

What about the print server? Will that be back or am I stuck redoing that either way?

Any better options?

[Ossian]

Your strategy should work -- non-authoritative restore will cover AD and DNS
DHCP should be OK too -- may be some issues with leases clashing but I presume another DHCP server has a split scope so will not issue an overlapping address

System State should restore the print server unless any printers use files not stored in the C:\WIndows directory structure.

[ZrOuT]

I made a temp DHCP server which I'll turn off when this goes live

will the new server (named the same) retain its FSMO roles after the system state restore? I would imagine it would, but just checking the obvious.

[Ossian]

Yes, it will retain FSMOs