Install and configure Hyper V for VDI

Question

Hi Everyone
I am trying to setup a POC lab using Hyper-V to demonstrate use case for VDI
I do understand you need to have 2012R2 connection brokers and RDSH servers as part of the VDI deployment.
Coming from a vmware background I have much to learn in this area. I have 4 HS22 blades installed with 2012R2 Datacentre and configured teaming for the management Network. All 4 2012R2 host presented with shared storage from our SAN. On each host there are
6 NIC . 2 is for management / migration ?? and the rest of the 4 Nic is for the VM data network
On the management Teaming Nic, I have setup 2 NIC in independent mode with load balancing Dynamic. The second nic is set as Standby Adapter.
Before I enable the Hyper V role , I would like to find out the best practice for setting up 2012R2 HyperV for VDI ? Do I need a seprate migration network or use the same management teaming Nic ? And Where do use specify in hyper to use this network for
vm migration between host.
In Vsphere we use port group to assign different Vlan for each VMs. You can have multiple Port groups (with vlan id)  belongs to a vsphere distributed V switch. Host can be part of the distribute vswitch.
My understanding you have to manually enter the vlan id on each separate vm, there is no drop box to choose the vlan 
is there any way we can achieve the similar result in Hyper V. 
we do have license to use VMM
Many thanks

Answer 1

Here's an example of how I set up my networking for VDI using 2 hosts and a 10Gb connection.  This configuration creates the team, the virtual switch with bandwidth mode, adds the different logical networks, sets the VLANs, and assigns the bandwidth
priority for each. You dont see a VLAN associated with the VM Traffic adapter because the switch ports include the VM Traffic Native VLAN for that network.
This is a fairly common setup for sharing the different networks over a 10GB pipe.  Also, you don't see our storage network in there due to the way our FCoE is configured.  Our FCoE configuration is a separate 10GB connection that uses the switch
to prioritize the bandwidth.
PS C:\Users\Administrator> New-NetLbfoTeam -name ClusterTeam -TeamMembers "Ethernet 2","Ethernet 6","Ethernet 8","Ethernet 9"
PS C:\Users\Administrator> New-VMSwitch "ClusterSwitch" -MinimumBandwidthMode weight -NetAdapterName "ClusterTeam" -AllowManagementOS 0
PS C:\Users\Administrator> Set-VMSwitch "ClusterSwitch" -DefaultFlowMinimumBandwidthWeight 20
PS C:\Users\Administrator> Add-VMNetworkAdapter -ManagementOS -name "VM Traffic" -SwitchName "ClusterSwitch"
PS C:\Users\Administrator> Add-VMNetworkAdapter -ManagementOS -name "Management" -SwitchName "ClusterSwitch"
PS C:\Users\Administrator> Add-VMNetworkAdapter -ManagementOS -name "Live Migration" -SwitchName "ClusterSwitch"
PS C:\Users\Administrator> Add-VMNetworkAdapter -ManagementOS -name "Cluster" -SwitchName "ClusterSwitch"
PS C:\Users\Administrator> Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Management" -Access -VlanId 153
PS C:\Users\Administrator> Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Live Migration" -Access -VlanId 13
PS C:\Users\Administrator> Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Cluster" -Access -VlanId 12
PS C:\Users\Administrator>
PS C:\Users\Administrator>
PS C:\Users\Administrator> Set-VMNetworkAdapter -ManagementOS -name "VM Traffic" -MinimumBandwidthWeight 40
PS C:\Users\Administrator> Set-VMNetworkAdapter -ManagementOS -name "Management" -MinimumBandwidthWeight 20
PS C:\Users\Administrator> Set-VMNetworkAdapter -ManagementOS -name "Live Migration" -MinimumBandwidthWeight 20
PS C:\Users\Administrator> Set-VMNetworkAdapter -ManagementOS -name "Cluster" -MinimumBandwidthWeight 20