I have a Windows Server 2019 member server that has two network cards. One nic serves one subnet that has a manual DHCP address(call that connection Ethernet2). The second nic connection is on another subnet that also has a manual DHCP address assigned to it(call that Ethernet). I want to install Hyper-V so I can have a VM serve the client machines for the subnet that is connected to the network that Ethernet is connected to. When I go through the Hyper-V installation it asks me do I want to select either of the network cards 
I'm not sure want to do at this point. If you can give some guidance.
-
Hyper-V on Windows Server 2019
-
Can I create a external virtual switch later if I don't select Ethernet ? So will that external virtual switch communicate with the virtual host machine within Hyper-V that's using Ethernet nic card for the different subnet ? I would like the VM server to communicate with the clients that are on that subnet.
-
Hi daniel, you dont have to select anything in there.
You can create any type of virtual switch after role adding completed. -
Sorry I missed this question.
As @Engin-Altug stated, you do not need to select anything on that screen during installation. Hyper-V is just giving you the option to create a virtual switch that is associated with the physical network adapters in your Hyper-V server. Most of the time, you will want at least one, so you can create an external virtual switch to connect your VMs to the physical network. You can create an external switch for one or both adapters later, so you can skip the step during the installation if you want to.
If you don't plan on connecting your VMs to the physical network, you don't have to create an external switch at all. If you don't, you can still create private and internal virtual switches to allow the VMs to communicate with each other and/or the hyper-v server.
You will need an internal or external virtual switch to allow the Hyper-v server to communicate with the VMs. Private will only allow communication between the VMs themselves.
Let me know if you have more questions!
-
@Mike-Rodrick
I created an external virtual switch for my vm and gave the physical host a manual DHCP as as well as the vm. Both are running W2k19 server. One of the problems I'm running into is I can ping to the vm hostname and IP address, But I can't ping my host machine name or IP address from within my virtual machine. What is going on ? Also, my vm needs to talk to client machines that are on a different subnet. How would I accomplish that ? Is it a routing issue or a firewall issue or both ?
