How to Configure NIC Teaming on Windows Server
Applies to: Windows Server 2019, 2022 and 2025.
NIC Teaming can provide adapter redundancy and traffic distribution on supported physical hosts. Hyper-V Switch Embedded Teaming has different requirements and is preferred for some virtualization designs.
Network changes can immediately interrupt management access. Maintain console access, export the current configuration and use approved test addresses. Visit networkmanager.info for managed Windows VPS services.
Prerequisites
- Use matching supported adapters and drivers.
- Keep console access.
- Document switch configuration and VLANs.
- Confirm whether the host runs Hyper-V.
Procedure
Step 1: List adapters
Identify candidates by MAC, speed and status.
Get-NetAdapter | Select Name,InterfaceDescription,MacAddress,LinkSpeed,StatusStep 2: Review teams
Check existing configuration.
Get-NetLbfoTeam -ErrorAction SilentlyContinueStep 3: Create a team
Use approved independent mode for a switch-independent example.
New-NetLbfoTeam -Name 'ServerTeam' -TeamMembers 'Ethernet 1','Ethernet 2' -TeamingMode SwitchIndependent -LoadBalancingAlgorithm DynamicStep 4: Configure team interface
Assign VLAN and IP only after the team is stable.
Step 5: Test link loss
Disable one member during a maintenance test and confirm management continuity.
Verification
Review team health, members and team interface.
Get-NetLbfoTeam -Name ServerTeam
Get-NetLbfoTeamMember -Team ServerTeam
Get-NetAdapter -Name ServerTeamRollback
Move IP configuration away from the team before Remove-NetLbfoTeam. Restore individual adapter settings through console.
Security and operational notes
Microsoft has deprecated LBFO for some newer scenarios; evaluate Switch Embedded Teaming for Hyper-V according to the target release.
