Introduction to NIC Teaming on Windows Server 2019

NIC Teaming (also known as Link Aggregation or Network Adapter Bonding) allows you to combine two or more physical network adapters into a single logical adapter. In Windows Server 2019, NIC Teaming is built in as a feature called Load Balancing and Failover (LBFO). The primary benefits are increased bandwidth through aggregation, fault tolerance through automatic failover when one adapter fails, and simplified management through a single logical interface. Windows Server 2019 supports teaming of up to 32 adapters per team.

Windows Server 2019 NIC Teaming supports three teaming modes: Switch Independent (no switch configuration required), LACP/802.3ad (requires switch support for Link Aggregation Control Protocol), and Static Teaming (requires manual switch configuration). It also supports two load-balancing algorithms: Address Hash (distributes outbound traffic based on a hash of IP/MAC/port) and Hyper-V Port (distributes traffic based on virtual machine MAC addresses).

Creating a NIC Team via PowerShell

View available network adapters before teaming:

Get-NetAdapter | Select Name, InterfaceDescription, Status, LinkSpeed

Create a Switch Independent team with two adapters using Address Hash load balancing:

New-NetLbfoTeam -Name "Team1" -TeamMembers "Ethernet 1","Ethernet 2" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm HyperVPort

For LACP (IEEE 802.3ad) mode (requires switch-side configuration with port channel or LACP): 

New-NetLbfoTeam -Name "StorageTeam" -TeamMembers "NIC1","NIC2","NIC3","NIC4" -TeamingMode LACP -LoadBalancingAlgorithm HyperVPort

Verify the team was created:

Get-NetLbfoTeam

Check team member status:

Get-NetLbfoTeamMember -Team "Team1"

Configuring Team NIC IP Address

After creating the team, a new virtual adapter named “Team1” appears in the network adapter list. Assign it a static IP address:

New-NetIPAddress -InterfaceAlias "Team1" -IPAddress 192.168.1.100 -PrefixLength 24 -DefaultGateway 192.168.1.1
Set-DnsClientServerAddress -InterfaceAlias "Team1" -ServerAddresses 192.168.1.10,192.168.1.11

Verify the IP configuration on the team interface:

Get-NetIPAddress -InterfaceAlias "Team1"

Creating Team Interfaces (VLANs)

You can create multiple virtual team interfaces (team NICs) from a single physical team, each assigned to a different VLAN. This is useful for Hyper-V hosts that need separate management, storage, and VM traffic VLANs on the same team:

# Add a VLAN interface for management (VLAN 10)
Add-NetLbfoTeamNic -Team "Team1" -VlanID 10 -Name "Team1-MGMT"

# Add a VLAN interface for storage (VLAN 20)
Add-NetLbfoTeamNic -Team "Team1" -VlanID 20 -Name "Team1-Storage"

# Add a VLAN interface for VMs (VLAN 30)
Add-NetLbfoTeamNic -Team "Team1" -VlanID 30 -Name "Team1-VMs"

Assign IP addresses to each VLAN interface:

New-NetIPAddress -InterfaceAlias "Team1-MGMT" -IPAddress 10.10.1.100 -PrefixLength 24
New-NetIPAddress -InterfaceAlias "Team1-Storage" -IPAddress 10.20.1.100 -PrefixLength 24

Configuring Active-Standby Mode

For a simple active-standby failover team where one adapter is always in standby mode (useful for simple redundancy without load balancing):

New-NetLbfoTeam -Name "FailoverTeam" -TeamMembers "Ethernet 1","Ethernet 2" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm HyperVPort

# Set Ethernet 2 as the standby adapter
Set-NetLbfoTeamMember -Name "Ethernet 2" -Team "FailoverTeam" -AdministrativeMode Standby

View member administrative modes:

Get-NetLbfoTeamMember -Team "FailoverTeam" | Select Name, AdministrativeMode, OperationalMode

Testing Failover

Test NIC team failover by disabling one adapter:

Disable-NetAdapter -Name "Ethernet 1" -Confirm:$false

Verify the team is still functional using ping or by checking the team status:

Get-NetLbfoTeam -Name "Team1" | Select Name, Status
ping 192.168.1.1 -t

Re-enable the adapter:

Enable-NetAdapter -Name "Ethernet 1"

Removing a NIC Team

To remove a NIC team:

Remove-NetLbfoTeam -Name "Team1"

This unbinds the member adapters and removes the virtual team interface. Each physical adapter returns to individual operation. NIC Teaming in Windows Server 2019 is a zero-cost high-availability feature for network adapters that every production server should use, especially Hyper-V hosts and file servers where network availability is critical.