locked
Failover Cluster Manager v10 (Windows 10 Ent) - Cluster Version Not Supported RRS feed

  • Question

  • We are running a 2012 Hyper-V cluster managed primarily by SCVMM 2012 R2 and as a backup Failover Cluster Manager.

    I have installed Windows 10 RSAT (WindowsTH-KB2693643-x64.msu) and been testing I can again manage our various services with my Windows 10 client.

    When trying to connect to either of our 2012 Hyper-V cluster I get the following:

    Connection Not Supported

    Cluster XXXXXXX not supported

    The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager

    On each host Failover Cluster Manager connects without issue.

    I have traced the connections, checked firewalls, checked WMI and RPC etc and cannot find an issue.

    My colleagues can connect with v6 of Failover Cluster Manager.

    If I try connect without appropriate credentials I does fail for not enough privileges so I can see it does talk to the cluster.

    Any thoughts? Next step? Bug?  

    ## UPDATE ##

    I lab'd this by creating very simple no setup 2012 R2 DC, 4 hosts 2 of which created a 2012 R2 cluster and the other two created 2012 cluster. I was able to connect fine to the 2012 R2 but had the same issue with the 2012 cluster. I will play with the lab in hope it is not a missing feature of the latest RSAT/FOCM.

    • Edited by bodaduk Tuesday, August 25, 2015 11:54 AM
    Thursday, August 20, 2015 3:23 PM

Answers

  • Failover Cluster Manager (CluAdmin.msc) only supports N-1 downlevel management.  So from a Windows 10 client running RSAT, it is technically running the Failover Cluster Manager that is in Windows Server 2016.  Which means from Win10 RSAT, you can manage Win2016 and Win2012 R2.

    You cannot use Failover Cluster Manager to manage Win2012 (N-2) from Win10 RSAT.  You could however use PowerShell.

    Thanks!
    Elden

    Tuesday, August 25, 2015 9:17 PM

All replies

  • I'm highly interested in an answer here too.  Just installed the much needed RSAT for win10, but can't manage my 2012 H-V cluster...

    DLovitt

    Thursday, August 20, 2015 10:04 PM
  • In exactly the same boat here, very frustrating!!!
    Monday, August 24, 2015 3:09 PM
  • Failover Cluster Manager (CluAdmin.msc) only supports N-1 downlevel management.  So from a Windows 10 client running RSAT, it is technically running the Failover Cluster Manager that is in Windows Server 2016.  Which means from Win10 RSAT, you can manage Win2016 and Win2012 R2.

    You cannot use Failover Cluster Manager to manage Win2012 (N-2) from Win10 RSAT.  You could however use PowerShell.

    Thanks!
    Elden

    Tuesday, August 25, 2015 9:17 PM
  • Thanks for replying Eldon though very frustrating, for all it would take to support N-2,3,4,.. I guess Windows 10 is not fit for purpose for not only my organisation but also many others.

    For those wanting to help the cause

    https://windows.uservoice.com/forums/265757-windows-feature-suggestions/suggestions/9494259-rsat-backwards-support

    • Edited by bodaduk Wednesday, August 26, 2015 12:37 PM
    Tuesday, August 25, 2015 11:14 PM
  • hello,

    I'm able to connect Windows Hyper-v 2012R2 cluster but when I try to open VM "settings" or "Manage", nothing happens. Also I'm not able to create new VM from RSAT for Windows 10.

    Thursday, August 27, 2015 12:13 PM
  • Same here. When i try to connect VM, just receive the message: "Failed to connect to virtual machine xyz"

    When i see the event log, i have this error:

    "Could not load file or assembly 'Microsoft.Virtualization.Client.Common.Types, Version=10.0.0.0, Culture=neutral, PublickeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified".

    I have Hyper-V console installed.

    Thanks,

    João Sousa

    Monday, September 14, 2015 9:27 AM
  • Did you read the answer entered by Elden, the clustering product manager?  Windows 10 cannot manage n-2 (Windows Server 2012 and earlier).  It can manager 2016 and 2012 R2.

    bodaduk - " for all it would take to support N-2,3,4"  Do you know something Elden doesn't know about writing backwards compatible code when there are underlying changes in the operating system?


    . : | : . : | : . tim

    Monday, September 14, 2015 8:22 PM
  • Tim Cerling - If there were significant changes between 2012 and 2012R2 for failover clustering I would agree. But there isn't. The fact that Hyper-V manager still works fine shows how stupid this is!

    Considering Windows 10 only allowed a roll-back period of 1 month but it took MS longer than that to release the RSAT tools, I'm now not able to roll-back to Windows 8.1 due to having to wait so long for MS to release these tools which don't even work on the currently release N-1 format (2012R2 and 2012) because that is currently all that is available. Technicially, right now, failover clustering on Windows 10 only supports a single, production, operating system - 2012R2.

    Massive fail M$.

    Thursday, September 17, 2015 6:32 AM
  • Can someone point me in the right direction to manage virtual machines from a Windows 10 machine? I getsame error as everyone else. Cluster not supported..
    Friday, September 18, 2015 5:07 AM
  • I Have Winodws Server 2012 R2 + Hyper-V and get the error  in the above post.
    Friday, September 18, 2015 10:25 AM
  • I am getting the "Could not load file or assembly 'Microsoft.Virtualization.Client.Common.Types, Version=10.0.0.0, Culture=neutral, PublickeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified". error as well..

    I have Windows 10 Ent 64-bit and am accessing a Server 2012R2 failover cluster.. The hyper-v manager works fine but when connecting to the VM from inside the failover cluster mmc it gives the above error..

    Friday, September 18, 2015 2:06 PM
  • I am seeing the same problem. What makes it worse is that it worked fine to begin with and I believe one of the recent updates from Microsoft broke something. Hyper-V Manager works fine though. And I am using Windows 2012R2 so it is not because of the canned answer giving above.
    Monday, September 21, 2015 2:26 PM
  • Same problem here. Windows 2012 R2 Cluster + Win 10 Pro.

    Roles -> Virtual Machines... -> New Virtual Machine... gives me

    Could not load file or assembly 'Microsoft.Virtualization.Client.Common.Types, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    The first attempt to change VM settings - nothing happens. Choose "settings" again and you'll get MMC has detected an error in a snap-in and will unload it.

    Moderators please split this tread as the Eldens reply is the answer for a 2012 Hyper-v Cluster not 2012 R2.


    My DPM blog ystartsev.wordpress.com

    Thursday, September 24, 2015 11:37 AM
  • Also experiencing this same problem.  Windows 2012 R2 Cluster + Win 10 Pro.
    Thursday, September 24, 2015 7:19 PM
  • Windows 10 RSAT Failover Cluster Manager operations such as Create new virtual machine, change VM settings, Manage VM, Connect to VM require Microsoft.Virtualization.Client.Common.Types.dll

    This dll is not included with any RSAT version, NET Framework or anything. Google knows nothing about it.

    MSFT guys. We need that dll :)


    My DPM blog ystartsev.wordpress.com

    Friday, September 25, 2015 11:50 AM
  • Moderators please split this tread as the Elden Christensen reply is the answer for a 2012 Hyper-v Cluster not 2012 R2.

    Have a nice day !!!
    DPM 2012 R2: Remove Recovery Points
    DPM blog

    Tuesday, September 29, 2015 6:30 AM
  • Forum etiquette is to start a new thread for a new topic.  Or, the original poster has the option to unmark the answer.

    . : | : . : | : . tim

    Tuesday, September 29, 2015 12:47 PM
  • Was having this same issue with Windows 8.1 (microsoft.virtualilzation.client.commontypes, version=6.3.0.0) connected to Server 2012 R2 and found out that HyperV management tools weren't installed (as they are a different feature from the rest of RSAT). Once I added that Windows feature, it connected just fine.
    Sunday, January 10, 2016 6:00 AM
  • This is Microsoft's way of making revenue by forced upgrade. Remember the good old days when no matter what version of software one head it was always downward-compatible. It's counter-intuitive. One cool way to deal with it it to stick with Windows 7
    Monday, April 18, 2016 11:10 PM
  • This is not a viable solution. If MS provided an upgrade path for a cluster maybe but they don't. We are forced to Destroy and rebuild our 2012 clusters to move them to 2012 R2. Support should be added for 2012 to be managed from Windows 10, even if that support is a different version of Failover Cluster Manger.
    Wednesday, May 11, 2016 3:45 PM
  • Windows Server 2016 Failover cluster manager cannot manage Windows 2012 Hyper-V servers too.
    Tuesday, November 15, 2016 5:07 AM
  • I had this same problem until I installed the hyper-v management tools and then It worked.
    Thursday, December 29, 2016 8:22 PM
  • I just had the same problem on a fresh install of the 1607 build of windows 10 ent.  I had to install the H-V management tools from the Windows 10 features before Failover Cluster Manager from Windows 10 RSAT fully worked. You'd a thunk they'd install the necessary features automatically when you install RSAT, but we're talking about the keyboard monkeys and Microsoft now, aren't we.  I actually swear, they can do NOTHING right anymore. Dying branch of a once noble tree. SMH.

    DLovitt

    • Proposed as answer by A1980P Thursday, February 1, 2018 2:44 PM
    Thursday, December 29, 2016 9:30 PM