How to identify the Virtual Adapter of the Management OS?

Environment: HyperV on Windows Server 2008

My understanding of how virtual network works is the following: when you create a External virtual switch in HyperV Manager, this virtual switch binds itself to the physical adapter of the server. When you configure this virtual switch, a virtual adapter is created on the Management OS and on All guest Virtual Machines. The Management OS and the Virtual Machines use their pertaining virtual adapter to communicate with the Virtual switch (which is bounded to the Physical NIC of the server) to communicate with the physical network. Please correct me if I am wrong.

In order for me to assign a static IP to my Virtual Machines, I will need to connect to the machine itself and configure its respective "virtual" adapter.

My question is, how can I identify the virtual adapter of the management OS to configure it statically?
LuiLui77Asked:
Who is Participating?
 
Cliff GaliherCommented:
That isn't really accurate. Hyper-V will associate the selected NIC to the virtual switch when an external network is created. But virtual adapters for the VMs must be added manually.

As for the management OS, yes, a virtual adapter is created by default and is an active participant on the virtual switch.

As far as identifying adapters, if you view properties, it is pretty easy. The physical adapter will ONLY be bound to the "virtual network switch protocol." Don't touch any settings on that adapter.

The virtual adapter will have all of the usual bindings to TCP/IP, client networking, etc. You'd make changes there.

Now with that said, the preferred configuration is to have one physical NIC not associated with any Hyper-V external networks. That NIC will therefore not be bound to any virtual switches and can be changed and managed just as if hyper-v were not installed. And even better, it will be dedicated to the management OS, so even if something goes wrong with hyper-v's virtual switches (it happens), you have management access to the OS. Which makes the whole virtual adapter issue moot.
0
 
Santosh GuptaCommented:
You can try to use the following PowerShell script, it utilizes WMI to find out if machine is virtual machine or physical machine.


gwmi -q "select * from win32_computersystem"
0
 
LuiLui77Author Commented:
Ok Cliff, thanks. I can see it better now, but in regards to the virtual network adapter that I have to configure manually on every virtual machine, I never had to do so. The only thing that I do is to select the virtual network switch to use on the Network adapter option under Hardware. Is this considered as configuring the virtual network adapter manually?
0
 
Cliff GaliherCommented:
Yes. Creating the virtual switch did not add those adapters. They were there already. And as you are selecting the switch, those adapters were not auto configured or changed when you created the switch either.
0
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.