Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

One of the main domain controllers harddisk failed so I had to replace it and reinstall Windows Server 2003 all over again from scratch. Luckily, I have another domain controller layer around.

Now the problem is that I could join the domain because of "The specified user already exists". I went to AC Users and Computers on the other domain controller to delete the old computer name but I received "The object SER1 (or some of the objects it contains) cannot be deleted because: Access is denied" note that I logged in with a Enterprise admin privileges. This is really weird.

Did some internet searching and found that I have to delete the old name using ADSI Edit (adsiedit.msc) but to no avail. I still get Access is denied.

Kindly advice. I am really getting frustrated and I need to use the same old name on the server.

Thanks in advance SZ

share|improve this question
add comment

3 Answers 3

up vote 3 down vote accepted

You want to go thru the Forcing the Removal of a Domain Controller procedure as specified by Microsoft. You can't just delete the old computer object and have things work properly.

You can't do the "dcpromo /forceremoval" portion because the old computer is already gone, so just ignore that part.

The only part you'll really need to do is the NTDS metadata cleanup portion of the procedure, so you might just skip to that.

share|improve this answer
    
Thanks but the forcing removal did not work. I don't know what is the source if the problem here. I even tried running this vbs script microsoft.com/technet/scriptcenter/scripts/ad/domains/… and while it shows it's a successful process I still see the old domain controller –  SZayat Jul 21 '09 at 16:04
    
What do you mean by "the forcing removal did not work"? Are you receiving an error message when attempt to do the metadata cleanup from NTDSUTIL? –  Evan Anderson Jul 21 '09 at 19:10
    
I didnt know how to use "metadata cleanup". Sorry if i miss informed you earlier. –  SZayat Aug 2 '09 at 5:20
add comment

Remove the replication link for the server in AD sites and services. Problem fixed. Try deleting again.

share|improve this answer
1  
Can you add more explanation of how and why this fixes the problem. –  ChrisF Jan 28 '13 at 23:33
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.