Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 26, 2017 10:35 PM
Is there an ETA on when this "HOT FIX" is going to be released?
Some post mentioned it will be earlier February 2017, could you confirm that?
All replies (3)
Thursday, January 26, 2017 11:09 PM | 2 votes
From NIC Teaming failed (Build 10568) Windows 10
"There 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.
(Edit) NIC Teaming however can be done using 3rd party software, just the native LBFO teaming available from Microsoft is not supported on client SKUs.
Adam Rudell | Windows Networking Beta | Microsoft Corporation
Proposed as answer by ARUDELLMicrosoft employee Tuesday, September 06, 2016 4:17 PM
Edited by ARUDELLMicrosoft employee Tuesday, September 27, 2016 1:42 PM"
So 'It is NOT supported on client SKU, and never has been'. So no fix is due. Need third party drivers for teaming but I am not aware of any that do that.
Wednesday, June 12, 2019 10:52 AM
Many motherboard manufacturers are equipping 2 or more on-board network adapters. It's completely absurd that Microsoft does not support native NIC Teaming (Dynamic LACP) on their PRO version of windows.
Wednesday, June 12, 2019 3:46 PM
from Mr. Happy:
"(Edit) NIC Teaming however can be done using 3rd party software, just the native LBFO teaming available from Microsoft is not supported on client SKUs."
If you have Intel NIC, teaming can be accomplished: