Problems commonly occur when Office Communications Server systems configuration does not match the topology in which they are installed. Additionally, network outages and infrastructure such as firewalls or proxies can introduce problems that were not planned for during initial testing or installation. Identifying helpful diagnostic resources and presenting specific scenario troubleshooting sessions in detail, Part V provides expert guidance and diagnostic frameworks to help efficiently identify and resolve problems.
Office Communications Server and Office Communicator include several tools to help identify and diagnose problems. Event logs are used to identify issues on the server and can now be enabled for the client as well. Both the server and client have the ability to enable diagnostic logs that provide an incredible level of technical detail (sometimes much more information than is necessary to work through a problem). Chapter 16 presents event log examples with explanations and helpful next steps and walks through gathering diagnostic information and putting it to use in general terms.
When involved diagnostics are necessary, Chapter 17 is a helpful reference. This chapter explores a few detailed scenarios—including protocol failures, federation-related errors, and others—to provide the reader expert assistance without the need to spend time contacting support or wait for newsgroup or forum answers.
3.17.176.167