• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5506
  • Last Modified:

2008 R2 Domain controller - demote fail

Hello,

I have a 2008 R2 DC that has many problems. There is already a second DC in the same forest/domain. I want to reinstall the one with the many problems but I can't demote him.
When I run dcpromo or the dcpromo unattented command line I get the following error:
- Failed to detect if Active Directory Domain Service binaries were installed. The error was: The remote procedure call failed.

I can't also open the server manager, the same problem.

Can I just format and reinstall this server or will I have problems in my domain when I do this?

PS: there is already an active second DC including DNS.
PS2: this was a Exchange 2010 + DC config. Not the best config I realize now, there for I want to reinstall the first DC and only make him Exchange 2010 server and keep the second DC as the active DC.
PS3: none of the DC's are in read only
0
NR_EIS
Asked:
NR_EIS
  • 3
  • 2
  • 2
  • +2
1 Solution
 
Schnell SolutionsSystems Infrastructure EngineerCommented:

The ideal idea is that we try to repair the damaged DC and depromote it in a soft way. But some times it is not possible so in such cases we just remove the data manually, the only drawback of this is that we will need to make some additional steps, but it is not a problem for AD. One thing that we can check before formatting, demotting or removing the damaged DC is confirming how long does it have without replicate. If it has more than the thombstom life it is not worth enough to try to repair it and it should be eliminated

You can check it like this...

Go to the working DC, open a command prompt and write:

repadmin /replsummary




0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:


In case that we decide to remove that server from AD we shall be aware of the actual roles that it has, example: If it is a DNS server and there are clients pointing to this server (do the clients include the second DNS as DNS Server?), if it is a Certificate Authority (Server with ADCS installed), if there are applications pointing to that DC/GC/LDAP (hardware appliances, internal applications in servers), if there are FSMO running on it (RID, PDC, Schema, Infra, DNM).

How is it with the Exchange 2010 that it has installed, isn't it actually working?

0
 
ChandarSCommented:
On the DC where you are running DCPROMO

Check the DCPROMO log what they are saying  and check also eventvwr

DCPromos.log
DCPromo.log

Location : %SystemRoot%\Debug

So If you decide to format the system

Then you need to manually do the metadata cleanup

http://support.microsoft.com/kb/216498

PS : Check FSMO role holder before doing anything
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Darius GhassemCommented:
First run dcpromo /forceremoval to remove AD from this server you can just format if you want but you need to run metadata cleanup to remove any lingering objects from AD.

Good graphical view of metadata cleanup steps http://www.petri.co.il/delete_failed_dcs_from_ad.htm.

Go into DNS delete all records for this DC.
0
 
NR_EISAuthor Commented:
@ schnellsolutions: the replication has no problem, and the Exchange 2010 still does it core services but the ecp panel doesn't work anymore along with some other problems
@ ChandarS: I've transferred all the master configurations the my other DC (RID, PDC, Inf)
@ dariusg: the force removal doesn't work also, same problem as opening dcpromo standard. I'm going with the reinstall and the metadata cleanup, thanks for the post from Petri

I'm going to leave this open until everything is done. Thanks for the posts already...
More information is still welcome.
0
 
ChandarSCommented:
Hvae you checked the DCPromos.log and DCPromo.log
Location : %SystemRoot%\Debug

Or event viwever what is saying.

If you are getting any thing odd then post here...
0
 
NR_EISAuthor Commented:
@ ChandarS: Yes I have checked my logs and after the METADATA clean up there is no error anymore. Also all the records to my previous DC in AD & DNS are gone.

But I still have a big problem. After installing Exchange 2010 again on a different server I got my previous sever also in my databases. With a mention of his database store, the store can't be deleted because there is no connection anymore to the previous one.

I've tried to delete everything (accepted domains, send connectors) and re adding them, but still my incoming doesn't come in. In is received by the exchange but the connector have the following problem: "451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain; nonexistent domain"

I've searched a bit and all the posts I came along mention an availability group with one server down, what in this case isn't the problem.

Any advice?
0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:
Hello NR

You are telling that you installed Exchange 2010 again on a different server. What happened with the Exchange server on the original server? is it online? If that server is permanently offline the best option is to recover it using setup /recoverserver option. But if it is not possible the data in the Configuration partition of AD shall be removed and just in that way you are going to eliminate the apperance of that old server. What is the actual status?

Send us the following information after running these commands in Exchange Management Shell:

Get-ExchangeServers | fl
Get-ReceiveConnectors | fl
Get-SendConnectors | fl

0
 
Vishal PatelCommented:
You can try following links:

(1) http://www.petri.co.il/fix_unsuccessful_demotion.htm
(2) http://www.petri.co.il/fix_unsuccessful_demotion.htm

Let me see if problem persists.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now