Hyper-V Virtual Switch Manager and host adapter names

We're building an HP DL380 G10 with Server 2016 as a Hyper-V host.  There are 4 physical Ethernet adapters on board.  I edited the friendly names of these adapters to agree numerically with the device name (which in turn agree with the physical labels on the server).  See first image attached.

When I create a virtual switch however, the list of physical adapters available does not reflect the updated friendly names.  See second image.  

I could live with this if the 3 'numbered' adapters in the virtual switch manager were right, but they are not.  The device the VSM sees as #4 is actually #3, and so on.  

Is there any way to force Hyper-v to refresh these values or edit this list via the registry?  I've already removed and re-added the Hyper-V role and the problem remains.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jose Gabriel Ortega CastroCEO Faru Bonon IT - EE Solution ExpertCommented:
Khamma1Author Commented:
Thanks Jose.  That's not where the issue lies though.  The adapter names in control panel on the host are perfect. (image 1)

The problem is that when creating a Hyper-V virtual switch, the adapter names shown in the drop-down (image 2) don't match the adapter names in control panel.
Jose Gabriel Ortega CastroCEO Faru Bonon IT - EE Solution ExpertCommented:
Yeah, I realized later on, I recommend that you just take the gigabit # order and match it with the one you already create it and document it. I haven't seen that change before.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
We usually do something like this:

Rename-NetAdapter "Ethernet" -NewName Mgmt-1
Rename-NetAdapter "Ethernet 1" -NewName Mgmt-2
Rename-NetAdapter "Ethernet 2" -NewName vSwitch-1
Rename-NetAdapter "Ethernet 3" -NewName vSwitch-2

New-NetLbfoTeam -Name Mgmt -TeamMembers Mgmt-1,Mgmt-2

New-NetLbfoTeam -Name vSwitch -TeamMembers vSwitch-1,vSwitch-2

Then go on to create the virtual switch on that team.

With Broadcom Gigabit make sure to disable Virtual Machine Queues for all physical ports or there will be network problems.
Khamma1Author Commented:
Agreed on the VM queues.  The names are fine, and I don't need teaming yet.  I don't think I'm doing a good job of getting this weird situation across.

When I connect the host server to Ethernet, everything works as expected.
If I plug into the first Ethernet port on the host, Control Panel > Network Connections shows a link on Ethernet #1
This works for all 4 physical ports; they 'agree' in name with what's shown in Control Panel.

Now I create a virtual switch.  I select Ethernet #4 as the port to use for External network.  I connect a patch cable to physical Ethernet 4 on the host.  It doesn't work...  But it does on PORT #3.

Through trial and error I found the way the virtual switch manager has the ports named:
Physical port                  Host adapter name                  Name in virtual switch manager
Ethernet #1                      Embedded LOM 1 Port 1           Gigabit Ethernet #2
Ethernet #2                      Embedded LOM 1 Port 2           Gigabit Ethernet
Ethernet #3                      Embedded LOM 1 Port 3           Gigabit Ethernet #4
Ethernet #4                      Embedded LOM 1 Port 4           Gigabit Ethernet #3

No matter what I do with things like Rename-NetAdapter the names don't change in the virtual switch manager drop-down.

I don't want to put this into production with a note that says "Yeah, the virtual switch says it's connected to Ethernet #3, but it's really #4"
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Supposedly, there was something set up in the OS to correctly set the "Host Adapter Name" based on the PCIe location(s) of the NICs. That in turn was supposed to produce the "Physical Port" names in order. Supposedly.

We've installed a lot of virtualization hosts and cluster nodes over the years with identical setups across the board and the naming rarely comes out the same.

The "Physical Port" name is the important one. We correlate based on MAC address. The lowest MAC address on each NIC gets set to management team while the others get set to the virtual switch, Live Migration, and any other network need.

I suggest ignoring the name in the virtual switch manager.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.