2003 DC replacement

The easiest route is a full restore to new hardware.
1. Install 2003 on a new server (do not connect the NIC to your production network).
Choose a server that is not a FSMO role holder. Setup as a stand-alone workgroup server. Call the server the same name, same IP, same drive letters. I would recommend booting the new server from the 2003 media, do not use smart start.
2. Create a full backup of the existing server including the system state and restore it to the new server.
You probably would want to stop as many services as possible before the backup. Do not restart the services, shut down the server.
3. Connect the new server to the lan and boot it up. Verify that ad services are functioning on the new server.  Load the latest Hp SSD or drivers for 2003.
-Do not boot up the old server on the LAN unless something is wrong with the new one.
-Transfer the FSMO'S to this server or split them among two new servers after the second restore is complete.

The major advantages of this approach are;
-No need to make any changes on any work-stations, or reinstallation of any apps like exchange, sql.
-If something goes wrong with the restored server, the roll-back plan involves simple starting the old server back up.  

I like that plan too, but I've had little luck myself trying to restore a system from one piece of hardware to another piece of hardware, especially when hardware RAID is concerned.  I've always viewed backups (system state or otherwise) as disaster recovery, and not migration tools.  But that's just me.

ckratsch I hear you but do not agree...  Please dont get all defensive and pissed off...
I am speaking from personal expierience, in countless scenario's...

-Using my M$ recommeded and supported method works because the new server is already setup with the right drivers before the restore... The restore does not replace the disk controller drivers in use and thats why there is no "RAID doesnt start issue" with this method...
I've used it to restore from IDE to Raid Array's, Raid arrays to single disks.....you name it...


We only work with "real servers", like proliants etc... Maybe you've had these problems because of the funky uncertified or unsupported hardware you use...

Oh I'm not defensive or anything.  Everyone has their own methods.  I'm sure you've got more experience with this kind of situation than I do, and knowing that, I'm likely to attempt your option myself in the future.

The time I was thinking of was when I tried to do a restore from tape onto an empty array using ArcServe's disaster recovery method.  I understand (now) that that's different from what you're proposing, which is install a base system first, then restore data and system state from backup.

I still think of tape backup as disaster recovery though.  ;)

One other thing I forgot, for RLiberty - make sure you also change the Site Licensing server.  (I am finishing up a DC replacement myself right now, and forgot to do that myself.)

ckratsch Arcserve ....No wonder it didnt work :) Kidding... I like backup exec myself....
-Last week I used Ntbackup to accomplish the same thing.... The job was "replace old POC IDE 2000 single DC" with a new HP ML350 with a raid array...
Problem: 3rd party accounting app and integration with adobe 7 pro to generate pdf quotes and invoices must function on the new server to avoid very expensive 3rd party involvement...   Solution: Restore the existing clone/ide PDC to the new "real server" with Ntbackup...
-It worked fine, the clients apps function as before(except much faster), no need to involve the app provider although I had no clue about how it works or is integrated with adobe... Frankly... who cares :)

-If your backup had a DR rapid recovery feature that allows you to boot from a CD or diskettes and start a full restore....Look at the instructions... I'm 99% sure there will be a disclaimer like "you must restore to the same hardware"....

Both are viable answers to me. I like the restore idea, but what are you using to backup? We use Veritas BackupExec.