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

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 Get-CsClsScenario global/ | Select -ExpandProperty Provider | Format-Table Name,Level,Flags -a NameLevelFlags MediationServerInfoAll S4InfoAll SipstackInfoAll TranslationApplicationInfoAll OutboundRoutingInfoAll InboundRoutingInfoAll UserServicesVerboseTF_Component,TF_CM,TF_Protocol

12. New-CsClsScenario -Identity "global/CustomVerbose” $a = New-CsClsProvider -Name "Sipstack" -Type "WPP" -Level “Verbose" -Flags "All" $b = New-CsClsProvider -Name “OutboundRouting" -Type "WPP" - Level “Verbose" -Flags "All" -Role Edge $c = New-CsClsProvider -Name "InboundRouting" -Type "WPP" -Level "All" -Verbose "All" Set-CsClsScenario -Identity "global/CustomVerbose" -Provider @{Add=$a,$b,$c}

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