This document discusses centralized logging in Lync Server 2013. It provides the following key points: 1. Lync Server 2013 introduces a centralized logging system (CLS) that allows administrators to start, stop, and search trace logs from all machines in a deployment from a single centralized location. 2. CLS consists of a CLSController PowerShell module that sends commands to CLSAgents running on each Lync Server, and the CLSAgents control the local logging and manage log files. 3. The document provides examples of using CLS commands to configure logging scenarios and providers, and search logs across the deployment.

1. Lync Server 2013 – Centralised Logging
Tom Arbuthnot
Senor Consultant, Modality
@tomarbuthnot
http://www.lyncdup.com
tom@tomarbuthnot.com
Credit For Content
Bryan Nyce
UC Voice Architect
Microsoft

2. Good old OCSLogger
• Microsoft Lync Server 2013 Debugging Tools
– Snooper
– OCSLogger
– OCSTracer
– ClsController.psm1
http://www.microsoft.com/en-us/download/details.aspx?id=35453
27/04/2013 Microsoft Unified Communications User Group London (MUCUGL) 2

3. Start, stop, and flush trace logging for any/all machines in a deployment from one place
Start/stop logging based on scenarios
See what logging is turned on per pool/machine for the entire deployment
Search trace logs based on specified parameters from a centralized place

4. Sends Start, Stop, Flush, and Search commands to all the
CLSAgents in the deployment
Aggregates search results from CLSAgents
Available on every Lync Server in “C:Program
FilesCommon FilesMicrosoft Lync Server
2013ClsAgent”
(PowerShell Module for Management)
Runs on every Lync Server
Controls logging based on commands from CLSController
Manages log files to ensure drive space is not consumed,
moves old logs to fileshare

6. AddressBook
AlwaysOn
ApplicationSharing
AudioVideoConferencingIssue
CAA
CLS
CPS
DeviceUpdate
HostedMigration
“HybridVoice”
IMAndPresence
IncomingAndOutgoingCall
LILRLegacy
LILRLYSS
LYSSAndUCS
MediaConnectivity
MeetingJoin
MonitoringAndArchiving
RGS
SP
UserReplicator
VoiceMail
WAC
XMPP

7. $scenario=Get-CsClsScenario
global/IncomingAndOutgoingCall
foreach ($sc in $scenario.provider) { $sc.name }
Get-CsClsScenario global/<ScenarioName> |
Select -ExpandProperty Provider |
Format-Table Name,Level,Flags -a
Component Name Level
MediationServer Info
S4 Info
Sipstack Info
TranslationApplication Info
OutboundRouting Info
InboundRouting Info
UserServices Verbose

8. Managing CLS (PowerShell)

9. Managing CLS If you Love GUIs
Randy Wintel/James Cussen have
written a GUI to run the PowerShell
commands
http://www.mylynclab.com/2013/04/ly
nc-2013-centralised-logging-tool.html

11. Examples

12. Output

13. Gotcha’s
$provider = New-CsClsProvider -Name “SIPVerbose" –Flags “SIPStack”-Type
"WPP" -Level “All"
New-CsClsScenario -Identity "global/SIPVerbose"-Provider $provider