After some research on the Internet, I realised that you must not use Hyper-V MMC, use the "Setting" button in the Failover Clustering Manager instead. (Click below to enlarge)

I have a wide scope of interests in IT, which includes hyper-v private cloud, remote desktop services, server clustering, PKI, network security, routing & switching, enterprise network management, MPLS VPN on enterprise network etc. Started this blog for my quick reference and to share technical knowledge with our team members.
I was facing same problem.And to my amazement the issue is resolved once I removed the VM from the cluster and added it in again.Thanks for the tip too.
ReplyDeleteThanks for thwe tip, you solved a problem for me that's been driving me crazy! Lol
ReplyDelete