PowerShell Logo Small


This is the built-in help made by Microsoft for the command 'Add-NetEventNetworkAdapter', in PowerShell version 5 - as retrieved from Windows version 'Microsoft Windows Server 2012 R2 Standard' PowerShell help files on 2016-06-23.

For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.


Adds a network adapter as a filter on a provider.


Add-NetEventNetworkAdapter [-Name] <String> [[-PromiscuousMode] [<System.Boolean>]] [-CimSession [<CimSession[]>]] [-ThrottleLimit [<Int32>]] [-Confirm] [-WhatIf]

Search powershellhelp.space


The Add-NetEventNetworkAdapter cmdlet adds a network adapter as a filter on a Remote Packet Capture provider. The protocol stack uses multiple layers to transmit, receive,
and process network traffic, or packets. The provider logs network traffic as Event Tracing for Windows (ETW) events.

Use this cmdlet multiple times to add several adapters. To see which adapters currently belong to a provider, use the Get-NetEventNetworkAdapter cmdlet.

When you add an adapter to provider in a session that is currently running, stop and start the session for your changes to take effect. Use the Stop-NetEventSession cmdlet
to stop a session and the Start-NetEventSession cmdlet to restart it.



Online Version: http://go.microsoft.com/fwlink/?LinkID=294381




Example 1: Add a network adapter

PS C:\>New-NetEventSession -Name "Session38"
PS C:\> Add-NetEventPacketCaptureProvider -SessionName "Session38"
PS C:\> Add-NetEventNetworkAdapter -Name "Ethernet01"

This example creates a network event session, adds a provider, and then adds a network adapter.

The first command uses the New-NetEventSession cmdlet to create a network event session named Session38.

The second command adds a provider to the session named Session38 by using the Add-NetEventPacketCaptureProvider cmdlet. A session must have a provider in order to capture

The third command adds a network adapter. After you create and configure the session, use the Start-NetEventSession cmdlet to start capturing packets.