This is the built-in help made by Microsoft for the command 'Start-NetEventSession', 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.
Starts event and packet capture for a network event session.
Start-NetEventSession [-Name] <String> [-CimSession [<CimSession>]] [-PassThru] [-ThrottleLimit [<Int32>]] [-Confirm] [-WhatIf] [<CommonParameters>]
Start-NetEventSession [-CimSession [<CimSession>]] [-PassThru] [-ThrottleLimit [<Int32>]] [-Confirm] [-WhatIf] [<CommonParameters>]
The Start-NetEventSession cmdlet starts event and packet capture for a network event session. A session controls how the computer logs events and, optionally, network
traffic, or packets. Use the New-NetEventSession cmdlet to create a session. Before you can start logging, add network event providers to a session. A network event provider
logs events and network traffic as Event Tracing for Windows (ETW) events.
If a session is currently running, you cannot start it. Use the Get-NetEventSession cmdlet to see session status.
Online Version: http://go.microsoft.com/fwlink/?LinkID=294405
Example 1: Start a session
PS C:\>New-NetEventSession -Name "Session38"
PS C:\> Add-NetEventProvider -Name "Microsoft-Windows-TCPIP" -SessionName "Session38"
PS C:\> Start-NetEventSession -Name "Session38"
This example creates a session, adds a provider to it, and then starts the session.
The first command creates a session named Session38 by using the New-NetEventSession cmdlet.
The second command adds a provider to the session by using the Add-NetEventProvider cmdlet. A session must have a provider in order to log events.
The third command starts the session named Session38.