Unsupported Cluster Configuration for Virtual Machines located on SMB Share in VMM 2012 SP1

Article, Cluster, File Server, Hyper-V, Microsoft, SMB, Software, Storage, System Center, System Center Virtual Machine Manager, Virtualization, Windows, Windows 8/Server 2012 1 Minute

The last issue I’ve stumbled upon with System Center is with VMM component.

Symptoms

  • You have SCVMM 2012 SP1 UR2 installed
  • You have Windows Server 2012 Hyper-V for hosts
  • You use SMB 3.0 share for storing virtual machines
  • Some or all of your virtual machines does not use FQDN path to their vhd/x files
  • You’ve added your File Server in VMM by FQDN or NetBIOS Name
  • You receive the following error: Error (13924) The highly available virtual machine (VMNAME) is not supported by VMM because the virtual machine uses non-clustered storage.
  • Some or all of your virtual machines show as Unsupported Cluster Configuration

image

image

  • You may also have missing appropriate NTFS permissions on the share

    • image

    Resolution

I’ve managed to resolve this issue by executing the following steps:

1. Make sure you’ve added your file server in VMM by FQDN. If it is not added by FQDN you have to add it.

2. Create new share. You can create it on the same server. Give the share appropriate permissions.

3. Locate the new share in VMM. Add it as storage location to your hosts/clusters.

4. After is added make sure it show green in the properties of the hosts/clusters.

5. Storage migrate all your virtual machines from the old share to new share. For the machines with status Unsupported Cluster Configuration you can change the status to Running by live migrating them trough the Failover Cluster console.

6. After storage migration of each virtual machine refresh it and make sure in the properties of the machine in Status tab all is green.

7. After successful migration of all virtual machines you can remove the old share from the hosts/clusters and delete it from the File Server.

 

I’ve also may had problems with the permissions on the old share but it is easier to create new share than fixing permissions on existing share with running virtual machines.

The information is provided ‘AS IS’ with no warranties and confers no rights. Keep in mind that your case may be similar and this solution may not work for you.

Software I’ve used:

  • Windows Server 2012 with latest updates
  • SCVMM 2012 SP1 UR2
  • File Server with SMB share

Published by Stanislav Zhelyazkov

Stanislav Zhelyazkov has been working in IT since 2007. Stanislav has started his IT career as a Help Desk Specialist in 2007 while studying Informatics in the University of Ruse. He also worked in HP Enterprise Services (now known as DXC), maintaining large corporate IT infrastructures for clients in Holland, Switzerland and Germany and was involved in a Private Cloud project based on MS Hyper-V and System Center. He was also in the role of Principal Consultant in Lumagate developing and consulting companies on Azure, OMS, management and Private clouds. Currently he is Cloud Infrastructure Engineer at Sentia Denmark. Stanislav is active community member at MSDN forums providing answers on Azure. His blogposts can be found at www.cloudadministrator.net or www.systemcentercentral.com.

Published

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.