This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 56.00000000000001%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello All, I have installed Windows Server 2022 on an HP server, along with the Hyper-V Role. I attempted to configure NIC Teaming on the local server using 4 physical ports and then create a virtual switch connected to this NIC Teaming. However, it appears that this type of NIC Teaming, which is LBFO, is deprecated. Therefore, I need to configure SET NIC Teaming. I used PowerShell commands to configure NIC Teaming, and the load balancing algorithm type is set to dynamic. Initially, the speed showed as 4GB, but then the connection to the server was disconnected. I changed the load balancing algorithm type to HyperVPort, and everything is functioning properly now, but the speed is now showing as 1GB. Could you please advise? Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
This appears to be consistent with the experiences described in https://learn.microsoft.com/en-us/answers/questions/1369473/switch-embedded-teaming-hyper-v-port-vs-dynamic
hth Marcin
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 94%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIX%3C/text%3E%3C/svg%3E)
Hi Ahmad, Thanks for your post. I totally understand your frustration on dealing with this issue, but please understand that Network Adapter Teaming is a third-party Technology that provides fault tolerance for multiple Network Adapters. Since Network Adapter Teaming is only provided by Hardware Vendors, Microsoft does not provide any support for this technology through Microsoft Product Support Services. As a result, Microsoft may ask that you temporarily disable or remove Network Adapter Teaming software when troubleshooting issues where the teaming software is suspect. If the problem is resolved by the removal of Network Adapter Teaming software, then further assistance must be obtained through the Hardware Vendor. Reference: Support Policy for NIC Teaming with Hyper-V - Windows Server | Microsoft Learn Best Regards, Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.