Feature Request: Windows 11 NIC Teaming - Merge GitHub Project

[bseklecki_ge]

Finally someone has created a project to properly import the Windows Server 2022 LBFO kernel modules into Windows 11.

GitHub - hifihedgehog/Windows11LBFO: Adds LBFO NIC teaming support to your Windows 11 system with a single script run.

Adds LBFO NIC teaming support to your Windows 11 system with a single script run. - hifihedgehog/Windows11LBFO

github.com

(I validated that it functions on 24H2/Win11 LTSC 2024)

The sketchy thing is that he's redistributing binaries from Server 2022 addon / FOD ISO right there on GitHub.

( Paradoxically, he's doing it on GitHub, a Microsoft subsidiary. I dont think a cease & desist order will take long to process before this project disappears! Or, they have the silent blessing of Microsoft and this is their way of silently admitting a strategic mistake. )

Anyway, for NTLite:

If you wanted to offer to merge/integrate this as a feature, perhaps you could do it but require that operator to place the licensed binaries for LBFO Kernel module from the Server 2022 FOD ISO manually?

 

[garlin]

You have a short memory:
NIC Teaming / Load Balancing and Failover (LBFO) / Microsoft-Windows-NetworkTeamInstaller Optional Feature?

It will never be offered as a NTLite feature, because it violates the Licensing Agreement:

work around any technical limitations in the software that only allow you to use it in certain ways;

Technically it's not too difficult to follow the original article, and understand the basic steps are:

- import the driver files into the image​

- import reg files to sign the files, and recreate the missing service​

 

[WizKid]

It will never be offered as a NTLite feature, because it violates the Licensing Agreement:

Not only that, but said feature is a feature of an OS meant to be used for routing. Take for example my Ubiquiti UniFi OS router:



Said distro is based on Debian 11.

Windows Client SKUs are not designed to be used in such a role, hence the EULA limitation.

 

[garlin]

This request is like asking to port Server File De-duplication to Client SKU's. Some people know how, but it contravenes the EULA.

 

[WizKid]

This request is like asking to port Server File De-duplication to Client SKU's. Some people know how, but it contravenes the EULA.

As in copy-on-write?

APFS (Apple File System) mandates such.

 

[garlin]

https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/overview

 

[WizKid]

https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/overview

I stand corrected then. APFS doesn't do deduplication either. When you duplicate a file on an APFS volume, it just creates a hard link, just like NTFS