Error validating hyper v machine name
I also modified the script to give me the option to only show updates that are missing or both.This is achieved by setting the variable to show installed and missing.
Now the customer will be adding new nodes to the infrastructure and these will be hosting a Windows 2012 R2 Hyper-V Failover Cluster.Well as it turns out it was the Jumbo Frame setting on the CSV and LM NICs. The Mellanox NICs allow for MTU Sizes up to 9614 in their Jumbo Frame property.Those servers had been connected to a couple of DELL Force10 S4810 switches. Now super sized jumbo frames are all cool until you attach the network cables to another switch like a Power Connect 8132 that has a max MTU size of 9216.Recently I was involved in troubleshooting some issues on a Windows 2012 based Hyper-V Failover Cluster.The issues were various but it all started with many failed backups of the virtual machines, and random host connectivity issues resulting in the VMs being vacated from that host.