You also learned how you can use these tools to locate, diagnose,
and resolve problems that can occur in OCS 2007. In addition, you were introduced to
CDRs, which allow you to track usage trends. Tracking these trends allows you to properly
plan for network and server capacity. Finally, you discovered how the OCS 2007 MP for
SCOM 2007 will allow you to proactively monitor your OCS 2007 infrastructure.
Solutions Fast Track
Using Call Detail Records
?› You can use CDRs to track and trend usage statistics.
?› CDRs are maintained in a SQL database to maintain historical data.
?› CDR reports can be easily generated by Microsoft Excel or SQL Server Reporting
Services.
OCS Troubleshooting Tools
?› OCS provides several tools for diagnosing and troubleshooting problems.
?› You can install the OCS 2007 Resource Kit to provide additional diagnostic tools,
including the Snooper tool.
?› You can use the Best Practices Analyzer to search for confi guration problems.
System Center Operations Manager 2007
?› System Center Operations Manager (SCOM) is the preferred system for proactively
monitoring an OCS 2007 infrastructure.
?› You can confi gure SCOM to monitor OCS 2007 deployments with a minimal
amount of effort setting up rules and alerts.
402 Chapter 12 ??? Managing and Monitoring OCS 2007
Frequently Asked Questions
Q: What is the proper process to troubleshoot problems with OCS 2007?
A: Review the event logs or SCOM alerts; run the post-install Validation Wizard; run the Best
Practices Analyzer to ensure that your servers are confi gured properly; run the OCS 2007
logging tool; run the Snooper tool if you??™re diagnosing SIP issues; contact Microsoft PSS.
Pages:
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411