Improve company productivity with a Business Account.Sign Up

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

Exchange uninstall error

I'm trying to decommission one of our Exchange 2010 servers.  I've encountered several errors, most of which I've been able to resolve except for 2 that seem intertwined and pointing to each other.
When I try to uninstall Exchange through the control panel - programs and features, it fails when doing the readiness check for the mailbox role with the error - (paraphrased) - this computer is part of a cluster and must be removed from the database availability group.
So I use powershell to issue the command "remove-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer servername"  This command throws the error - (paraphrased) "Mailbox Server servername is not part of the DAG"  I've attached a screen print of these errors
As you can see, it appears to be a viscious circle - can anyone help me get of this merry-go-round?
  • 5
1 Solution
VB ITSSpecialist ConsultantCommented:
Try running the below commands in PowerShell (remember to "Run as administrator"):
Import-Module FailoverClusters
Remove-ClusterNode <Server> -Force

Open in new window

If the Remove-ClusterNode command doesn't work then try:
Clear-ClusterNode <Server> -Force 

Open in new window

Md. MojahidCommented:
Open ADSI Edit and delete all exchange server information from here.
skbarnardAuthor Commented:
Before I accept a solution -- VB ITS - your solution did indeed let me remove the server from the cluster but I only wanted to uninstall Exchange from that particular server.
It appears that once this node was removed from the cluster, it may have removed the whole cluster or may have uninstalled Exchange from all nodes.
I now am receiving the attached error when trying to open the EMC on one of the 2 remaining nodes.  Can either of you or anyone else help me understand how to get around this?
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

skbarnardAuthor Commented:
OK, long pause before getting back to this question.  I'm now trying to decommission my remaining 2 Exchange 2010 servers.  I'm trying to uninstall via the control panel/programs and features area.  When I click on Exchange 2010 and click 'Uninstall', the wizard starts up and runs its checks.  I run into errors and close things down as the errors come up but the wizard still thinks that the node 2 server has connectors associated with it.  The node 2 server is part of a cluster, I haven't turned off the cluster services but I have disabled all connectors on this node.
Since it was causing a problem, I researched 'uninstall Exchange 2010' and found an article that said to manually remove registry keys.  I don't think we're ever going to install Exchange again but I still want to decommission these servers properly.
However, I did go ahead and remove the Exchange registry keys (HKLM\Software\Microsoft\Exchange & HKLM\Software\Microsoft\Exchange Server).  Now, of course, I can no longer open the EMC and when I click on 'Uninstall' in the programs area of control panel, the wizard won't even start.
My plan is to re-purpose the servers in the Exchange cluster.  I'm currently trying to uninstall Exchange from our remaining node and get the error that I can't remove the mailbox role because of the OAB.  How can I remove the mailbox role - do I just go ahead and delete the OAB?
skbarnardAuthor Commented:
OK, another comment -- I've been researching this online and found an article (I don't actually know where it is at this point) but I followed the directions in that article.  It was something to do with removing a stubborn node from the DAG by doing a registry hack.
I removed the DWORD or whatever from the registry and now I'm unable to uninstall Exchange (through Control Panel - Programs and Features) on that node - the uninstall wizard will not open.
The DAG is actually down (as seen through Failover Clustering on the other node I haven't touched yet) and I'm unable to expand anything out in the EMC (on the untouched node) - it opens but that's about it.  EMC will not open on the node that's had the registry hack.
Technically, I'm going to be repurposing the servers in my Exchange cluster so I don't really care that Exchange is not working,  but in my research I determined that if you don't decommission Exchange properly, if you ever try to install Exchange again the remnants left by not decommissioning properly can cause issues.
Can anyone help with PS commands or CLI commands or 3 party apps that will help me get out of the mess I've probably created for myself?
skbarnardAuthor Commented:
I know this was a quasi-abandoned question but I am actively seeking advice right now.  If I need to open a new question, I'd be glad to but I thought it best to try using this already open thread.
Off for the weekend - hope anyone viewing is having a nice one but looking forward to hopefully some good links to articles that will help me maybe force an uninstall of Exchange.
skbarnardAuthor Commented:
It's been a long while since I initially asked this question and if anyone pokes down through the thread, they'll see I was asking for some additional advice which to date I haven't received.
I'm accepting the solution from VB ITS since their response did indeed allow me to do what I was initially asking about.
I will open a new thread on a similar topic but with a somewhat convoluted issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now