You need to change the Firewall rules on both machines (NOT only the Hyper-V Server) Run this command on both machines: netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes
After doing some research, it looks like you can’t downgrade cluster functional levels, nor can you live migrate instances from 2016 to 2012 anyways. I would suggest using server 2016 instead of a 2012 to get this job done. You’d have to put a lot of work into using the wrong tool for the job … Read more
Don’t worry about the MTTF, MTBF, MTBR and MTBF figures… why would those apply to the specifics of your environment? The servers have internal redundancies and can be extremely stable in production. But that depends on your environment, the disk array/composition, types of disks, RAM quantity, CPU configuration, thermal characteristics, power, etc. Employing some form … Read more
The VM is configure to use 10GB of RAM, I have 16GB, it should start but it doesn’t. Not enough info. The host has 16GB RAM, of which only 4.8GB is in use. This leaves at least 11GB available for Hyper-V to use. Except it can’t. Too little. I love to add 1gb per vm … Read more
You really, really want to be able to easily identify which files belong to which virtual machine. Even if you lose access to the Hyper-V console. This comes up when trying to restore a VM from backups. Or when Hyper-V forgets about all of your VMs and you need to import them. Or the VM … Read more
I use VMs because they are portable. When you attach a physical disk, you lose most of the portability. It is much easier to copy a VHD file to another host than it is to move the physical disk between them.
Having 2-node cluster, it’s beneficial to have at least 2 AD DC VM’s each located on a separated host. In case of a host failure, you will ensure the AD is up and running. The AD running on a VM also allows you granularly maintain AD and Hyper-V host. Microsoft recommends to run AD either … Read more
Add the target account credentials to the Windows Credential Manager from the command line and try reconnecting: cmdkey /add:TARGET /user:TARGET\USER /pass Where TARGET is the remote Hyper-V host name and USER is the username added as an Administrator to the Hyper-V server. As an aside, after having struggled with this configuration myself, I highly recommend … Read more
From a helpful fellow commenting at https://blogs.technet.microsoft.com/virtualization/2017/04/20/making-it-easier-to-revert/: Set-VM -Name MyVM -AutomaticCheckpointsEnabled $false will tell Hyper-V on Windows 10 not to use automatic checkpoints for that virtual machine only. I’m still not aware of a way to tell the Windows 10 Hyper-V host not to set that option on new VM’s, but at least we have … Read more
You want the “remove-vmnetworkadapter” cmdlet in PowerShell. Merely looking at Device Manager will only allow you to add or remove device drivers from “devices” in the machine, where in this case the device is virtual. If you want a list of the virtual NICs that are exposed to the management OS (which is what you’re … Read more