We help IT Professionals succeed at work.

NIC Teaming in Windows 10

8,321 Views
Last Modified: 2017-11-28
I tried doing a nic teaming on my windows 10 machine but  The LBFO feature is not currently enabled, or LBFO is not supported on this SKUit is not supported, sometimes it the cards that is not compatible, does anyone did this and can recommend a nic cards that will allow teaming?

Currently have a
Intel(R) 82574L Gigabit Network Connection
Intel(R) 82574L Gigabit Network Connection
Realtek PCIe GBE Family Controller
Comment
Watch Question

IT Specialist
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Windows 10 does not have native teaming. That is a server-only feature. And since it was introduced in 2012, many newer NICs have dumped their own teaming feature from their drivers.

If you want teaming in windows 19, you'll have to find a NIC where the vendor still offers their own teaming solution via driver/software *and* supports windows 10.  

It is a rare request. Usually when teaming is needed, you'd want to be running windows server anyways. I'd strongly look at why you want to do this via windows 10. It probably isn't a good fit.
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Regarding the first intel link, that actually won't work.  New-LBFOTeam is actively blocked on current builds on windows 10.  To quote Microsoft's official stance from https://social.technet.microsoft.com/Forums/en-US/66166918-5b67-4754-89e5-a2572b1888a2/nic-teaming-failed-build-10568-windows-10?forum=win10itpronetworking:

here are no native LBFO capabilities on Win10. Microsoft does not support client SKU network teaming.

It was a defect in Windows 10 build 10240 that “New-NetLbfoTeam” wasn’t completely blocked on client SKUs.  This was an unintentional bug, not a change in the SKU matrix.  All our documentation continued to say that NIC Teaming is exclusively a feature for Server SKUs.

While the powershell cmdlet didn’t outright fail on client, LBFO was in a broken and unsupported state, since the client SKU does not ship the mslbfoprovider.sys kernel driver.  That kernel driver contains all the load balancing and failover logic, as well as the LACP state machine.  Without that driver, you might get the appearance of a team, but it wouldn’t really do actual teaming logic.  We never tested NIC Teaming in a configuration where this kernel driver was missing.

In the 10586 update (“Fall update”) that was released a few months later, “New-NetLbfoTeam” was correctly blocked again.

In the 14393 update (“Anniversary update”), we continued blocking it, but improved the error message.

The bottom line is that customers should NOT attempt to create teams on client SKU.  It is NOT supported on client SKU, and never has been.  Classic NIC Teaming continues to be supported in Windows Server 2016.
William MillerIT Specialist
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Abraham DeutschIT professional
Top Expert 2016

Author

Commented:
Thank you for your help
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.