Atte,
This is a pretty straight forward process, but there are several potential
road blocks along the way.
I would install WIN2000 Server on the new hardware. I would then run
dcpromo on the new hardware so that it becomes "an additional Domain
Controller in an existing domain".
I would then make sure that DDNS is installed on this new hardware.
I would then install DHCP on the new hardware. Look into dhcpexin for
moving the database over to the new hardware. Please see the following
link:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/dhcpexim-o.asp
I would then move over any services that might also be running on the old
hardware to the new hardware.
I would consider using xcopy to copy any user files/folders that might exist
on the old hardware to the new hardware.
I would transfer the five FSMO Roles ( assuming that there is only one
domain / tree / forest in your environment with only one Domain Controller )
from the old hardware to the new hardware. Please see the following link:
http://support.microsoft.com/?id=255690
I would make sure that the new hardware is also a Global Catalog Server.
Please see the following link:
http://support.microsoft.com/?id=313994
You could then dcpromo the old hardware to gracefully ( let's hope! ) remove
it from being a Domain Controller. If that fails then take a look at
ntdsutil to do a metadata clean up ( please see this link:
http://support.microsoft.com/?id=216498 if necessary ).
I might suggest to you that you keep the old hardware around as a second
Domain Controller - unless the old hardware is really flacky. It is a very
nice thing to have two Domain Controllers ( and is a Best Practice ).
HTH,
Cary