Removing DC that is not online anymore

I promoted a server to DC and renamed it without demoting it first. Now I have the old name all over the domain. How can I remove it properly?
Thomas NSystems Analyst - Windows System AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joseph MoodyBlogger and wearer of all hats.Commented:
https://support.microsoft.com/kb/555846?wa=wsignin1.0

You will need to check the FSMO roles and perform a metadata cleanup. If your IP changed, ensure that clients have updated dns settings.
0
Joshua GrantomSenior Systems AdministratorCommented:
Here's another TechNet article on metadata cleanup that is a little newer. This can be done through the GUI or command line.

Need http://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx#bkmk_graphical
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Joshua GrantomSenior Systems AdministratorCommented:
You can also used the script that is referred to at the bottom of the TechNet article I supplied.

https://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3
0
Thomas NSystems Analyst - Windows System AdministratorAuthor Commented:
I try to delete it in users and computers and it tells me it cannot be deleted. It says "....The specified module could not be found" but it still in the console. Any suggestions?
0
becraigCommented:
To clean up server metadata by using Ntdsutil

Open a command prompt as an administrator: On the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, provide Enterprise Admins credentials, if required, and then click Continue.

    At the command prompt, type the following command, and then press ENTER:
    ntdsutil

    At the ntdsutil: prompt, type the following command, and then press ENTER:
    metadata cleanup

    At the metadata cleanup: prompt, type the following command, and then press ENTER:
    remove selected server <ServerName>

Also if you take a quick look at the like I posted, you will find it is very extensive with a lot of steps to try including the others links posted subsequently.  It might be worth it to take a look and head to the 2008 section and give it a read.
0
Joshua GrantomSenior Systems AdministratorCommented:
That is not the proper way to remove it. Please read the articles on removing orphaned domain controllers.
0
Rob StoneCommented:
Other than following the metadata cleanup KB here are my thoughts.

Check again when replication has occurred (unless you are checking AD on the DC you made the name change on).  Refresh the mmc console after replication too.

I just executed what you have said in a test lab on 2008 R2, there was a warning saying this isn't the correct way to rename a DC but I went ahead and changed and rebooted. The server name changed in ADU&C and ADS&S with the old name being removed from everything except some SRV records in DNS.

If the metadata cleanup doesn't work I'd suggest taking a quick backup and restoring to an isolated test lab to play with it there.  VMware Workstation or VirtualBox are good for this if you don't have the capacity on a server estate.
0
Thomas NSystems Analyst - Windows System AdministratorAuthor Commented:
This article says to do it that way:

Need http://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx#bkmk_graphical

So dont go in and hit delete?

I tried using ntdsutil using this article:

http://www.petri.com/delete_failed_dcs_from_ad.htm

but it does not see the server
0
Thomas NSystems Analyst - Windows System AdministratorAuthor Commented:
I tried becraigs plan but I get this error:

C:\Windows\system32\ntdsutil.exe: metadata cleanup
metadata cleanup: remove selected server "server"
Binding to localhost ...
Connected to localhost using credentials of locally logged on user.
LDAP error 0x22(34 (Invalid DN Syntax).
Ldap extended error message is 0000208F: NameErr: DSID-031001F7, problem 2006 (B
AD_NAME), data 8350, best match of:
        'CN=Ntds Settings,server'

Win32 error returned is 0x208f(The object name has bad syntax.)
)
Unable to determine the domain hosted by the Active Directory Domain Controller
(5). Please use the connection menu to specify it.
metadata cleanup:
0
Joshua GrantomSenior Systems AdministratorCommented:
I'm sorry, yes that is how you remove it using the GUI, but have you verified which server is holding the FSMO roles? How many DC's do you have?
0
Thomas NSystems Analyst - Windows System AdministratorAuthor Commented:
This worked after clicking on it a few times. Weird it didnt work right away but thats Windows. Thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.