Hyper-V Failover Cluster 2012R2 with Windows 10 Node?
-
I believe you need windows fail over clustering which is not included in windows 10
-
And of course the critical question... why would you want to do this?
-
@scottalanmiller said:
And of course the critical question... why would you want to do this?
It's cheaper a W10 licence, I guest.
-
@iroal said:
@scottalanmiller said:
And of course the critical question... why would you want to do this?
It's cheaper a W10 licence, I guest.
Nope, more expensive. Hyper-V is free. Cost would be an inverse reason here.
-
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
And of course the critical question... why would you want to do this?
It's cheaper a W10 licence, I guest.
Nope, more expensive. Hyper-V is free. Cost would be an inverse reason here.
Fail over clustering It's not free, you need a Windows 2012r2 licence, isn't it?
-
@iroal said:
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
And of course the critical question... why would you want to do this?
It's cheaper a W10 licence, I guest.
Nope, more expensive. Hyper-V is free. Cost would be an inverse reason here.
Fail over clustering It's not free, you need a Windows 2012r2 licence, isn't it?
If that's true, it completely eliminates the "Hyper-V" is fully free argument and makes it solidly a "why ever use this" compared to XenServer.
-
http://www.altaro.com/hyper-v/hyper-v-failover-clusters/
Not super clear but it looks like free Hyper-V does this.
-
Scott, I don't remember, so you have a write up talking about how to install Hyper-V completely free?
-
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
And of course the critical question... why would you want to do this?
It's cheaper a W10 licence, I guest.
Nope, more expensive. Hyper-V is free. Cost would be an inverse reason here.
Fail over clustering It's not free, you need a Windows 2012r2 licence, isn't it?
If that's true, it completely eliminates the "Hyper-V" is fully free argument and makes it solidly a "why ever use this" compared to XenServer.
Until XS is as fully point and click supported as Hyper-V/VMWare, it will never gain SMB market.
It does not matter how much of a fanboy you are of XS. It currently takes too much manual work or command line knowledge to be useful to the SMB market where there is only a single guy doing all the work.
-
Hyper-V server 2012 R2 is a completely free and fully functional stand alone product. It is GUI free but you can manage it through the usual tools. Server Manager works great. You can download it from the Microsoft Technet Evaluation Center
https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2012-r2
And yes, clustering is an available feature.
-
@JaredBusch said:
Until XS is as fully point and click supported as Hyper-V/VMWare, it will never gain SMB market.
I don't agree. Why? Because it is already dramatically more point and click than Hyper-V. It's marketing, not ease of use, maturity or features, driving Hyper-V adoption. Or just confusion, as has long been its strong suit. But if you do a pure Hyper-V install vs. a pure XenServer/XenCenter, XS blows it out of the water. Doing XO takes a little more so doesn't have a direct comparison, but takes XS to yet another level that HV doesn't compete with well.
-
@Dashrender said:
Scott, I don't remember, so you have a write up talking about how to install Hyper-V completely free?
Is a write up needed? It's just a normal install. Hopefully instructions aren't needed. You just pop in the disc and install
If Hyper-V isn't dead simple to use, why would anyone use it? Isn't the point to be easy? That's all you need for XS. @JaredBusch was just pointing out that HV dominates because it is so easy to just point and click to use. -
No, not an installation post. Something that compared and contrasted hyper-v and XS. And a general description of how hyper-v is fully free.
Many IT people only ever see hyper-v as a service ads on to full server.
-
@Dashrender said:
No, not an installation post. Something that compared and contrasted hyper-v and XS. And a general description of how hyper-v is fully free.
Many IT people only ever see hyper-v as a service ads on to full server.
http://mangolassi.it/topic/5272/somethings-you-need-to-know-about-hyperv/
-
@scottalanmiller said:
http://www.altaro.com/hyper-v/hyper-v-failover-clusters/
Not super clear but it looks like free Hyper-V does this.
So, It's free if you install the Free Version but if you pay and install the Windows 2012 R2 Standard version is not available.
It's impossible to understand how the licences works in Ms.
-
@iroal said:
@scottalanmiller said:
http://www.altaro.com/hyper-v/hyper-v-failover-clusters/
Not super clear but it looks like free Hyper-V does this.
So, It's free if you install the Free Version but if you pay and install the Windows 2012 R2 Standard version is not available.
It's impossible to understand how the licences works in Ms.
Hyper-V is always free. No ifs, ands or buts. No exceptions. Always free. MS licensing is confusing, but not around Hyper-V. It's as straightforward as can be. There are multiple ways to install it, but only one way to license it - free. There are no "versions".
Even if you own unlimited Windows 2012 R2 licenses, most experts agree that you don't use that installation method, that's a fall back for Windows admins that just flee at the sight of anything outside of their normal routine. It's an illusion for people who can't handle the thought of a hypervisor. But the recommended install is always the pure Hyper-V one because it is the lightest means of installing.
-
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
http://www.altaro.com/hyper-v/hyper-v-failover-clusters/
Not super clear but it looks like free Hyper-V does this.
So, It's free if you install the Free Version but if you pay and install the Windows 2012 R2 Standard version is not available.
It's impossible to understand how the licences works in Ms.
Hyper-V is always free. No ifs, ands or buts. No exceptions. Always free. MS licensing is confusing, but not around Hyper-V. It's as straightforward as can be. There are multiple ways to install it, but only one way to license it - free. There are no "versions".
Even if you own unlimited Windows 2012 R2 licenses, most experts agree that you don't use that installation method, that's a fall back for Windows admins that just flee at the sight of anything outside of their normal routine. It's an illusion for people who can't handle the thought of a hypervisor. But the recommended install is always the pure Hyper-V one because it is the lightest means of installing.
Thank you for the explication.
-
@iroal the biggest confusions come from so many SMB Windows Admins that have convinced each other that Hyper-V exists in different modes because it "appears" that way to those not versed in virtualization and this, in turn, makes licensing seem confusing because they believe that there are different Hyper-V versions and associate things with Hyper-V that are actually part of Windows and vice versa. So in communities like SW, there are a huge number of people who repeat the same myths so much that it seems like it must be true.
Those of us coming from Xen backgrounds have an advantage because we are already aware of how Hyper-V works and what appears to be complicated from a Windows perspective, mostly because of Microsoft trying to make things "easy" for Windows admins, is actually quite simple. It's a problem that Microsoft tries to abstract something a bit too much and makes it confusing when there is no need for it. Calling the VM that controls the system the "physical" is insane, physical already means something quite the opposite, for example.
-
@scottalanmiller
In my case I had several confusions with Fail over clustering and his licences model in Hyper-V -
@iroal said:
@scottalanmiller
In my case I had several confusions with Fail over clustering and his licences model in Hyper-VUsing anything other than the "pure" Hyper-V installation adds confusion because you are applying a Windows license to the control environment and have to deal with Windows licensing on top of Hyper-V. If you avoid having that extra install, it gets easy to deal with (there is nothing to track or know.) All of the complications come from the Windows Server install rather than from the Hyper-V install.
I would recommend moving to straight Hyper-V installations to make things easier and more powerful. It is safer and more performant from having fewer wasted resources in the control environment. But it requires more effort to manage in a small environment.
