Re: Sites and Services question

When you remove the DC from the site, you don't have to remove the site from AD. It can stay there and then AD will automatically configure the next closest site to cover that site within DNS so clients will start flowing over to the next closest site.

So assuming your site metrics are configured properly things should be good and the sites that the machines are in will remain the same, only the reported site for the DC will vary.

So for example, say you have a hub and spoke configuration, if you remove a DC from a spoke, the hub DCs should automatically start covering the spoke site assuming you configured the site link between the hub and the spoke properly.

Once you remove the DC, start using nltest and nslookup to verify what is covering that site then.

joe

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm


W C Hull wrote:
We have a Domain Controller located in an office out east and although the office is going to remain open we can no longer justify a domain controller be located on site. When we shut down the DC we want to take the addresses for the offices and move them to another DC in an adjacent state. Here is the issue......

We currently use the site code value in the logon script to determine proxy settings for the office. In the current environment we have two separate site codes and set the proxy settings based on site code detected. If we consolidate one site into the other then we will end up with two different proxy settings but only 1 site code. Is there any way to move this address range from one DC to another and still maintain separate site code values in Active Directory?

Any insight would be appreciated.

Thanks!


.

Loading