How to create Switch Embedded Team for Virtual Network Switch

Fabian Felden 0 Reputation points
2025-11-26T12:30:09.62+00:00

I want to add a virtual switch for my Hyper-V I am hosting. This virtual switch unfortunately doesn't work for my current setup:

  • NIC Teaming activated, LACP Bond for "Ethernet" and "Ethernet 2" with a dynamic load balancing.
    Trying to add the virtual switch to this bond outputs the following (translated from german):
    """Error applying virtual switch properties
    Error adding connections for the virtual Ethernet switch.

An LBFO team cannot be attached to a virtual Hyper-V switch. If teaming is required, use "New-VMSwitch" to create a Switch Embedded Team (SET). For more information, see: https://go.microsoft.com/fwlink/?linkid=2185083 """

I checked out the link, cleaned the network configs with

netcfg -d

and got to work setting everything up.

My commands were as follows:

New-VMSwitch`` ``-Name`` ``$SwitchName`` ``-NetAdapterName`` ``$NIC1Name``,``$NIC2Name`` ``-EnableEmbeddedTeaming`` ``$true`` ``-AllowManagementOS`` ``$true`` ``-Confirm``:``$false

Set-VMSwitchTeam`` ``-Name`` ``$SwitchName`` ``-TeamingMode`` SwitchIndependent``-LoadBalancingAlgorithm`` Dynamic

New-NetIPAddress`` ``-InterfaceAlias`` ``$vEthernetName`` ``-IPAddress`` ``$IPAddress`` ``-PrefixLength`` ``$PrefixLength`` ``-DefaultGateway`` ``$Gateway

Set-DnsClientServerAddress`` ``-InterfaceAlias`` ``$vEthernetName`` ``-ServerAddresses`` ``$DNS1``,``$DNS2

Unfortunately, not even a restart of my server after this setup managed to establish a connection.

I also tried the Set-VMSwitchTeam with -Teamingmode LACP, but that yielded an error along the lines of:
"""The value LACP can not be convertet do VMSwitchTeamingMode.""" (I don't know the exact wording anymore)

Does anyone know how to fix this? I need my host and my VM to have a stable internet connection and I don't care how I can get there.

Cheers!
Fabian

Windows for business | Windows Server | Networking | Network connectivity and file sharing
{count} votes

6 answers

Sort by: Most helpful
  1. Fabian Felden 0 Reputation points
    2025-12-04T17:57:58.9+00:00

    Hey all,

    for everybody who is interested:
    The problem was actually on the side of the provider of my dedicated server. They only allowed LACP bonding on the NICs and that is why the SET bond failed to provide a network connection.
    I asked them to make the NICs compatible without limitations and now it is fixed.

    Thanks for everyone who helped me!

    Cheers!
    Fabian

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.