Forum Discussion
[server 25314] External SET Team to Internal after Reboot.
I have created SET Teaming on Windows Server 25314 (actually from a previous build) using External and 3 Intel i350-T4 ports, configured for Hyper-V and external access. ...
hi,
Hi, please refer to this article to create your network teaming on windows server 2022
https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/bypass-lbfo-teaming-deprecation-on-hyper-v-and-windows-server/m-p/3672310
Hi, please refer to this article to create your network teaming on windows server 2022
https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/bypass-lbfo-teaming-deprecation-on-hyper-v-and-windows-server/m-p/3672310
Thanks for the reply.
In the meantime, LBFO Teaming can work fine and we usually do it that way.
However, I get warnings with every Windows Insider update, which is inconvenient to be honest.
I would like to be able to use SET Teaming normally, as SET Teaming worked in the same environment in a build a while ago (I lost the build number) and the performance was better than LBFO Teaming.Addition:
How many years has it been since SET Teaming was implemented?
How long will you leave it halfway?
And if you are going to leave it half-assed, isn't there a need to deprecate LBFO?
I have nothing but questions about the Server Team's policy.
