There are at least three (3) methods of enabling a perfmon log using logman.
|1||The perfmon is setup locally on the machine being monitored. The most common method.||Setting a local perfmon in a Windows client or Windows Server.|
|2||The perfmon is setup from a remote machine, to monitor several machines. The perfmon is setup locally on each of the machines being monitored. Great when you are setting up local perfmon’s on a server farm or have several machines that you need to monitor.||Setting a remote perfmon Windows Server 2012 style...|
|3||The perfmon is setup remotely. The second (2nd) most common method.
When is this usually useful? Do you have a Windows client or Windows Server that randomly become unresponsive to a local login or a domain login? You are able to ping the machine but cannot open a UNC share (\\MachineName\ShareName)? Where the only method to recover is to power off the machine and restart?
|Setting a remote perfmon in a Windows client or Windows Server.|
I hope this helps clarify why there are three (3) posts for setting a perfmon.