Windows 10: DNS-problem running a Windows Failover cluster in Hyper-V on Windows 10.

I am trying to set up a lab Failover cluster on Hyper-V running on a Windows 10 host. The setup is 3 Windows server 2016 trial: 1 Domains controller and 2 member servers, to participate in the cluster. The DC also acts as DNS and iSCSI-target hosting 3 cluster disks.


The problem is, the IP-configuration of the servers seems to change randomly. With each restart I can get a 10.1... a 172.16 or a 192.169 network. Sometimes the servers are on different nets For example the DC having 172.xxx and the two members on 192.168. This messes up up the DNS setttings and the member servers sometimes falls out of the domain.


How can I control the DHCP within Hyper-V, and make sure the DNS-settings is correct?

:)

 

Win. 10 Failover Cluster Manager error

Hey all,

When I'm trying to connect to VM via "Failover Cluster Manager" mmc I'm getting "Failed to connect to virtual machine 'xxx'. For more data, see 'Information Details'."

When connecting to VMs from Hyper-v Manager mmc the VMs open as expected.

My Hyper-v cluster is 2012-R2 with latest updates and my win. 10 is fully updated.

Any suggestions?

Nir

 

Windows 10 RSAT - Failover Cluster Manager

I installed the remote server admin tools yesterday to my Win10 enterprise which made me very happy at first. DNS, DHCP, ADUC all worked great. Then I opened failover cluster manager. Problems began.

We have dozens of MS clusters running 2003 and up, mostly 2008R2 or 2012R2. When I try and manage them I get

Connection Not Supported

Cluster XXXXXXX not supported

The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager

This is happening with all the clusters I need to manage. Is this a bug or "working as designed"?

 

Hyper-V problem

Hi something happened.i think it is related network problem

i have 5 hyper-v host

and all my vm on the failover cluster show that they are restarted in migrating prosess

error this VM failed to perform the operation.The virtual machine is not in a valid state to perform the operation.

i need to learn if all on my 5 hyper-v host had network problem. and vm's starte to migrate and didnt find active network connection by host then went to restart. is it should be right?