Kevin Remde's IT Pro Weblog
IT Pro Resources
TechNet EventsMicrosoft Security Response CenterTechNet IT Manager Community HubMicrosoft Virtual AcademyKevin’s Evaluation Download Center
IT Pro Evangelist Blogs
Blain Barton Blain Barton's Blog@BlainBar
Brian LewisMy Thoughts on IT...@BrianLewis_
Dan Stolts IT Pro Guru Blog@ITProGuru
Jennelle Crothers TechBunny@jkc137
Keith MayerIT Pros ROCK!@KeithMayer
Kevin Remde Full of I.T.@KevinRemde
Matt Hester Matthew Hester's WebLog@MatthewHester
Tommy PattersonVirtually Cloud 9@Tommy_Patterson
Yung Chou Yung Chou on Hybrid Cloud@YungChou
At our IT Camp in Minneapolis a few weeks ago, Kris asked me a valid question.
“How does a Hyper-V Server (not the full windows install) do clustering if you can’t install the cluster role?”
Kris’s question is a good one, because we had just been discussing how limited Hyper-v Server is in terms of what it can do, while at the same time supporting all of the same virtualization features and scale that a full Windows Server 2012 R2 machine with the Hyper-V Role installed does; including the ability to be joined to a Windows Failover Cluster.
In fact, during the discussion of what roles are supported on Hyper-V Server, I showed this screenshot:
So if you thought Windows Failover Clustering was a role, you’d be scratching your head at this one.
“Ah.. so what’s the catch?”
No catch. Windows Failover Clustering is not a role. It’s a feature!
It’s actually in the list of features rather than roles. It’s not enabled by default, and the Create Cluster wizard actually enables it when needed.
PS – In case you missed it, we did a 6 week series of blog articles comparing VMware to Microsoft virtualization. Check it out, here: http://aka.ms/VMWorMSFT.