SCVMM Migrate Vmware to Hyper-V

Hello Handian Sudianto,

The error "The virtual machine is configured as highly available but the selected host does not have high availability services enabled and running. ID: 11006" occurs because the migration process requires the target Hyper-V host to have cluster-based high availability (HA) services enabled.

When migrating a VM configured as highly available (HA) with SCVMM to another host or cluster, the host must have HA features enabled and be part of a failover cluster with cluster storage configured and running. This error indicates that the host you are trying to migrate to does not have these HA cluster services active or set up properly.

For testing migration to a standalone Hyper-V host (non-clustered, without HA), you need to either:

• Disable the "Make this VM highly available" option in SCVMM before migrating, or
• Migrate the VM to a host that is part of a properly configured failover cluster with HA enabled.

In short, for moving a highly available VM, the target host must be in an HA cluster. Otherwise, migrate to non-HA hosts with HA disabled on the VM.

Steps to resolve:

1. Check if the Hyper-V host you want to migrate to has Failover Clustering and High Availability enabled.
2. If not running a cluster on the target host, disable the Highly Available setting on the VM in SCVMM before migration.
3. If using a cluster, ensure the cluster and cluster storage are healthy and online.
4. Use Failover Cluster Manager to verify cluster and HA status.

This will allow testing migration to standalone Hyper-V by disabling HA on the VM or migrate with HA enabled to a cluster host with HA services running.

Let us know if any questions?

If the comment was helpful, please click "Upvote".

The error "The virtual machine is configured as highly available but the selected host does not have high availability services enabled and running. ID: 11006" occurs because the migration process requires the target Hyper-V host to have cluster-based high availability (HA) services enabled.

When migrating a VM configured as highly available (HA) with SCVMM to another host or cluster, the host must have HA features enabled and be part of a failover cluster with cluster storage configured and running. This error indicates that the host you are trying to migrate to does not have these HA cluster services active or set up properly.

For testing migration to a standalone Hyper-V host (non-clustered, without HA), you need to either:

• Disable the "Make this VM highly available" option in SCVMM before migrating, or
• Migrate the VM to a host that is part of a properly configured failover cluster with HA enabled.

In short, for moving a highly available VM, the target host must be in an HA cluster. Otherwise, migrate to non-HA hosts with HA disabled on the VM.

Steps to resolve:

1. Check if the Hyper-V host you want to migrate to has Failover Clustering and High Availability enabled.
2. If not running a cluster on the target host, disable the Highly Available setting on the VM in SCVMM before migration.
3. If using a cluster, ensure the cluster and cluster storage are healthy and online.
4. Use Failover Cluster Manager to verify cluster and HA status.

This will allow testing migration to standalone Hyper-V by disabling HA on the VM or migrate with HA enabled to a cluster host with HA services running.

Let us know if any questions?

If the comment was helpful, please click "Upvote".

hi @Siva shunmugam Nadessin

I can't untick the High Availability, should be disable in vmware?

Hello Handian Sudianto,

In Hyper-V, once a VM is marked as highly available, the option becomes cluster-controlled. That’s why the checkbox is grayed out — you cannot disable it directly in Hyper-V Manager.

To disable high availability, you must use Failover Cluster Manager:

1.  Open Failover Cluster Manager on one of the cluster nodes.

2.  In the left pane, select Roles.

3.  Locate your VM in the list.

4.  Right-click the VM → Remove.

• Confirm removal.
• This removes the VM from cluster HA management but does not delete the VM.

5.  Now if you go back into Hyper-V Manager, the “Make this virtual machine highly available” checkbox will no longer be ticked or grayed out.

Using VMWare

VMware HA is enabled at the cluster level, not per VM, but you can override behavior:

Option 1 – Exclude a VM from HA restarts

1. Log into vSphere Client (vCenter).
2. Go to your Cluster → Configure → vSphere Availability.
3. Scroll to VM Overrides → click Add.
4. Select the VM.
5. Change VM restart priority to Disabled.
   • This tells HA not to restart the VM even if a host fails.

Option 2 – Disable HA completely (for the whole cluster)

Affects all VMs in the cluster.

1. Go to your Cluster in vSphere Client.
2. Select Configure → vSphere Availability.
3. Click Edit.
4. Untick Turn on vSphere HA → Save.

Let us know if you have any questions

Hi @Siva shunmugam Nadessin

The source VM under esxi already 'disabled' for VM restart Priority but still in the SCVMM i can't untick the High Availability.

The source vm i

Hello Handian Sudianto,

Kindly try below steps.

Option 1: Remove HA in SCVMM

1. In SCVMM, go to VM Properties → General → Availability.
2. If the checkbox is greyed out:
   • Remove the VM from the Failover Cluster in SCVMM.
     • Or migrate it to a non-clustered host temporarily.
     1. Once on a standalone host, the High Availability option becomes editable.

Option 2: Use PowerShell

If the UI won’t allow changes try using PowerShell.

Get-SCVirtualMachine -Name "VMName" | Set-SCVirtualMachine -HighlyAvailable $false

Run this in the SCVMM PowerShell console. It forces the High Availability flag off.

Have you tried Failover Cluster Manager if not try option below.

Option 3: Check Cluster Resource

• Open Failover Cluster Manager on the Hyper-V cluster.
• If the VM is listed as a clustered role, remove it from the cluster.
• Refresh SCVMM after that.

please reach out to us If you have any further questions.

Thanks