Hi guys, i have a client with an interesting problem.
They currently have two 2008 R2 machines running i hyper-V performing load balancing for exchange 2010 cas. Each machine has its own physical NIC, but that NIC is shared, so essential the LAN and the NLB net shares the physical NIC.
So moving to the present situation, they moved one of the machines to a new hyper-v cluster, but now it doesn't have its own physical NIC, it now has two virtual NICs, the LAN and NLB, when they try to add the machine to the cluster it gets stuck on converged, also when trying to add it to the cluster, it only shows one NIC, (the LAN), after some troubleshooting i discovered you have to uncheck the NLB checkbox on the NLB nic properties in order for it to show up but it still wont join the cluster.
Hope that wasnt too confusing, please let me know if you need clarification. So question, is this normal behaviour for HyperV and NLB?