Não, não é possível obter o NMI teamin em SKUs do cliente Windows 10. Mas disponível para SKUs do servidor.
A partir da versão 14393 (atualização de aniversário), esse recurso de agrupamento da NIC foi bloqueado ou removido para sempre. Parece que o recurso foi adicionado por engano ao cliente Windows 10 SKUs. Quando você coloca o comando New-NetLbfoTeam no PowerShell, por exemplo, New-NetLbfoTeam -Name "NewTeam" -TeamMembers "Ethernet", "Ethernet2"
, o erro é exibido da seguinte forma
New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO
is not supported on this SKU. At line:1 char:1
+ New-NetLbfoTeam -Name "NewTeam" -TeamMembers "Ethernet", "Ethernet2"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_NetLbfoTeam:root/Standa rdCimv2/MSFT_NetLbfoTeam)
[New-NetLbfoTeam], CimException
+ FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam
Aprincipalrazãofoidadaem Social.TechNet.Microsoft: Nic Teaming quebrado na compilação 10586 da seguinte forma (citado):
"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."