Using Office Communications Server 2007 Logging Tool
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
The Microsoft® Office Communications Server 2007 Logging Tool integrates a range of logging and tracing functionality. The functionality available in Office Communications Server 2007 Logging Tool facilitates troubleshooting by capturing logging and tracing information from the product while the product is running. Logging and tracing functionality was previously available only by running OCSLogger.exe as a command-line tool, but is now also available from the Office Communications Server 2007 administrative snap-in on any computer running Office Communications Server 2007 or on which the Office Communications Server 2007 administrative tools are installed. You can use Logging Tool to run debug sessions on any Office Communications Server 2007 server role.
Office Communications Server 2007 Logging Tool generates log files on a per-server basis, so it must be actively running and tracing on each computer for which you want to generate a log.
Note
To view and analyze log files on a computer other than the one on which the logs were captured, you can install and run OCSlogger.exe on the other computer by installing the Office Communications Server administrative tools on that computer. By default, OCSLogger.exe is installed to %ProgramFiles%\Common Files\Microsoft Office Communications Server 2007\Tracing. You can run OCSLogger.exe on computers that are based on the Microsoft Windows® XP or Windows Vista® operating system. In order to run OCSLogger on Windows Vista, you must launch it in an elevated mode (running the application in "Run as Administrator" mode).
This section contains the following topics: