Setting up Hyper-V role on Windows 2012

I connected LAN cables to 2 ports on my Windows 2012 server. While setting up the Hyper-V role for the first time, I selected one of the (two) LAN cards, to use it for virtual switches. I plan to setup one VM, install Windows 2012 on it and then set it up as my primary domain controller.

Is all of the above, good practice? Is it okay to have those two LAN cards on the server, connected to my network at the same time?

The setup said that it is recommended to use one virtual ethernet card for VM virtual switches and to leave one ethernet card spare, for the physical host to use. I need to make sure that my network setup is okay, before setting up the VM.

I plan to assign a static IP to the VM, but not to the physical host.
Who is Participating?
Mohammed KhawajaConnect With a Mentor Manager - Infrastructure:  Information TechnologyCommented:
Rule of thumb for virtualization:

NIC 1  primary for management, use NIC 2 as backup
NIC 2 for live migration, use NIC 1 as backup
NIC 3 and NIC 4 teamed/bonded for VMnetworks

Above is recommended for minimum, more NICs required if using iSCSI.  It is also strongly recommended that each networks be segregated via VLANs. For a single server, 2 NICs would be fine and it should work.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you only have two network interface cards, I would at least team them, and make them active and standby.
bobox00Author Commented:
Thanks for all comments. I have already setup the Hyper-V role, using one nic card. I would like to use 2 teamed NICs instead. How do I make this change? Should I remove the hyper-v role and then reinstall it?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.