Can't join server back into domain after force demotion
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am sorry the second last line under adsiedit.msc check under domain deleted the server name folder
then try to join again.
then try to join again.
ASKER
OK will give it a go next week. Thanks in advance.
ASKER
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?
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?
ASKER