MicrosoftNZ_BenThomas Yeah, thanks, that never occurred to me. Oh, wait... it did. But thanks for the assumption that I'm a moron... but you do ask an interesting question (despite it having an EXTREMELY obvious answer of "because I didn't know how") so let's analyze why I didn't start there: I tried to find any information on it, but I kept finding my way back to one of a billion forums and blogs like this one that ONLY talk about converting and the conversion tool and don't say a single thing about how to create one from scratch. Combine that with a billion other red herring blogs about things like Microsoft Teams, every other conceivable hyper-v teaming problem, the acronym "SET"... and the bad assumptions I made (although they seem reasonable even in hindsight) that you would create a SET team in the same place in the GUI we've always created NIC teams and that there would be a GUI way of doing it somewhere in Server or even Hyper-V once I realized I should look there... and I was one frustrated guy by the time I had read yet another overly-long and overly-detailed explanation of SET without a single word of how to create one.
So... for any other frustrated folks who find their way here and are super annoyed... let me sum up the basics:
1. Apparently LBFO refers to just about any kind or type of Windows Server NIC Team you could create from the GUI. I know that NOWHERE in the GUI does it say a single thing about "LBFO", it's apparently something you're just supposed to know. It doesn't matter how you change the prioritization or protocol... if you're working in the Windows Server GUI or even using the typical powershell commands that come with Windows Server for creating a NIC team, you're already wrong.
2. From my reading, you need to turn off LACP as it won't work with SET, so go ahead and reconfigure your switch ports back to their default. Go ahead. I'll wait.
3. Don't create a NIC team in Windows Server NIC teaming. Yes, if you already created one in Windows Server 2022, you'll just need to delete it because the conversion tool, like most things Microsoft makes, doesn't work with their own products. No, I have no idea what that means for the myriad of other applications that access NIC teams, but I can tell you that if you look hard enough, you can find an extensive list of all the applications SET doesn't work with, despite many posts making it seem like a panacea. Yes, creating a SET team is apparently a function of Hyper-V, not windows server (although it does support SOME other functions, not ALL), so the fact that nobody explains that and none of the error messages you're seeing are remotely helpful will lead you to making an understandable, but wrong, assumption that you create a SET NIC Team the way you'd create any other team. So make sure you install Hyper-V server functionality first, then worry about creating your team later. (Yes, I know the hyper-v role installation will try to create your virtual switch, because... well... Microsoft is too big for their own good and the left hand never talks with the right hand... so you can't do it from there. Just skip it or create a temporary one and come back to teaming later.)
4. You have to create the SET team from Powershell after you have Hyper-V installed. Apparently, even though all the Microsoft posts and error messages will condescend to you about how they released SET in 2016 and it's now 2022 and what the hell is wrong with you, you're so out of date... they still haven't managed to add it to the GUI in 6 years either, so don't let them make you feel bad. It's actually not too hard to find the documentation on the command once you realize what you need to search for, so if this link is broken by the time you're reading this, just google "switch embedded team powershell command". This is the blog I used to get the command info I was looking for: https://blog.workinghardinit.work/tag/switch-embedded-teaming/
