These include things such as connection issues, certifi cate
validation failures, and client authentication problems. These diagnostics are similar to the
MS-Diagnostics headers and you can view them in the OCS 2007 event log on the OCS
server. Figure 12.11 shows an example of a runtime diagnostics event.
Figure 12.10 Sample Event with Diagnostics Header Information
Managing and Monitoring OCS 2007 ??? Chapter 12 377
Logging Tool
OCS provides a detailed logging tool that is automatically installed with the installation of the
core product. The logging tool allows you to start detailed logging sessions that create trace logs
of various components of OCS. You can use these logs to review detailed diagnostic information
when troubleshooting OCS issues. The logging tool even includes a command to prepare the
logs to send to Microsoft Professional Support Services (PSS) in situations when you need to
work with Microsoft to troubleshoot your OCS deployment. Let??™s take a more in-depth look
at the logging tool.
Figure 12.11 Example of a Runtime Server Diagnostics Event
378 Chapter 12 ??? Managing and Monitoring OCS 2007
The fi rst thing we need to do is enable a new debug session. This will create the trace logs
for storing diagnostic information. To enable a new debug session perform the following steps:
1. Open the OCS MMC by going to Start | Administrative Tools | Offi ce
Communications Server 2007.
2. Expand the tree and locate the server you want to begin to start the debug session.
Pages:
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397