Removing GC server from windows 2003 domain, from a branch office which runs on a different subnet.
Hello,
We have a windows 2003 SP1 as one of the GC servers in a branch on a different subnet. This server has DNS and DHCP enabled. Now we want to remove this server from the domain net work. What are the steps and precautions needed for this to make.?
Our head office has 2 domain controllers and one of them is already a GC server. So I assume that I do not have to shift the GC role from the branch server. Also we have exchange 2003 in place in the head office. The data link between the branch office and the head office is 4Mbps over the fiber.
We have a windows 2003 SP1 as one of the GC servers in a branch on a different subnet. This server has DNS and DHCP enabled. Now we want to remove this server from the domain net work. What are the steps and precautions needed for this to make.?
Our head office has 2 domain controllers and one of them is already a GC server. So I assume that I do not have to shift the GC role from the branch server. Also we have exchange 2003 in place in the head office. The data link between the branch office and the head office is 4Mbps over the fiber.
ASKER
Once done these, will there be any metadata of this server in any of my head office's domain controllers? and also in my exchange 2003 server?
Here is a link
If you run DCPromo and there are no errors there will be no metatdata to cleanup in AD.
You will want to make sure this DC does not hold any roles.
netdom /query fsmo
I would also suggest to make all of your Domain Controllers GCs.
You can move the DHCP scope to your head office using netsh
http://technet.microsoft.com/en-us/library/cc740017(WS.10).aspx
If you run DCPromo and there are no errors there will be no metatdata to cleanup in AD.
You will want to make sure this DC does not hold any roles.
netdom /query fsmo
I would also suggest to make all of your Domain Controllers GCs.
You can move the DHCP scope to your head office using netsh
http://technet.microsoft.com/en-us/library/cc740017(WS.10).aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you can demote the DC without any preparation .AD demotion process will handle everything.But you can
do the following steps manually:
Transfer FSMO.
wait for replication.
demote the AD.
unauthorise the DHCP.
uninstall DNS, DHCP
if you want to replace the domain controller then:
Transfer FSMO.
wait for replication.
backup your DHCP database ( using the comman netsh dhcp server export dhcpdb all)
demote the AD.
unauthorise the DHCP.
uninstall DNS, DHCP