Automatically configure NIC Teaming in Windows Server 2012

Starting with Windows Server 2012, Microsoft has provided built-in support for NIC teaming. Insight Control server provisioning provides a script in the script repository that will enable NIC Teaming. For more information on the Configure NIC Teaming for Windows script see the Insight Control Server Provisioning Build Plans Reference Guide.


	IMPORTANT: Imaging with NIC teams are not supported. Dissolve any NIC teams before creating an image of a server and then recreate the teams after imaging is complete. Deploying an image with NIC Teaming enabled causes duplicate MAC address on the server. This duplication causes a network failure.


	IMPORTANT: When creating NIC teaming using IC server provisioning: If the NIC through which the agent communicates back to IC server provisioning is disconnected or modified, then the agent may not be able to connect back to appliance and update the completion of the job status. Also, no further management from the appliance to the target server will be possible. Hardware inventory related to NIC teaming may not get updated back to the appliance.

For a list of NIC teaming related commands under PowerShell, enter the following command under PowerShell CLI: get-command -Module netlbfo.

Enable NIC Teaming in an OS Build Plan for a new Windows server 2012 OS install

Make a copy of the Windows Server 2012 scripted install OS Build Plan by selecting Actions→Save As from the OS Build Plan screen.
Edit the new OS Build Plan to add the Configure NIC Teaming for Windows script as the last step of the new OS Build Plan, after the Wait for HP SA Agent step. To do this select Add steps and edit as follows; then select Add to save the file:

Type: Run script

Script: Configure NIC Teaming for Windows

Parameter: Enter the required parameters to specify which NICs to team, using the following format: FieldName,Value[,Value][,Value...]

This is a comma separated list and no extra spaces should be used when specifying parameters. Any spaces specified will be read as part of the value.
- FieldName — lists the NIC characteristics that will be specified in the other parameters. Valid name are:
  - Name
  - InterfaceDescription
  - ifIndex
  - Status
  - MacAddress
  - LinkSpeed
- Values — The value to be checked that corresponds to the specified FieldName parameter.
  
  Status,Up
  
  Name,Ethernet,Ethernet2
  
  MacAddress,18-A9-05-C5-E1-B3,18-A9-05-C5-E1-B4
Click OK to save the OS Build Plan.


	NOTE: Adding another reboot step after the NIC teaming script is not necessary because modifying the OS for NIC teaming does not require a reboot.

Create a standalone OS Build Plan to enable NIC Teaming on an already installed Windows Server 2012

Make a copy of the ProLiant HW — Boot WinPE Service OS Build Plan by selecting Actions→Save As from the OS Build Plan screen.
Edit the new OS Build plan with the following:
1. Delete all three steps so you have an empty Build Plan..
2. Add a new step and choose the Configure NIC Teaming for Windows script. To do this select Add steps and edit as follows; then select Add to save the file.
  
  Type: Run script
  
  Script: Configure NIC Teaming for Windows
  
  Parameter: Enter the parameters to specify which NICs to team, using the following format:FieldName,Value[,Value][,Value...]
  
  This is a comma separated list and no extra spaces should be used when specifying parameters. Any spaces specified will be read as part of the value.
  - FieldName — lists the NIC characteristics that will be specified in the other parameters. Valid name are:
    Name
    
    InterfaceDescription
    
    ifIndex
    
    Status
    
    MacAddress
    
    LinkSpeed
  - Value — The value to be checked that corresponds to the specified FieldName parameter. Parameter examples:
    
    Status,Up
    
    Name,Ethernet,Ethernet2
    
    MacAddress,18-A9-05-C5-E1-B3,18-A9-05-C5-E1-B4
Click OK to save the Build Plan.

prev	up	next
Enable Windows Hyper-V role after a Windows OS installation	home	Create a Build Plan to enable virtualization