# Intel® PROSet for Windows* Device Manager

Intel® PROSet for Windows* Device Manager is an extension to the Windows Device Manager. When you install the Intel PROSet software, additional tabs are automatically added to Device Manager.

| NOTE: You must have administrator rights to install or use Intel PROSet for Windows Device Manager.

## Installing Intel PROSet for Windows Device Manager

Intel PROSet for Windows Device Manager is installed from the Product CD with the same process used to install drivers. You can select Intel PROSet for Windows Device Manager and Advanced Network Services from the Install Options dialog.

| NOTE: Upgrading PROSet for Windows Device Manager may take a few minutes.

## Removing Intel PROSet for Windows Device Manager

Use Add/Remove programs from the Control Panel to uninstall Intel PROSet for Windows Device Manager.

## Changing Intel PROSet Settings Under Windows Server Core

You can use the command line utility prosetcl.exe to change most Intel PROSet settings under Windows Server Core. Please refer to the help file prosetcl.txt located in the \Program Files\Intel\DMIX\CL directory. For iSCSI Crash Dump cofiguration, use the CrashDmp.exe utility and refer to the CrashDmp.txt help file.

## Changing Intel PROSet Settings via Microsoft* Windows PowerShell*

You can use Windows PowerShell* to change most Intel PROSet settings. Install the IntelNetCmdlets module by checking the Windows PowerShell Module checkbox during the driver and PROSet installation process. This should import the cmdlets in the module automatically. If you cannot access the modules, use the Import-Module cmdlet. You may need to restart Windows PowerShell to access the cmdlets.

To use the Import-Module cmdlet, you must specify the path and the name of the module. For example:

`PS c:\> Import-Module -Name "C:\Program Files\Intel\IntelNetCmdlets`\`IntelNetCmdlets`"

See the Microsoft TechNet for more information about the Import-Module cmdlet.

| NOTE: If an adapter is bound to an ANS team, do not change settings using the Set–1NetAdapterAdvanceProperty cmdlet from Windows PowerShell*, or any other cmdlet not provided by Intel. Doing so may cause the team to stop using that adapter to pass traffic. You may see this as reduced performance or the adapter being disabled in the ANS team. You can resolve this issue by changing the setting back to its previous state, or by removing the adapter from the ANS team and then adding it back.

### System requirements for using IntelNetCmdlets:

- Microsoft* Windows* 7, Microsoft Windows Server* 2008 R2, or newer
- PowerShell v3.0, or newer

## Compatibility Notes

The following devices do not support Intel PROSet for Windows Device Manager

- Intel® 82552 10/100 Network Connection
- Intel® 82567V-3 Gigabit Network Connection