We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

Steps necessary to decommission a DC from one domain and then add it as a DC to another domain

chris3174
chris3174 asked
on
Medium Priority
658 Views
Last Modified: 2012-08-13
What are the complete steps to decommissioning a server from domain A (including removing DNS and site replication routes) and then adding it as a domain controller in Domain B? The documentation on the DC says that it does not hold any FSMO roles but what are the steps to confirm?
Comment
Watch Question

tigermattSite Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011

Commented:

You can confirm the FSMO roles the server holds by going through the instructions for transferring the FSMO roles, at http://support.microsoft.com/kb/324801. For each role, you can note the current role holder (just don't press the 'Change' button, and you won't make any changes).

You'd need to ensure you also have another Global Catalog DC somewhere on the network, and that you also have another DC running the DNS Service.

If all that is true, you can go to the DC you wish to move and run dcpromo. Follow the prompts to demote the server. This will drop it back to a Member Server, and should automatically delete any replication links and so on from the domain.

Then, you'll need to change the server's domain membership so it is a member of Domain B. You can then reboot, log in to the server (now on Domain B) and then re-run dcpromo, this time to promote the server as an additional DC.

-Matt

Author

Commented:
what about the fact that its also a DNS server?
Site Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011
Commented:

That won't be a problem assuming you have other DCs which are also DNS Servers on the network. Your DNS zones should be AD-integrated, so every DNS Server should host the same copy of the DNS zone.

The only point of note is to ensure that all servers, workstations and DHCP scopes are updated so that they don't refer to the demoted server for DNS. That would be the only issue here.

-Matt

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.