blueoakmo
asked on
Moving Win2K DC between machines on same site
I am going to be moving a DC from one machine to another within an existing domain. Have setup domains, additional controllers, and member servers, but have never decommissioned a machine except during upgrades.
Besides making sure my other DC is updating AD properly, changing all operation master settings to the new server, and reassigning the DNS setting for each machine to point to the new DC, are there any other steps I need to take to ensure all DC features are now using the new DC as the master before I permanently remove the existing DC?
Hope this isn't too easy.
TIA
Besides making sure my other DC is updating AD properly, changing all operation master settings to the new server, and reassigning the DNS setting for each machine to point to the new DC, are there any other steps I need to take to ensure all DC features are now using the new DC as the master before I permanently remove the existing DC?
Hope this isn't too easy.
TIA
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I would also make sure that any other functions, like DHCP, were running on the old DC are moved to the new DC.
ASKER
First, I apologize for being a little vague because I haven't put my hands on this system yet so I'm working off of some second hand info (I guess it's relevant that it's almost halloween because I don't know, yet, what "boogieman" is around the corner on this job :0 )
Thanks for the GC info, I planned on making sure that was set on the soon-to-be DC when I checked the AD replication. The system currently has 8 servers - one PDC, one BDC ( I know Win2K doesn't use these terms but this is what was forwarded to me) and 6 "other" servers. So I'm assuming at this point that the "PDC" is the master controller and the "BDC" is an additional controller and the "other" servers are member servers..
So with that being said, as long as the "BDC" is set as a GC, and AD has been replicating correctly, I can just change the DNS setting in the DHCP server (one of the member servers) to point to the new "PDC" and change the FSMO roles and I'm good to go?
Thanks.
Thanks for the GC info, I planned on making sure that was set on the soon-to-be DC when I checked the AD replication. The system currently has 8 servers - one PDC, one BDC ( I know Win2K doesn't use these terms but this is what was forwarded to me) and 6 "other" servers. So I'm assuming at this point that the "PDC" is the master controller and the "BDC" is an additional controller and the "other" servers are member servers..
So with that being said, as long as the "BDC" is set as a GC, and AD has been replicating correctly, I can just change the DNS setting in the DHCP server (one of the member servers) to point to the new "PDC" and change the FSMO roles and I'm good to go?
Thanks.
that sounds good to me