• Article

How to Remove a Node from a Hyper-V Host Cluster in VMM

 

Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager, System Center 2012 - Virtual Machine Manager

You can use the following procedure to remove one or more nodes from a managed Hyper-V host cluster by using the VMM console in Virtual Machine Manager (VMM). After you remove a node from a cluster, that node becomes a stand-alone managed host.

Prerequisites

Before you begin this procedure, make sure that the following prerequisites are met:

  • The managed Hyper-V host must be located in a domain that is trusted by the domain of the VMM management server.

  • The host cluster that you want to remove the node from must have more than one node.

  • The node that you want to remove must be in maintenance mode. To start maintenance mode, in the Fabric workspace, expand Servers, and then expand All Hosts. Locate and then right-click the cluster node that you want to remove, and then click Start Maintenance Mode. In the Start Maintenance Mode dialog box, click Move all virtual machines to other hosts in the cluster, and then click OK.

To remove a node from a Hyper-V host cluster

  1. Open the Fabric workspace.

  2. In the Fabric pane, expand Servers, expand All Hosts, expand the host group where the cluster is located, expand the host cluster, and then click the node that you want to remove.

    Note

    The node that you want to remove must be in maintenance mode. In the Hosts pane, verify that the host status is In Maintenance Mode.

  3. On the Host tab, in the Cluster group, click Remove Cluster Node.

  4. When prompted whether you want to remove the node, click Yes.

    VMM removes the node from the cluster. Open the Jobs workspace to view the job status.

  5. To verify that the node was removed, in the VMM console, make sure that it is no longer listed as part of the cluster.

    Note

    As part of the job, any shared storage that is managed through VMM is unregistered from the node that is being removed. If you allocated storage to the cluster that is not managed by VMM, we recommend that you unregister the shared storage from that node by using your storage array vendor’s management tools.

See Also

Modifying a Hyper-V Host Cluster in VMM