Nope this isn't for fun. I'm trying to monitor PC activity and this is one of the components that could potentially identify rogue processes related to network traffic.
I'm just manually parsing the CSV file for now. But one other thing I just noticed is the following.
1. If I run xcopy fileA.iso to \\remoteserver\folder
2. The network activity is showing under the svchost.exe -k LocalService process, where it should in reality show under the System Process, whose ID is 4
TcpSend, 13952677, "svchost" (3848), 112, 010.004.038.231, 445, 010.006.140.044, 1200TcpRecv, 13952679, "svchost" (3848), 104, 010.004.038.231, 445, 010.006.140.044, 1200
3. This looks like a bug with XPerf, as it is not correlating network activity to the correct process. I even tried killing the svchost process above and even though I kill the process 3848 above, a newly started xperf trace STILL shows it associated to it even though it's been killed. The process name shows up as Unknown now though.
TcpSend, 13952677, "Unknown" (3848), 112, 010.004.038.231, 445, 010.006.140.044, 1200
TcpRecv, 13952679, "Unknown" (3848), 104, 010.004.038.231, 445, 010.006.140.044, 1200
Looks like this is a generic Windows Trace Log bug. Even if I create a new Trace under the perfmon "Trace Logs" section, the incorrect process id still shows up. I filtered to only trace "Network TCP/IP".
Do you guys know if there is a fix for incorrect processid association for tcp/ip traces?