VMM 2012 R2 Hyper-V Networking – best practice Share on Facebook Post on reddit Tweet on Twitter Share on LinkedIn Home › Forums › Virtualization › Microsoft Hyper-V Technology › VMM 2012 R2 Hyper-V Networking – best practice This topic has 2 replies, 3 voices, and was last updated 4 years, 1 month ago by mr.mahesh. Viewing 1 post (of 1 total) Author Posts atchinsonMember Jul 30, 2014 at 5:23 pm #164066 I have been reading and studying about the different ways to configure VMM 2012 R2 Hyper-v networking. I have searched and searched, but cannot seem to find a clear answer. So… Physical Network – (One Company, no tenants, isolation not required) Single fully routable network with multi vlans at each physical site. Do I create a Logical Network for each VLAN? (Doesn’t seem right) I am guessing I create a single Logical Network with sites and each site I add it particular available VLANs. (Currently what I am doing) With a single VM Network. However, when creating VM from Templates, I cannot choose the required VLAN, which breaks the process of auto joining the domain. How can I make sure the VM is connected to the right VLAN without having to change the VLAN after the VM is created? Do I create a VM Network for each VLAN? This might make more sense, but I cannot 100% verify if this is the correct way. Everything I read says if you have a single network, just choose the “One connected network” and a single VM Network, but I run into the VM creation problem (picking the VLAN). I can choose VLAN-based independent networks, but I do not require Isolation. Can someone please help sort this out? Thanks Author Posts Viewing 1 post (of 1 total) You must be logged in to reply to this topic.