How to Configure NIC Teaming and Load Balancing in Windows Using PowerShell

Enterprise workloads—such as virtualisation hosts (Hyper-V), file servers, and database nodes—require continuous network availability and high-throughput data transfer. Relying on a single physical network interface card (NIC) creates a single point of failure and restricts throughput to the capacity of a single cable.

Windows provides native NIC Teaming, also known as Load Balancing and Failover (LBFO). This technology bonds multiple physical network adapters into a unified, virtual team interface (tNIC). If one physical adapter, cable, or switch port fails, network traffic transparently fails over to remaining interfaces without interrupting active TCP connections, while simultaneously aggregating bandwidth across all active links.

Understanding NIC Teaming Modes and Algorithms

Before configuring a team, select the architecture that aligns with your network switch infrastructure:

Teaming Modes

• SwitchIndependent (Default): Does not require switch configuration. The physical network adapters can connect to different, unstacked switches for maximum hardware redundancy.
• LACP (Link Aggregation Control Protocol): Requires an 802.1ax/802.3ad dynamic trunk configured on the physical network switch. Dynamically aggregates bandwidth across links.
• Static: Requires static link aggregation (EtherChannel / trunk) configured on the switch.

Load Balancing Algorithms

• Dynamic (Recommended): Evaluates TCP stream characteristics and packet sizes in real time, distributing outbound flows across all adapters for optimal throughput and low latency.
• AddressHash: Hashes packet header attributes (MAC addresses, IP addresses, or ports) to assign flows to specific NICs.
• HyperVPort: Distributes network traffic based on virtual machine Hyper-V switch port IDs, ideal for multi-tenant virtualisation clusters.

Inspecting Physical Network Adapters

Open an elevated PowerShell prompt on Windows:

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

Identify the names of the physical adapters you wish to bond (for example, Ethernet 1 and Ethernet 2).

Creating a NIC Team Using New-NetLbfoTeam

To create a new network team named ProductionTeam using SwitchIndependent mode and Dynamic load balancing:

New-NetLbfoTeam -Name "ProductionTeam" -TeamMembers "Ethernet 1", "Ethernet 2" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false

PowerShell creates the virtual team interface and binds the physical adapters. Confirm the creation and health of the team:

Get-NetLbfoTeam -Name "ProductionTeam"

Output details:

Name                   : ProductionTeam
Members                : {Ethernet 1, Ethernet 2}
TeamNics               : ProductionTeam
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : Dynamic
Status                 : Up

Configuring an Active/Standby Failover Architecture

In high-reliability deployments, you may designate one primary adapter as active and a secondary adapter as an idle standby that only engages if the primary fails:

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

To restore both adapters to active load-balancing operation:

Set-NetLbfoTeamMember -Name "Ethernet 2" -AdministrativeMode Active

Assigning IP Configuration to the Virtual Team Adapter

Once bonded, IP addresses, subnet masks, DNS servers, and default gateways must be configured on the resulting team interface (ProductionTeam), not on individual physical members:

# Configure static IPv4 address and default gateway
New-NetIPAddress -InterfaceAlias "ProductionTeam" -IPAddress "192.168.10.50" -PrefixLength 24 -DefaultGateway "192.168.10.1"

# Configure DNS server addresses
Set-DnsClientServerAddress -InterfaceAlias "ProductionTeam" -ServerAddresses "192.168.10.10", "192.168.10.11"

Testing Failover and Auditing Member Status

To verify team resilience, inspect individual member statuses in real time:

Get-NetLbfoTeamMember -Team "ProductionTeam" | Select-Object Name, FailureReason, LinkStatus, AdministrativeMode

Physically unplug the network cable from Ethernet 1. Running the command reveals Ethernet 1 status changes to LinkDown while ProductionTeam remains Up, confirming seamless hardware failover.

Removing or Modifying the Team

To decommission a team and restore physical adapters to standalone operation:

Remove-NetLbfoTeam -Name "ProductionTeam" -Confirm:$false

Deploying NIC Teaming via PowerShell provides scalable network redundancy and throughput aggregation across mission-critical Windows enterprise servers.