You can access that tool directly via the OCS console by selecting Logging... when right-clicking on a Standard server or Enterprise pool object and choosing a New or Existing Debugging Session.
Clicking the Analyze Log Files button will only display components for files that are stored in the C:\WINDOWS\Tracing directory (which is the default directory used to store any saved tracing files.)
But, you can only convert ETL files captured by the OCS logging tool on the server, as the Communicator.ETL files saved on the client workstation's C:\Windows\Tracing folder can not be converted and (from what I've been told) are used to send to MSPS for them to decode and only they have the tools to do so. It also appears that only the SIPstack components files can be analyzed as using the tool in the past that was the only component to appear in the analyze window. I had to send of ABserver log files to MSPS when troubleshooting ABS behavioral issues.
Alternatively, you can simply look through the ETL files with a text editor and weed-out the information you are looking for as much of the data in XML in plain-text, but it is a bit tough to read.
top tip!!
