Renamed only DC - cannot name it back - cannot access ADDC

Chris Krun 21 Reputation points
2022-03-10T19:35:24.857+00:00

Due to extenuating circumstances, our only DC was forcibly renamed and now the AD is broken, when trying to follow the solution below:

https://social.msdn.microsoft.com/Forums/en-US/09f6599e-8ec3-4f4d-ba4e-ecaa55578080/renamed-dc-ad-broken?forum=winserverDS

I get the message: The Specified Domain either does not exist or could not be contacted.

While trying to post this question, I came across the following:

https://social.msdn.microsoft.com/Forums/en-US/f801a32a-6796-4a83-90ad-f210f11478d1/help-renamed-primary-dc-and-ad-is-broken?forum=winserverDS

I will try that tomorrow night. Wish me luck!

If none of this works, what are my options? Start from scratch and recreate the whole AD, Users, etc.? System backup was not successful.

TIA!

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,008 questions
{count} votes

Accepted answer
  1. Thameur-BOURBITA 32,606 Reputation points
    2022-03-10T21:45:53.413+00:00

    Hi,

    Renaming a domain controller is not recommended.
    If you have only 1 DC , try to restore it from a backup. If the Restoration is not working , I recommend you to start from scratch.

    Once you fix this issue , you should promote a additional a domain controller .It's recommended to have at least two domain controllers per domain for high availability.

    Please don't forget to mark helpful reply as answer


3 additional answers

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP
    2022-03-10T20:03:58.06+00:00

    Sounds good, let us know.


  2. Chris Krun 21 Reputation points
    2022-03-15T18:32:51.237+00:00

    I was able to restore from a backup. I will put the old server on the network, and then the current server (with the broken AD) should find it and authorize its name change?

    0 comments No comments

  3. Dave Patrick 426.2K Reputation points MVP
    2022-03-15T18:35:58.207+00:00

    No, don't bring up the old one. I'd check health (dcdiag, repadmin tools) and if all is good you can stand up a new one for replacement with the desired naming.

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new one, patch it fully, license it, join existing domain, add active directory domain services, promote it also [making it a GC][1] (recommended), [transfer FSMO roles over][2] (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

    --please don't forget to upvote and Accept as answer if the reply is helpful--