Searching the Log Files

Since most cases will be covered by the default AlwaysOn scenario, administrators can begin troubleshooting by searching for a specific pool or user with the Search-CsLogging cmdlet.

For example, to search for a specific user’s traffic on a single pool during a known time frame, use this:

Search-CsClsLogging -Pools LYNCPOOL1.companyabc.com -Uri "[email protected]" -StartTime "12/9/2012 10:00AM" -EndTime "12/9/2012 1:00 PM" -MatchAll

By default, any parameter included in the search is considered an acceptable match. That is to say that the -MatchAny parameter is always assumed unless the administrator specifies -MatchAll within the search. The preceding example would have returned all traffic on LYNCPOOL1.companyabc.com, all traffic from the user [email protected], and all traffic in the organization between 10:00 a.m. and 1:00 p.m. on 12/9/2012 if -MatchAll had not been specified.

Alternatively, use the following syntax to search for a single user’s traffic across all pools in the organization, which is the really powerful part of the new service:

Search-CsClsLogging -Uri "[email protected]"