First published on TECHNET on Dec 20, 2016
~ John Clyburn | Senior Consultant
Hi everyone, my name is John Clyburn and I’m a senior consultant here at Microsoft. I was recently working at a customer site where we were getting “
Unsupported Cluster Configuration”
errors in the SCVMM console for VMs in a Hyper-V cluster so I thought I’d take a minute today to discuss what we did in the hopes that it might help you if you run into a similar situation. There can be many different symptoms and resolutions for a problem like this so just be aware that what I describe here is specific to my particular scenario.
In this case, all of the VMs were still online and running without issue, I could log on to the VMs, and there were no service interruptions to the services running on the VMs. The customer had the following configuration:
- SCVMM 2012 R2 UR11 (Clustered).
- Two Windows Server 2012 Hyper-V (Clustered) for hosts.
- CSV and SOFS shares for storing virtual machines setup via SCVMM.
Several of the virtual machines displayed the following error in the VMM console under the status column:
Unsupported Cluster Configuration
In SCVMM, when we would right- click the VM and select
, we saw this
Error (13924) The highly available virtual machine (VMNAME) is not supported by VMM because the virtual machine uses non-clustered storage
As stated earlier, there can be many different causes for the Unsupported Cluster Configuration error, however in my particular case it was caused by a misconfiguration of the storage and property path settings on the VMs. When using a cluster, all of the VM storage properties settings must be stored on highly available storage like a cluster shared volume, and in my case not all of the VMs storage properties were being placed on a highly available storage.
For an example of the same error being caused by a network misconfiguration, here’s an article written by Microsoft’s own Chuck Timon that documents how he approached and resolved the same error:
The solution below demonstrates how to correct the
Unsupported Cluster Configuration error
caused by a misconfiguration of the storage and property path settings on a VM that is stored on a cluster volume. If the VM storage and property path is not pointing to folders that are highly available, you will receive the unsupported cluster configuration error. Follow the steps below to correct it.
In the Scenario below, I will use the following
ames in the example solution:
- Failed VM Name:
- VMM computer Name:
- VMM Cluster Name:
- VM storage path on servers:
CSV installation uses
SOFS installation uses
1. On the VMM server open an administrative
Virtual Machine Manager Command Shell and r
. For the c
omputer name use
SRV-VMM-01, or for
a cluster, use the cluster name of
2. In VMM PowerShell, run
Get-SCVirtualMachine -Name <SRV-FAILED-01> | FL * and c
heck to see if any of the following paths are not on HA storage such as a cluster CSV volume:
that the only way to see the above info is by using PowerShell. You will not see them in the properties of the VM.
3. If any of the paths point to local storage on the Hyper-V system then this is the problem. An example would be if it’s listed as
path will cause the error.
4. Record the following settings from the VM:
All drives VHDX file path
the VM. Optionally but recommended, export the VM in Hyper-V to the local file system for a backup.
6. If the VM is displayed in Failover Cluster Manager (FCM), launch FCM and navigate to <HYPERVClusterName>, then right-click the VM and select
the VM (
that we’ll have to delete the VM and recreate it but
DO NOT DELETE IT
IN SCVMM because SCVMM will delete all the files and we do not want that. Delete it in Hyper-V Manager by going to the Hyper-V manager console on the node that owns the VM, right-clicking the VM and selecting
. This will leave the VMs folder with all the VHDX files in it.
8. In SCVMM, the VM should now show as ‘Missing’. However, even if it does not, open PowerShell in VMM and run
Get-SCVirtualMachine -Name <SRV-FAILED-01> | FL *
. If you get data back, arrow up (to run the command again), but make the command look like this:
Get-SCVirtualMachine -Name <SRV-FAILED-01> | Remove-SCVirtualMachine -Force
The VM should now be gone in the VMM console.
9. Now, in
Failover Cluster Manager
Roles –> Virtual Machines –> New Virtual Machine
10. On the
Select the Target cluster node p
age, select the same Hyper-V host and click
11. On the
Specify Name and Location
page, specify the following:
that you should use the same VM name.
- Select Store the Virtual Machine in different locations and use
<SRV-SOFS-01.CONTOSO.LOCALMGMT-VHD1. Just make sure that the dis
k path is on HA Storage.
12. On the
page, select the appropriate generation.
13. On the
page, set the memory.
14. On the
page, set the networking.
15. On the
Connect Virtual Hard Disk
page, add the VM using the existing VM VHDX file. It’s important that you do not create a new disk. Navigate to the existing OS VM disk and add it, using either
16. On the
Finish, then on
DO NOT START THE VM YET
17. Add the
file to the VM.
18. Edit the VM by right-clicking it and selecting
. Navigate to
SCSI Controller, h
. In the Virtual Hard Disk box type the path to the existing shared VHDX file. This will be either
DO NOT CLICK APPLY YET!
Enable virtual hard disk sharing, then c
Checkpoint File Location
Smart Paging File Location
is pointing to the CSV or SOFS share and not a local folder on the Hyper-V host. This would be
f it doesn’t then the VM will not be able to migrate between the Hyper-V cluster nodes.
, set the appropriate Virtual Switch and click
to save the settings.
the VM in
failover manager, then c
onnect to the VM and login.
23. Set the VMs
At this point the VM should now be able to migrate in failover cluster manager and VMM.
Test the migration to verify.
Once complete, you should no longer see the “
Unsupported Cluster Configuration”
errors in the SCVMM console.
| Senior Consultant | Microsoft
VMM 2012 R2 VMM 2016