[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 707
  • Last Modified:

2008 DC rename

Using computer management I renamed a current 2008 dc to a previous 2003 DC after I just demoted it. I also used the IP address of the old demoted 2003 dc and made it the IP on the 2008 dc, (I gave the 2003 dc an unused different IP).

I manually deleted the 2008 previous computername from the dns records. Everyting seems fine BUT in AD sites and Services the 2008 DC has its previous name, I manually replicated a few times and no changes.

I researched further and realized I should have used netdom command to rename DCs. Anyway, using the netdom command and doing a dc query I see the name of the 2008 DC as its old name as well. On the 2008 DC in ADSI edit on the OU=Domain controllers properties the vaule for the msDS-AdditionalDnsHostName is the new name (old 2003 dc name) that I want it to be.

So, clearly some things are not being replicated/changed properly.

What should I do to make sure the 2008 DC has the name I want it to be?
  • 4
  • 3
1 Solution
Rename it back to what it was first
Cross your fingers that things are not screwed up
Wait a few days after the demoted one is gone
Use the manual Metadata Clenaup process to verify that nothing still lingers with the old name refering to the old machine.
When everything seems clean then you can rename to new one to the old name.
tolinromeAuthor Commented:
I'm tempted to rename it what it was first but those DNS records are gone now and everything seems to be fine as in "no one is saying anyting is down or complaining", which in this company would happen in 1/2 second. I dont want to somehow makeit worse, if possible.

In theroy I think everyting I did made sense though...

what if I do the following:

1. Add the name of the dc that I want using the netdom command
    C:\>netdom computername serverdc1.lab.local /add:

    Successfully added serverdc21.lab.local
    as an alternate name for the computer.

   The command completed successfully.

2. Make that computername primary

3. Reboot the DC

I got all that information from here

Well I understand the people screaming in 1/2 a second  :-)

The thing that worried me was that you said you renamed right after demoting the other DC.  That should never be done that quickly,...AD does not respond to changes that quickly,...I would have waited at least a day just to be safe.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

tolinromeAuthor Commented:
I know, I agree. Unfortunateley I cant go back.

Do you think what I suggested will work (using the netdom command)?
Sounds correct,...but I have never done that.  I have never renamed a DC.  I have always created temp DCs,..took down the old,....introduce the new,...remove the temp,...and even when doing that I never re-used the same name.
Darius GhassemCommented:
You should have used the netdom command to rename a DC.

Here what you can try first rename DC back to other DC name. Run netdom to rename DC.

Do you have other DCs?

You should have other DCs. You should demote this DC you renamed without doing it the proper way then repromote. After you run a metadata cleanup
You should have other DCs. You should demote this DC you renamed without doing it the proper way then repromote. After you run a metadata cleanup

That would be my approach if in a similar situation.   This means that I also would never be in a position where I didn't have at least two DCs.  If I got hired at a company with only one DC,...I would be impossible to live with (or just get fired) until they spent the money for a second dedicated machine for a DC.
tolinromeAuthor Commented:
yes I have other DCs - two 2008 dcs and two 2003 dcs (4 in total).

so the majority says:

1. rename it to the previous dcname (using netdom)?
2. demote it.
3.change computer name to the dc name I want (old 2003 dc name) not using netdom.
4. make it a DC.

Does this sound like the best scenario? I just want to be sure since I dont want further DNS problems.

Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now