Solved

Can't join server back into domain after force demotion

Posted on 2008-06-13
7
655 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
ID: 21778156
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
ID: 21778237
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
ID: 21780756
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
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 1

Assisted Solution

by:himkal
himkal earned 70 total points
ID: 21782235
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
ID: 21782249
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
ID: 21787005
OK will give it a go next week. Thanks in advance.
0
 
LVL 23

Author Comment

by:ormerodrutter
ID: 21801665
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

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Synchronize a new Active Directory domain with an existing Office 365 tenant
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
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…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

821 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