5. “The” tool that you will use to help diagnose and troubleshoot Lync client and server issues Released in Lync 2013 as part of the “Debugging Tools” Can be used to read server or client side logs http://www.microsoft.com/en-us/download/details.aspx?id=35453

8. Start, Stop, Search commands Search results

9. Logging is based on scenarios Built in scenarios specify a group of components and log levels to be started and stopped together ACPMCU AddressBook AlwaysOn ApplicationSharing AudioVideoConferencingIssue CAA CLS CPS DeviceUpdate HostedMigration HybridVoice IMAndPresence IncomingAndOutgoingCall LILRLegacy LILRLYSS LYSSAndUCS MediaConnectivity MeetingJoin MonitoringAndArchiving Powershell RGS SP UserReplicator VoiceMail WAC XMPP

10. Scenario details can be discovered with the Get-CsClsScenario cmdlet NameLevelFlags MediationServerInfoAll S4InfoAll SipstackInfoAll TranslationApplicationInfoAll OutboundRoutingInfoAll InboundRoutingInfoAll UserServicesVerboseTF_Component,TF_CM,TF_Protocol Get-CsClsScenario global/ | Select -ExpandProperty Provider | Format-Table Name,Level,Flags -a

12. $a = New-CsClsProvider -Name "Sipstack" -Type "WPP" -Level "Verbose" -Flags "All" New-CsClsScenario -Identity "Global/CustomVerbose3" - provider $a $b = New-CsClsProvider -Name “OutboundRouting" -Type "WPP" -Level "Verbose" -Flags "All" $c = New-CsClsProvider -Name "InboundRouting" -Type "WPP" -Level "Verbose" -Flags "All" $d = New-CsClsProvider -Name "S4" -Type "WPP" -Level "Verbose" -Flags "All" Set-CsClsScenario -Identity "global/CustomVerbose3" -Provider @{Add=$b,$c,$d}

13. Start AlwaysOn logging for entire deployment start-csclslogging -scenario AlwaysOn Start another scenario for a specific pool start-csclslogging -scenario IncomingAndOutgoingCall -pools pool1.contoso.com Start another scenario for a specific server start-csclslogging -scenario IncomingAndOutgoingCall –computers fe1.contoso.com Stop logging stop-csclslogging -scenario IncomingAndOutgoingCall

14. Get the current Sipstack log for a specific pool search-csclslogging -components Sipstack -pools pool1.contoso.com – outputfilepath c:\logs\sip.log –loglevel Verbose The “sip.log” text file can be opened in any text editor or in Snooper Leave out the “pools” parameter to aggregate all Sipstack logs or use the “computers” parameter to pull the log from one computer Note: If you have created a custom scenario and changed the default log level you must specify which level you would like to search for by using the “loglevel” switch otherwise the higher level results will not be included in your search

15. The logs are stored in %temp%\Tracing for the Network Service account profile

21. www.microsoft.com/learning http://microsoft.com/msdn http://microsoft.com/technet http://channel9.msdn.com/Events/TechEd