How to Configure Teaming Network Adapters on Windows Server 2016

Network adapter teaming, also known as NIC teaming or Load Balancing/Failover (LBFO), allows you to combine multiple physical network adapters into a single logical interface. On Windows Server 2016, NIC teaming is a built-in feature that provides increased bandwidth, redundancy, and fault tolerance. When one adapter in the team fails, traffic automatically fails over to the remaining adapters without interrupting active connections. This guide walks you through configuring NIC teaming using both the graphical interface and PowerShell.

Before you begin, ensure you have at least two physical network adapters installed in your server. The adapters do not need to be identical models or speeds, although using matched hardware is generally recommended for predictable performance. NIC teaming works with both wired Ethernet adapters and some wireless adapters, though wireless teaming has significant limitations and is rarely used in production environments.

Understanding Teaming Modes

Windows Server 2016 supports three teaming modes. Switch Independent mode requires no configuration on the switch and works with any switch, including different switch models. The adapters can be connected to different switches, which provides the highest level of fault tolerance. Static Teaming (IEEE 802.3ad) requires manual configuration on the switch to define the link aggregation group. LACP (Link Aggregation Control Protocol) uses the 802.1AX standard and negotiates team membership automatically between the server and the switch. LACP is the most common enterprise choice when switch support is available.

You also choose a load balancing algorithm. Address Hash distributes traffic based on hashing the source and destination address components. Hyper-V Port mode is designed for Hyper-V environments and distributes traffic based on the virtual switch port. Dynamic mode, introduced in Windows Server 2012 R2, combines outbound load balancing with Hyper-V Port inbound handling and is the recommended default for most workloads.

Configuring NIC Teaming via Server Manager

Open Server Manager from the Start menu or taskbar. In the left navigation panel, click Local Server. Locate the NIC Teaming property in the Properties section. It will show Disabled by default. Click the Disabled link to open the NIC Teaming configuration window.

The NIC Teaming window shows all available adapters. In the Adapters and Interfaces section, select the adapters you want to add to the team by holding Ctrl and clicking each one. Right-click the selection and choose Add to New Team. Give the team a descriptive name such as TeamProduction. In the Additional Properties section, choose your teaming mode, load balancing mode, and specify a standby adapter if desired. Click OK to create the team. Windows will create a new virtual network adapter representing the team. You can assign IP addresses to this virtual adapter just like any other adapter.

Configuring NIC Teaming with PowerShell

PowerShell provides full control over NIC teaming and is ideal for scripted deployments. The following commands demonstrate creating and configuring a team.

First, view available network adapters:

Get-NetAdapter

Create a new NIC team using two adapters in Switch Independent mode with Dynamic load balancing:

New-NetLbfoTeam -Name "TeamProduction" -TeamMembers "Ethernet","Ethernet 2" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic

Verify the team was created successfully:

Get-NetLbfoTeam

View team members and their status:

Get-NetLbfoTeamMember

Add an additional adapter to an existing team:

Add-NetLbfoTeamMember -Name "Ethernet 3" -Team "TeamProduction"

Set a specific adapter as standby (active-passive configuration):

Set-NetLbfoTeamMember -Name "Ethernet 2" -Team "TeamProduction" -AdministrativeMode Standby

Configure the team to use LACP mode instead:

Set-NetLbfoTeam -Name "TeamProduction" -TeamingMode Lacp -LacpTimer Fast

Assigning IP Addresses to the Team Interface

Once the team is created, Windows creates a virtual adapter named after your team. Assign a static IP address to it:

New-NetIPAddress -InterfaceAlias "TeamProduction" -IPAddress 192.168.1.10 -PrefixLength 24 -DefaultGateway 192.168.1.1

Set the DNS servers:

Set-DnsClientServerAddress -InterfaceAlias "TeamProduction" -ServerAddresses 192.168.1.1,8.8.8.8

Creating VLAN Interfaces on a Team

You can create multiple virtual interfaces on a team, each associated with a different VLAN. This is common when the team is connected to a trunk port on a switch:

Add-NetLbfoTeamNic -Team "TeamProduction" -VlanID 10
Add-NetLbfoTeamNic -Team "TeamProduction" -VlanID 20

Each VLAN NIC appears as a separate adapter in the system, allowing independent IP configuration per VLAN.

Removing a NIC Team

To remove a NIC team and return adapters to standalone operation:

Remove-NetLbfoTeam -Name "TeamProduction"

NIC teaming on Windows Server 2016 is a straightforward way to improve network reliability and throughput without requiring specialized hardware. Switch Independent mode is the quickest to deploy since it requires no switch configuration, while LACP offers the most robust enterprise-grade link aggregation when supported by your switching infrastructure. Always test failover behavior after configuration by physically disconnecting one adapter to verify traffic continues uninterrupted through the remaining team members.