Networking / Security · Risk: High · Documentation Verified
Last verified: 2026-10-26
Microsoft NetLbfo reference: Sets parameters on the specified NIC team. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Set-NetLbfoTeam. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / NetLbfo · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-AsJob
Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete.
-CimSession
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
-Confirm
Prompts you for confirmation before running the cmdlet.
-InputObject (required)
Specifies the input object that is used in a pipeline command.
-LacpTimer
Specifies how often inter-connected devices exchange LACP protocol data units (PDUs) or control messages.
-LoadBalancingAlgorithm
Specifies the load-balancing algorithm the new team uses to distribute network traffic between the interfaces. You can specify one of the following load balancing algorithms: - Dynamic. Uses the source and destination TCP ports and the IP addresses to create a hash for outbound traffic. Moves outbound streams from team member to team member as needed to balance team member utilization. When you specify this algorithm with the *TeamingMode* parameter and the SwitchIndependent value, inbound traffic is routed to a particular team member. - TransportPorts. Uses the source and destination TCP ports and the IP addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces. When you specify this algorithm with the *TeamingMode* parameter and the SwitchIndependent value, all inbound traffic arrives on the primary team member. - IPAddresses. Uses the source and destination IP addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces. When you specify this algorithm with the *TeamingMode* parameter and the SwitchIndependent value, all inbound traffic arrives on the primary team member. - MacAddresses. Uses the source and destination MAC addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces. When you specify this algorithm with the *TeamingMode* parameter and the SwitchIndependent value, all inbound traffic arrives on the primary team member. - HyperVPort. Distributes network traffic based on the source virtual machine Hyper-V switch port identifier. When you specify this algorithm with the *TeamingMode* parameter and the SwitchIndependent value, inbound traffic is routed to the same team member as the switch port's outgoing traffic.
-MemberOfTheTeam
Specifies the network adapter name for which to modify the parameters.
-Name
Specifies the name of the NIC team to modify.
-PassThru
Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.
-TeamNicForTheTeam
Specifies the team interface whose associated NIC team is to be modified.
-TeamingMode
Specifies the mode of the NIC teaming. You can specify one of the following teaming modes: - LACP. Requires configuration on both the switch and the host to identify which links form the team. Uses the Link Aggregation Control Protocol (LACP) to identify links that are connected between the host and a given switch. - Static. Requires configuration on both the switch and the host to identify which links form the team. - SwitchIndependent. Specifies that a network switch configuration is not needed for the NIC team. Because the network switch is not configured to know about the NIC teaming, the team members can be connected to different switches.
-ThrottleLimit
Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Prerequisites
Windows with the NetLbfo module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
Security considerations
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.
Examples
Example 1: Set the teaming mode
Set-NetLbfoTeam -Name "Team1" -TeamingMode LACP
This command sets the teaming mode of the team named Team1 to LACP. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.