New 2008 Domain Controller File Server Same Name as Old 2003 Domain Controller
Posted on 2011-02-17
Need to replace aging/dying 2003 standard domain controller/file server. It is one of several remote DCs we have at remote sites. The existing DC is still operational at this site and appears to be replicating sysvol correctly to the main DC at HQ. It also acts as a file server with offline files caching enabled on the clients. For this reason my concern is to keep the same name domain controller, otherwise there will be huge headache with users not accessing the realtime data and not working off the cache.
Is it acceptable practice to keep same name of DC?
What are the steps to do this as smoothly as possible, transition from the old DC/file server to the new DC/file server with the same name.
Also, the new DC is Server 2008 R2, and it would be the the ONLY 2008 server on our domain for a while. All other DCs are running Server 2003 SP2.