Teaming with Windows Server 2012

It seems like ever day there are questions about how to team the NICs in Windows Server.  With Broadcom, you have to use BACS, which we all know is not full proof.  Intel makes it a little easier with teaming done in the driver.  Windows Server 8 has made it extremely simple.  You can use the Server Manager (which really calls the exe), Powershell, or the standalone exe to create and manage a team.  Below are the steps to create a team.

Server Manager

1. Open Server Manager (Windows Key and click Server Manager)
2. Local Server
3. Network Adapter Teaming

EXE (The easiest way)

1. Windows Key + R
2. run lbfoadmin.exe

*Using the NIC Teaming Manager, you can now create NIC teams on remote servers.  As well as many other remote features, such as adding roles and features to remote servers.

Steps to create a new team

1. Select the server you want to create the team on.
2. Under teams, click the down arrow next to the "TASKS" drop down.
3. Click on "New Team".
4. In the New Team Wizard, enter a team name.
5. Select the NICs that you want to be in the team.
6. Click Additional Properties
7. Select the teaming mode (Can use Static Teaming, Switch Independent, or LACP)
8. Select the Local Distribution Mode (Can use Address Hash or Hyper-V Port)
9. Select the Primary Team Interface (Can use the Default or Specific VLAN)
10. Click OK.

Once you have created the team, it will show up under the TEAM section and the status should be OK.  If you go and look at the Network Adapters, you will see your physical NICs and the new Team NIC.  If you look at the properties for the physical NICs in the team, you will notice that everything is unchecked except for the Microsoft Network Adapter Multiplexor Protocol.  This is the protocol used for teaming and load balancing.  The actual IP address will be stored in the new Virtual Team NIC.

This can also be done using a PowerShell commandlet.  Here are the steps for PowerShell.

Power Shell

1. Open PowerShell (Windows Key and click Windows PowerShell)
2. New-NetLbfoTeam (exact command:  New-NetLbfoTeam <TeamName> <NIC1>, <NIC2>

In summary, Microsoft has really made great steps to streamline the NIC Teaming process and has eliminated the requirement of 3rd party drivers and software.  I hope to have more for you soon.