This is the built-in help made by Microsoft for the command 'Add-NetEventVmSwitch', 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 Hyper-V virtual switch as a filter on a provider.
Add-NetEventVmSwitch [-Name] <String> [-CimSession [<CimSession>]] [-ThrottleLimit [<Int32>]] [-Confirm] [-WhatIf] [<CommonParameters>]
The Add-NetEventVmSwitch cmdlet adds a Hyper-V virtual switch as a filter on a Remote Packet Capture provider. Use this cmdlet multiple times to add multiple Hyper-V virtual
switches. To get existing Hyper-V virtual switches, use the Get-NetEventVmSwitch cmdlet.
The protocol stack uses multiple layers to transmit, receive, and process network traffic as packets. The provider logs network traffic as Event Tracing for Windows (ETW)
Online Version: http://go.microsoft.com/fwlink/?LinkId=294386
Example 1: Add a Hyper-V virtual switch on a provider
PS C:\>New-NetEventSession -Name "NESession01"
PS C:\> Add-NetEventPacketCaptureProvider -SessionName "NESession01"
PS C:\> Add-NetEventVMSwitch -Name �Network Adapter 2 - Virtual Switch"
This example adds a Hyper-V virtual switch as a filter on the Remote Packet Capture provider for a network session. After you complete these commands to configure the
network session, you can start and stop the event and packet capture for the network session by using the Start-NetEventSession and Stop-NetEventSession cmdlets.
The first command uses the New-NetEventSession cmdlet to create a network session named NESession01.
The second command uses the Add-NetEventPacketCaptureProvider cmdlet to add a Remote Packet Capture provider for the session named NESession01.
The third command adds a Hyper-V virtual switch as a filter on the Remote Packet Capture provider.