пробовал без LACPНу с LACP пробовать есть смысл только в том случае, если оно поддерживается и настроено на сетевом оборудовании.
New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU.There are no native LBFO capabilities on Win10. Microsoft does not support client SKU network teaming.See Adam Rudell [MSFT] Microsoft employee post Tuesday, September 06, 2016 4:16 PM
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
It was a defect in Windows 10 build 10240 that “New-NetLbfoTeam”:cry: