Forum Discussion
Feature Request: Please Remove NIC Teaming from Windows Server Manager and more
Dear MSFT Windows Server Team, Since there have been unexpected changes but appreciated on Windows Server Manager (vNext shows Azure Arc status) I would appreciate if vNext could have the follow...
I would love to keep LBFO NIC Teaming. I have bad experiences with vswitches/SET-Teaming and Server 2022, leading to bluescreen-loops within a minute after after boot. Intel driver issue according to the logs - same reason why I don't use RDMA with intel nics. I don't trust Intel drivers. I was lucky that I could disable SET-Teaming without needing to reinstall. Classical teaming works perfect, even though it required the Hyper-V switch to be configured via powershell. Thee-node hyper-v cluster runs like a charm for 10 month now. I agree on offering the SET variant in the GUI of course.
Joachim_Otahal I hear you. Intel NICs are not an optimal choice for server networking nowadays, due to way how drivers quality. And this even though they might be and need to be listed in the https://www.windowsservercatalog.com/ in the first place
I hope that Dan Cuomo can help to improve this in his new role (I learnt about from LinkedIn), don't have any expectations for older NICs such as X722 and before.