Configuring Advanced Features in Windows Server* Core Installations

Last Reviewed: 15-Sep-2017
Article ID: 000005922

Beginning with version 15.0 of Intel® Network Connections software, you can use the command line utility PROSetCL.exe to configure adapter settings under Windows Server* Core. You can configure adapter settings, teaming, and VLANs from the command line in any version of Microsoft Windows* including Core-only installations.

Intel Network Connections software copies PROSetCL.exe to the \Program Files\Intel\DMIX\CL directory when Intel® PROSet for Windows Device Manager* is installed. Use DxSetup.exe to install Intel PROSet using the command line. Installing the Base Driver and Intel® PROSet via the Command Line provides help for command line installation. If you install only the base drivers, prosetcl.exe does not install. Running DxSetup.exe installs Intel PROSet by default.

Refer to the help file PROSetcl.txt located in the \Program Files\Intel\DMIX\CL directory for basic help using prosetcl.exe.

Configuring a team or VLAN for Hyper-V

To use an ANS Team or VLAN as a Virtual NIC, set up the configuration using prosetcl.exe and nvspbind.exe utilities.

  • Use the prosetcl.exe utility to create the team or VLAN. See the prosetcl.txt file for installation and usage details.
  • Use the nvspbind.exe utility to unbind the protocols on the team or VLAN.

The following is an example of the steps for setting up the configuration:

  1. Use prosetcl.exe to create a team.
    prosetcl.exe Team_Create 1,2,3 MyNewTeam SFT
  2. Use nvspbind to get the team GUID.
    nvspbind.exe -n
  3. Use nvspbind to disable the team bindings.
    nvspbind.exe -d aaaaaaaa-bbbb-cccc-dddddddddddddddd *
  4. Create the virtual NIC by running a remote Hyper-V manager on a different system. See Microsoft's documentation for instructions on how to do this.
  5. Use nvspbind to get the Virtual NIC GUID.
  6. Use nvspbind to enable protocol bindings on the Virtual NIC.
    nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_netbios
    nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_tcpip
    nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_server

Nvspbind.exe (Network virtual service provider bind)

Nvspbind.exe is available for download from the MSDN Code Gallery.


See the version of prosetcl.txt installed with your software for command help.

PROSetcl.txt, 10/31/2012

Power Shell Team Creation Script

Attached is a sample PowerShell script for creating teams. This script:

  1. Enumerates all the network adapters on the local system
  2. Creates a team using:
    1. The first two adapters
    2. Adapter Fault Tolerant (AFT) mode
    3. Named TEAM1

You can specify your own value for the team mode and name:

$TeamingMode = 0
$TeamName = "TEAM1"

$TeamingMode specifies the team type or mode:

Value Team Mode or Type
0 Adapter Fault Tolerance (AFT)
1 Adaptive Load Balancing (ALB)
2 Static Link Aggregation (SLA)
4 IEEE 802.3ad Link Aggregation (LAG)
5 Switch Fault Tolerance (SFT)
6 Virtual Machines Load Balancing (VMLB)
Note Older versions of Intel PROSet may have a different value for VMLB team type. Make sure you are using the latest software version.

This script was tested on Microsoft Windows* Server 2012 and Server 2008 R2.

CreateTeamps1.txt, 3/21/2013, 3 KB

Related topics
Installing the Base Driver and Intel® PROSet via the Command Line
User Guides for Intel® Ethernet Adapters
Save and Restore Command Line Tool
VBS Scripts Used for Command Line Configuration
How do I use Teaming with Advanced Networking Services (ANS)?

This article applies to:

Active Products

Intel® Ethernet Controller X540-AT2