Hyper-V: five most common mistakes with deployments to avoid

Microsoft has made working with Hyper-V so easy that it no longer takes a specialized skill set to get a virtual machine up and running. Here’re the five most common mistakes with Hyper-V deployments and how you can avoid them: “#1. Ignoring management network: When you first add Hyper-V virtualization role, you should dedicate a […]

Microsoft has made working with Hyper-V so easy that it no longer takes a specialized skill set to get a virtual machine up and running. Here’re the five most common mistakes with Hyper-V deployments and how you can avoid them: “#1. Ignoring management network: When you first add Hyper-V virtualization role, you should dedicate a single network interface card for management. Many people skip this because it wastes a network port. After all, without a dedicated management interface you’re still able to manage host, so why waste the port? Well, consider security implications. The host, otherwise known as parent partition, is hosting several VMs, all with their own workloads and data. When you’ve access to host, you also’ve direct console access to those VMss and virtual hard disks. Would you allow your DMZ and internal network to operate in same subnet? Of coursen’t -- there would be too many risks. Consider the host to be of a different security level than your VMs. The parent partition should only be manageable from a separate network interface on a network dedicated to administrative access. Without it, you open yourself up to security risks.”

Full Article: Five mistakes to avoid when deploying Hyper-V virtual machines