<div>
if you only have two network interface cards, I would at least team them, and make them active and standby.
</div>


if you only have two network interface cards, I would at least team them, and make them active and standby.

<div>
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?
</div>


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?

<div>
<div class="content wysiwyg-content">
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.<br />
<br />
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?<br />
<br />
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.<br />
<br />
<br />
I plan to assign a static IP to the VM, but not to the physical host.
</div>
</div>


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.

Setting up Hyper-V role on Windows 2012

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.