Currently we're running Windows 2000 Server which is our Domain
Controller and our general file server, as well as the host for DNS and
DHCP.

We purchased a new server which will act solely as a Domain Controller,
DNS and DHCP host, and a separate NAS which will be our file server.

We're requiring that the new Domain Controller retain the same hostname
and IP address as the one we currently have so we're not putting out
small fires across the network that may pop up when a client doesn't
see the domain controller any longer.

Before I go on an all-out hunt for a good white paper or best practice
- is there anyone here who's done something similar to this?  How would
you do this?  What is the best practice to ensure that once the cutover
from the old DC to the new DC and NAS that shared drives aren't lost
and the change is seamless to the user.

Is there a best practice to do this with a minimum of downtime (in
other words - can we avoid taking the system offline all weekend?).

Any advice would be appreciated.

Thanks in advance!

Couple of options for you to think about:

1) Use imaging software, like Ghost, to take a snapshot of the old server
and place the image on to the new hardware.
clean up and add/remove any drivers required
Do an inplace upgrade, by popping in the 2003 cd
This is quick, but can have problems from hardware being incompatable and
troubleshooting removal of old drivers. We've happily move a number of HP
servers accross this way in under six hours

2) Build a temp 2003 server, on a old workstation, make it a member of the
2000 domain then run /domainprep and /forestprep from the 2003 CD
http://www.petri.co.il/windows_2003_adprep.htm
Make the temp server a DC, and move all the FSMO roles accross to the temp
server http://support.microsoft.com/kb/255690/EN-US/. Once that's done, then
demote the old 2000 server, and remove it from the network by adding it to a
local workgroup. Build the new server as 2003, name it with the old server's
name and ip address. Make it a member of the now 2003 domain, run DC promo
and then take all the FSMO roles again. Once ou check the server isrunning
okay, then demote the temp server (dcpromo) and remove it from the network.

If DNS is AD integrated then it you don't have to copy the dns details
accross, just install DNS on all the DC's and wait until it replicates and
populates the DNS on the server. You'll have to re-set up the DHCP as that's
not stored in AD.
You'll need to re-create any shares on the new server to match the old 2000
one.
This is a fairly slow method, but gives you a clean 2003 domain and server -
best to do over a weekend.

A nice way to test this and do a couple of dry runs is to use www.vmware.com
or Ms Virtual server
Warning: make sure you have full, working backups of the server, including
system state, incase you need to roll back if you run into trouble.

HTH

NTBackup from different DAT Drives
WinXP Pro logging to Win2K server. Taking too much time.
Unlocking an in use Computer
Dynamic Disk with Hardware RAID-5
Problem with DNS resolution when W2K goes to internet.