Migrating services to a new DC

[Craig]

I have an old NT4.0 box upgraded to W2K w/AD A new server
is being added to the domain this week as a DC also. The
original DC will be retired as soon as all the services
have been migrated to the new DC.

Looking for directions on moving DNS and DHCP...

How do I go about migrating services without causing any
problems for users or myself?

Thanks in advance,

Craig

 

[Adam Wood]

I have an old NT4.0 box upgraded to W2K w/AD A new server
is being added to the domain this week as a DC also. The
original DC will be retired as soon as all the services
have been migrated to the new DC.

Looking for directions on moving DNS and DHCP...

How do I go about migrating services without causing any
problems for users or myself?

DNS: standard or AD integrated? If AD integrated, create the new DC
also hosting the zones, reconfigure all clients (ie change the DNS
server settings that come from DHCP), and then reture the initial
server. If not AD integrated, make the new server a secondary for the
zones, then make it authoritative. You can change the clients any point
after bringing up the new DC.

DHCP: depends on how much slack you have on the subnet. Essentially have
both running in parallel with smaller ranges than at present then stop
the initial one doling out new addresses before remocing its range and
increasing the range of the replacement.

Also remember to transfer all of the Active Directory FSMO roles and
create another GC before retiring the initial DC.

 

[Craig]

Adam,

Thanks for the pointers, I'm running AD integrated DNS, so
the plan will be to install DNS on the new server and
duplicate the content of the old server on the new.

DHCP has plenty of room to sustain two scopes in the same
address space, just a matter of whittling down one and
increasing the other until the scope has been completely
moved.

Thanks again,

Craig