Solved

Can't join server back into domain after force demotion

Posted on 2008-06-13
7
650 Views
Last Modified: 2010-08-05
Dear experts,

Have a weird question. I have just force demote a secondary DC using the /forceremoval switch (normal dcpromo didn't work).Things went fine and the server has now become a standalone server (kicked out from the domain). I then logged onto another DC and found that this demoted DC still exists in the Domain Controller container, tried to delete but it says "DSA objects cannot be deleted".

OK no problem so far. I knew I need to do metadata cleanup so I followed the instructions given but when I reached the point where "list servers in site", the demoted DC does not exist. It only lists all the DCs that are still live but this demoted DC wasn't shown. However I still can't remove its entry in the Domain Controller container.

Is there anything I have missed, or need to do to remove the entry? I guess it is of no harm leaving it there but I just want it to be tidy.

Thanks in advance.
0
Comment
Question by:ormerodrutter
7 Comments
 
LVL 70

Assisted Solution

by:KCTS
KCTS earned 70 total points
Comment Utility
How long was it since it was removed - it might just be a latency issue. Clear any references to the machine in DNS/WINS and clear the caches.
0
 
LVL 23

Author Comment

by:ormerodrutter
Comment Utility
Yep true. Only did it this morning so I shall wait until Monday and check again. Thanks.
0
 

Accepted Solution

by:
frsupport earned 110 total points
Comment Utility
I had this issue a couple of days ago, if you follow this resolution using ADSI Edit it should solve your problem, it solved mine.

Error Message: DSA Object Cannot Be Deleted

http://support.microsoft.com/kb/318698
0
Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

 
LVL 1

Assisted Solution

by:himkal
himkal earned 70 total points
Comment Utility
hey you have clean the meta of the server from the ntdsutil  t

go to ntdsutil -- meta clean up

use this link to clean up
http://technet2.microsoft.com/windowsserver/en/library/012793ee-5e8c-4a5c-9f66-4a486a7114fd1033.mspx?mfr=true

and then try under domain in ntdsutil clean delete the server name u have forcefully removed.

then try to join it to domain it should work
0
 
LVL 1

Expert Comment

by:himkal
Comment Utility
I am sorry the second last line under adsiedit.msc check  under domain deleted the server name folder

then try to join again.
0
 
LVL 23

Author Comment

by:ormerodrutter
Comment Utility
OK will give it a go next week. Thanks in advance.
0
 
LVL 23

Author Comment

by:ormerodrutter
Comment Utility
Guys,

It has been 4 days and the record is still in the DC container so its not Latency issue.

ADSIEDIT is not what I wanted. I don't have an orphan NTDS settings. I am not trying to delete anything form AD Site and Services, my problem is that an orphan DC still exists in the DC Container in AD User and Computers. Metadata Cleanup is not clearing it as this "orphan" DC doesn't show in "List servers n site".

Anymore ideas?
0

Featured Post

6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join & Write a Comment

My last post dealt with using group policy preferences to set file associations, a very handy usage for a GPP. Today I am going to share another cool GPP trick, this may be a specific scenario but I run into these situations frequently in my activit…
Introduction You may have a need to setup a group of users to allow local administrative access on workstations.  In a domain environment this can easily be achieved with Restricted Groups and Group Policies. This article will demonstrate how to…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now