Windows Server 2019 – Creating a new virtual switch

How to enable Remote Desktop on Windows Server 2019

The following is an example I use often. I am running a new Hyper-V Server, which is connected physically to my corporate network, and so I can spin up new VMs, connect them to my external virtual switch, and have them communicate directly to the corp network. This allows me to domain-join them, and interact with them like I would any server on my network. Maybe I need to create some VMs that I want to be able to talk with each other, but I do not want them to be able to communicate with my production network. A good example of this scenario in the real world is when building a test lab. In fact, I am taking this exact approach for all of the servers that we have used throughout this book. My physical Hyper-V Server is on my production network, yet my entire Contoso network and all of the VMs running within it are on their own separate network, which is completely segregated from my real network. I did this by creating a new private virtual switch. Remember from the description that when you plug VMs into this kind of switch, they can communicate with other VMs that are plugged into that same virtual switch, but they cannot communicate beyond that switch.

Inside the Virtual Switch Manager, all I have to do is choose the kind of virtual switch that I want to create, P r ivate in this case, and click on that Create Virtual Switch button. I can then provide a name for my new switch, and I am immediately able to connect VMs to this switch. You can see in the following screenshot that I have created two new private virtual switches: one to plug my test lab VM’s internal NICs into, and another switch that will act as my test lab’s DMZ network:

Comments are closed.