Here is a very incomplete list of what each option means on the Lync Server 2013 Logging Tool (OCSLogger.exe). I am still trying to learn how this tool works and am in search of a complete list of what each Logging Options does, so if you have any information on what each option does please drop a comment below so I can add it to the table. --Thanks and hope this helps someone else!
Notes:
Here is a very thorough guide from Microsoft on Specifying Options for Logging for Communications Server 2007
Here is a guide from Microsoft on Using Lync Server 2013 Logging Tool
| Component | Description |
| ABCommon | Enables logging for the Address Book service. |
| ABServer | Enables logging for the Address Book service that provides global address list information from Active Directory to the Office Communicator client. |
| ABServerIISModule | |
| ADConnect | Enables logging for Active Directory connectivity. |
| ADminUI | Enables logging information for the Lync Admin Control Panel, logging interactions and calls. |
| AggregationScript | Enables logging for the component that determines the aggregate user state and capabilities across all endpoints. |
| ApiModule | Enables logging for the component that exposes the Office Communications Server API to MSPL (Microsoft SIP Processing Language) and managed code applications. |
| ApplicationServer | |
| AppShareOoty | |
| ArchivingAgent | Enables logging for the Archiving agent that runs on the Front End Server and writes SIP messages to Message Queuing. |
| ArchJournal | |
| AsMcu | |
| AutoDiscover | |
| AvMcu | Enables logging for the A/V Conferencing Server. |
| AvMP | |
| CAAServer | |
| CASServer | |
| CertProvisioning | |
| ChatCommon | |
| ChatEndpoint | |
| ChatRoomManagement | |
| ChatSDK | |
| ChatWebService | |
| ClientVersionFilter | Enables logging for the Client Version Filter, an application that can be used to allow/block access from clients that conform to certain versions. |
| CLSAgent | |
| CLSCommon | |
| CLSController | |
| CLSControllerLib | |
| CLSFormat | |
| Collaboration | Logs activities of the collaboration object layer pertaining to instant messaging. |
| CpsDiagnostics | |
| CpsHostingFramework | |
| DataMCU | Enables logging for the Web Conferencing Server. |
| DataMCURunTime | |
| Deployment | |
| DeviceUpdate | |
| DeviceUpdateHttpHandler | |
| Dialin | |
| Dlx | Enables logging for the Group (DL) Expansion service. |
| ExumRouting | Enables logging for the component that routes calls to Exchange Unified Messaging for voice mail. |
| HybridConfig | |
| IIMFilter | Enables logging for the Intelligent Instant Messaging (IIM) application that filters incoming IM traffic using criteria specified by administrators. |
| ImMcu | Enables logging for the IM Conferencing Server, which enables group IM by relaying IM traffic among all participants. |
| InboundRouting | Enables logging for the Inbound Routing component that handles incoming calls largely according to preferences that are specified by users on their Enterprise Voice clients. |
| IncomingFederation | |
| Infrastrucutre | |
| InterClusterRouting | |
| InternalCommon | |
| JoinLauncher | |
| LCCertHelper | Enables logging of the component used for certificates-related functionality in SipStack, MMC, WMI, and the Certificates Wizard. |
| LcsServer | Enables logging of the RtcSrv service. On a Front End Server the RtcSrv service is the Office Communications Server Front End service. On an Access Edge Server, the RtcSrv service is the Office Communications Server Access Edge service. |
| LDM | Enables logging of Web Conferencing Server Connection Management which manages TLS/MTLS connections from clients and other servers such as the Web Conferencing Edge Server. |
| LocationInformationService | |
| Lyss | |
| Mach | |
| ManagementCore | |
| MCUFactory | Enables logging for the Focus Factory which determines which conferencing server is available to service the conference scheduling request. |
| MCUInfra | Enables logging for the component that provides communication between the Focus and the conferencing servers. |
| McxService | |
| Media_MMVR | |
| Media_PAL | |
| MediaStack_AUDIO_AGC | |
| MediaStack_AUDIO_DRC | |
| MediaStack_AUDIO_ECHODT | |
| MediaStack_AUDIO_FAXDT | |
| MediaStack_AUDIO_HEALER | |
| MediaStack_AUDIO_NOISEDT | |
| MediaStack_AUDIO_VAD | |
| MediaStack_AUDIO_VSP | |
| MediaStack_AudioCodes | |
| MediaStack_AudioEngine | |
| MediaStack_COMAPI | |
| MediaStack_COMMON | |
| MediaStack_Crossbar | |
| MediaStack_Crypto | |
| MediaStack_DebugUI | |
| MediaStack_DebugUI_AEC | |
| MediaStack_DEVICE | |
| MediaStack_MassConvertedTraces1 | |
| MediaStack_MediaManager | |
| MediaStack_PerFrame | |
| MediaStack_PerPacket | |
| MediaStack_QualityController | |
| MediaStack_RTCP | |
| MediaStack_RTP | |
| MediaStack_StreamingEngine | |
| MediaStack_TLS | |
| MediaStack_Transport | |
| MediaStack_VIDEO | |
| MediaStack_VOICEENHANCE | |
| MediationServer | Enables logging for the Mediation Server that translates between the Office Communications Servers and the media gateway. |
| MRAS | Enables logging for the Office Communications Server Audio/Video Authentication service, which provides authentication services for the A/V Edge Server, the component that provides the functionality to share audio and video with external users. |
| OutboundRouting | Enables logging for the Outbound Routing component that routes calls to PBX or PSTN destinations, applies call authorization rules to callers, and determines the optimal media gateway for routing each call. |
| OutgoingFederation | |
| PDP | |
| PowerShell | Enables logging for most of the PowerShell interfaces from the Lync Amdin Control Panel. |
| QueueDLL | Enables logging for the component that facilitates inter-process communication between the server and applications. |
| RDPApiTrace | |
| RDPEncComTrace | |
| ReachJoin | |
| ReachPerf | |
| RgsClientLib | |
| RgsCommonLibrary | |
| RgsDatastores | |
| RgsDeploymentApi | |
| RgsDeploymentLibrary | |
| RgsDiagnostics | |
| RgsHostingFramework | |
| RgsMatchMakingService | |
| Routing_data_Sync_agent | |
| RtcDbSyncAgent | |
| RtcHost | Enables logging for the component that is the host for all server API applications. |
| RTCSPL | Enables logging for the component that is the host for running MSPL (Microsoft SIP Processing Language) script based applications. |
| S4 | Logs all SIP messages between the Mediation server and PSTN gateways |
| ServerAgent | |
| ServerConfiguration | |
| ServerTransportAdaptor | |
| SIPStack | Enables logging for the SipStack component that handles TLS/MTLS connection management and SIP call flows. |
| StoreWeb | |
| TranslationApplication | Enables logging for the Translation Service which is the server component that is responsible for translating a dialed number into E.164 format based on the normalization rules defined by the administrator. |
| UCMA_Workflow | |
| UCWA | |
| UdcAgent | |
| UserPinService | |
| UserServices | Enables logging for the UserServices component that provides closely integrated IM, presence, and conferencing features built on top of the SIP proxy. Includes the Focus and Focus Factory. |
| WebInfrastructure | |
| WebRelay | |
| WebScheduler | |
| WPP_OC_RDP_APPSHAPI | |
| XDS_File_transfer_agent | Enables logging of replication data, specifically file transfer aspects. |
| XDS_Master_replicator | Enables logging for the creation of replication packges and notifications. |
| XDS_Replica_Replicator | Enables logging for receipts of replication packages and notifications. |
| XmppCommonLibrary | |
| XmppListener | |
| XmppRouting | |
| XmppTGW | |
Hi,
its a BIG shame that MS is unwilling to share the details of what those components do.
"S4" is no longer Communicator Web Access trace, but SIP trace between MEDIATION server and PSTN gateways, so that should be corrected not to spread misleading info!
Thanks for the info Richard, I have updated the table. If you have found out what some of the others are, please let me know so I can update the chart accordingly.
Thank you!
Jack
LET'S MAKE NO MISTAKE - Microsoft IS willing to share THE INFORMATION IF ONLY THE GUY THAT WROTE THE TOOL WAS WILLING TO SHARE WITH anyone else ON THE PLANET. I tried for 3 years as a technical writer for the Lync team to get this information (along with people in PSS) and we were stymied all along the way. Even up to the Principal Program manager I was told, essentially, if he doesn't want to give you the information, I can't force him. Really? Do we work for the same Microsoft here? If I had (when I was there) refused to give information to my peers and colleagues, I'd have been roundly taken out to the quad and shot.
No, it's not an unwillingness of MICROSFT. It's the power trip of ONE DUDE. (Name withheld to prevent stoning and execution in the quad by angry IT Pros.)
Haha, thanks for the follow up Rick! Quite the inside info on this.
Even though there isn't a complete list of all the options, would you by chance have any additional information from previous support sessions that we could add to help define the list?
Thanks!
Jack
Rick:
oh my god, that sounds terrible 🙁
Guess if that single person leaves MS, nobody will know (not even the PSS guys inside MS) how to troubleshoot Lync tickets? There has to be some kind of internal document floating around, otherwise Lync troubleshooting is a non-existent thing apart from the SIPSTACK loggin.