Excerpt from an article.
Here is where my dislike of Hyper-V network steps in. When one creates a new VM and it must be assigned a particular VLAN it has to be done by VLAN ID number and not using a friendly port group name.
I assume for most admins this configuration setting is not a large inconvenience as they may only have 3 or 4 VLANs. However, what if you have 10 or 15 or 50 VLANs in your environment? Every time you create a machine you have to know which VLAN ID number corresponds to the proper network segment for your new Management VM, or your new SQL server VM.
I think I can use -VMName instead of -ManagementOS for LAN, NLB and DAG to add them to appropriate VMs.
But in all books an articles I'm reading the VLAN assigned to a VM is done by VLAN ID number.
Is there something I should be aware of about using -VMName instead of selecting a VLAN ID for each VM I'm adding?