Renaming a Domain Controller Best Practices

LULU-6701 341 Reputation points
2024-02-28T20:30:25.87+00:00

Hello, What are the best practices for renaming a domain controller?

Windows for business Windows Client for IT Pros Directory services Active Directory
0 comments No comments
{count} votes

Accepted answer
  1. Thameur-BOURBITA 36,261 Reputation points Moderator
    2024-02-28T21:39:44.0433333+00:00

    Hi @LULU

    Before renaming domain controller , you should check if there are another application can be impacted. If all applications instaled on domain controller supports name modification you have two use case:

    1. If you have another domain controller in same domain you can perform the following steps:
    • If the target DC hosts FMSO role , move them to another Domain controller
    • Demote domain controller and convert it to member server
    • Rename Server
    • Promote it again as domain controller
    • If the target DC hosts FMSO role , move them again to this Domain controller
    1. If you have only one domain controller in this domain , you can perform the following steps:
    • Promote another domain controller in temporary machine
    • Move FSMO roles to temporary Domain controller
    • Demote domain controller and convert it to member server
    • Rename Server
    • Promote it again as domain controller
    • Move FMSO roles them again to this Domain controller
    • Demote temporary Domain controller

    Please don't forget to accept helpful answer

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Q&A Assist
    2024-02-28T20:30:25.8733333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To rename a domain controller, Microsoft recommends that you follow these best practices:

    1. Ensure that the domain controller is running the latest supported version of Windows Server for your organization, as recommended in the "Securing Domain Controllers Against Attack" article.
    2. Make sure that the domain controller is not a read-only domain controller (RODC), as RODCs cannot be renamed.
    3. Verify that the domain controller is not a global catalog server, as global catalog servers cannot be renamed.
    4. Ensure that the domain controller is not hosting any operations master roles, as these roles cannot be transferred to a renamed domain controller.
    5. Verify that the domain controller is not running any applications or services that rely on the computer name, as these applications or services may not function properly after the rename.
    6. Follow the procedures outlined in the "Core network components" article to rename the domain controller.

    References:

    0 comments No comments

  2. Philippe Ferrucci 0 Reputation points
    2025-05-07T09:35:33.06+00:00
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.