Home » Exchange Server » Unable to Remove Failed Server from DAG in Exchange Server 2010

Unable to Remove Failed Server from DAG in Exchange Server 2010

When an Exchange Server 2010 Mailbox server that is a member of a Database Availability Group has failed, part of the recovery process is to remove it from DAG membership.

In some scenarios this process may result in an error “A quorum of cluster nodes was not present to form a cluster“.  The full error text is below.

To resolve this issue use the -ConfigurationOnly switch instead to remove the failed Mailbox server from the Exchange 2010 DAG.  In this example server EX2 is being removed.

Next, evict the failed node from the Windows Failover Cluster.

Note: you need to import the Failover Cluster module into your Exchange Management Shell session to perform this task.

The failed server has now been removed from the Exchange 2010 DAG and the Windows Failover Cluster.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server


  1. wasim says:


    I am trying to import Import-Module FailoverClusters but msem shell is not getting this command please help


      • wasim says:

        msem is microsoft excange management shell, Actually i was Using Pssession from local machine
        Thank you so much it works from Dag member.

  2. BB says:

    I have an two exchange 2010 sp2 multi-role servers. In EMC it shows the replication is up to date with no queue built up. However, the DR server shows in the event viewer.

    “passive/active copy is not UP according to clustering”

    In cluster failover management the node shows as offline and so does the NIC. Both are online and the replication seems to be fine. The primary dag server shows all is well. Can I use the above to remove and readd the recovery exchange server? Do I need to remove all DB copies first or can I just execute the commands above and it will take care of it?

  3. Derek says:

    You have no idea how this helped. I couldn’t remove the member server from DAG because Windows Cluster Service would not start. Thanks!

  4. Mohammad says:

    Hi Paul and Thanks Again
    In my cluster and DAG everything was OK
    situation is :
    Two Ex 2010 SP1 in the DAG (mailbox01 and Mailbox02) and Two SP3 Added to DAG (mailbox1 and Mailbox2)
    Now I want to remove the previous ones

    but this error show up again and again while removing mailbox01 with no database copy on it

    anyway i used first cmdlet
    [PS] C:\>Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer Mailbox0X2 -ConfigurationOnly

    and it is removed from DAG but second ones

    [PS] C:Windowssystem32>Get-ClusterNetwork Maibox01 | Remove-ClusterNode -Force
    Get-ClusterNetwork : Failed to retrieve the network ‘Maibox01’ from the cluster ‘DAG’.
    An error occurred opening network ‘Maibox01’.
    The cluster network was not found
    At line:1 char:19

    do not work, give me following error and the server is not removed from windows failover cluster

    • Mohammad says:

      oh sorry
      i had no patience 🙂
      just needed some time maybe to clear the configurations from the cluster and then it worked
      i think you should mention that some time is needed between running those commands 😉

  5. Rune Goksør says:

    I ran these commands on a server that was still in the environment but halfway uninstalled from before. I was unable to uninstall Exchange 2013 from this “orphan” server after running the commands in this article because the server seemed to think that it was still a part of the DAG. MS helped me out with running this command first on one of the servers that is left in the DAG:

    cluster node ORPHAN-MBX /forcecleanup

    After that I could uninstall Exchange from this “orphan” server, and thus clean up AD properly.

  6. Zargham Haider says:

    I am unable to remove a Member from DAG. it shows below error:

    An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database availability group topology. Error: The fully qualified domain name for node ‘EX2’ could not be found.

    will you please help me.


  7. Ron Steurer says:

    This definitely helped me out in crisis when a server was added to a DAG but the IP still resolved to two servers so there was a conflict. Thanks Paul!!

  8. Trond Jenssen says:


    Helped me a lot. Had to remove a dead Exchange 2013 server from DAG, and remove-clusternode was the solution

  9. Nicola says:

    Hi, i have followed the procedure in the previus one article but my cluster dowsn’t go up. if i try to use this procedure i have this error:
    [PS] C:\Windows\system32>Get-ClusterNode EXCH-MBX03 | Remove-ClusterNode -Force
    Get-ClusterNode : Failed to retrieve the node ‘EXCH-MBX03’ from the cluster ‘DAG01’.
    An error occurred opening node ‘EXCH-MBX03’.
    The cluster node was not found
    At line:1 char:16
    + Get-ClusterNode <<<< EXCH-MBX03 | Remove-ClusterNode -Force
    + CategoryInfo : NotSpecified: (:) [Get-ClusterNode], ClusterCmdletException
    + FullyQualifiedErrorId : Get-ClusterNode,Microsoft.FailoverClusters.PowerShell.GetNodeCommand

    How can i do?

Leave a Reply

Your email address will not be published. Required fields are marked *