Nano Servers- 2 Node Hyper V Cluster

Good day All,

Welcome back!!!

I have been playing with Nano Servers, so thought of creating a Hyper V cluster see how it goes.. Not much of challenges but couple of little hurdles will share it .

Anyone missed how to create  your First Nano Server, please check my post


Lab: Created 2 Nano Servers with Hyper V roles, Installed Failover Clustering Feature.

NANO2016A : 192.168.1.42
NANO2016B : 192.168.1.43
NANHYPVERV: 192.168.1.44 - Cluster Name


1. You can't run Cluster Validation of Nano Servers from Windows 2012 R2 Server, you will need a Windows 2016 installed. So i have a VM with Windows 2016 installed




Note: I got couple of warnings because Firewall is disabled on both Nodes and also there is not Private heart beat network and no teaming for Prod nic as well.

2.
Provided the Cluster name and IP




3. This was simple, Cluster formed ..




4. if you noticed Quorum Settings its showing the Witness as None that is because there is no Witness disk , so how did Cluster get created????




if you have not heard of dynamic quorum in Windows 2012, then you should check out the below articles.. which goes over what is dynamic quorum, what is Node weight and how it is been playing under the hood to keep the cluster alive

https://www.petri.com/what-is-windows-server-2012-r2-dynamic-quorum
https://technet.microsoft.com/en-in/library/jj612870.aspx

Unless you didn't go over the above two articles you may not understand the Current Vote below



Note: If you like to change the quorum settings then you can change to File Share Witness if required, but i have left it like this

5.
 If you ready to create Virtual Machines, but how as i have already created a Windows 2012R2 Scale Out File Server i will use the same share to Store VM's .

First thing we need to do is give Full permission to below ID's on the share

Nano Servers Computer Account
Administrator who is going to manage the HyperV
System Account






As i told before we have launched Failover Manager on a Window 2016 and created  the Hyper V  cluster right? so now why i use the wizard to create the Virtual Machine i started to get the below errors






The reason we seeing this because we are running Failover Manager from a Windows 2016 Server so its checking for delegation for the Nano Servers on the file share, more information on Why we need delegation check the below link

http://blogs.msdn.com/b/taylorb/archive/2012/03/20/enabling-hyper-v-remote-management-configuring-constrained-delegation-for-smb-and-highly-available-smb.aspx

if you your forest functional level is 2012 then you follow the steps in below article

http://www.thomasmaurer.ch/2014/02/hyper-v-over-smb-set-smb-constrained-delegation-via-powershell/

After enabling delegation wait for sometime before you start creating, i have seeing setting taking time like 10mints not sure why :)

Now you should be able to create your Virtual Machine on Nano Hyper v Cluster and do Live Migration.



As this is still Technical Preview i would think MS would do lot of modifications before final release.

As i keep testing will either update the same blog or will post new one .. hopefully this helps someone and until next on you all have a good day!!!