The Centralized Logging Service (CLS) that we mentioned is for sure a powerful feature to troubleshoot Lync issues. However, in some specific scenarios, for example, when we need to quickly change the protocols that we are logging, we prefer to use a different tool to trace the protocol stack, the OCSLogger.exe tool.
Like Snooper, it is part of the Lync Server 2013 Debugging Tools. There are a couple of advantages to using OCSLogger over CLS. First and foremost, we should know that we have a graphical interface, rather than PowerShell, to manage the logging parameters. The second one is that we are able to change the protocols and features that we are tracing in a fast-paced manner. We will take a quick look at how the OCSLogger works.