removing problematic Win2k DC from 2003 forest

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

hi,

I have a possible job with a small lan, about 40 seats,
and there are several issues on site from what I hear.

Originally they had a simple WIn2000 SP4 box running AD.
A year ago, I installed a new Win2k3 server, SP1, (no R2 on this)
and replication, DNS, AD, and all else was fine.
Moved the 5 FSMO roles, to the new server, left the old Win2k server
online as a secondary DC

For whatever reason, they have had the original Win2k server turned off
for 6 weeks, due to crashed raid. Hard to really tell.

There is a single disk running the system on the win2k box however,
so I can get the thing to boot up.

I want to demote the Old win2k server from the AD, rebuild and reinstall from scratch. If I can't demote the old server using dcpromo,
what pitfalls are there around removing the AD entries using
NTDSUTIL on the new (win2003 server) ?

OF course I've read up on NTDSUtil and etc, but as always, I like
to hear from the guys and gals in the trenches before doing this
sort of thing.

Thanks
Jason K
.