- #MS LYNC 2013 AUTO START WHEN WINDOWS STARTS HOW TO#
- #MS LYNC 2013 AUTO START WHEN WINDOWS STARTS ARCHIVE#
- #MS LYNC 2013 AUTO START WHEN WINDOWS STARTS SOFTWARE#
- #MS LYNC 2013 AUTO START WHEN WINDOWS STARTS WINDOWS#
#MS LYNC 2013 AUTO START WHEN WINDOWS STARTS WINDOWS#
When Microsoft Lync/Skype for Business Server encounters a problem, it reports it as an event in the Windows Event Log dedicated to Microsoft Lync/Skype for Business. These thresholds (like any alert threshold in Monitoring Studio) can be customized through the interface:įigure 3- Setting Thresholds 3/Windows Event Logs Total Lync Server Processes (all processes that have % in their path)įor each of these processes, the following parameters are monitored:īy default, only the ProcessorTime parameter triggers a warning when it reaches 90% five times in a row and 99% twice in a row.The sum of all of these processes is available as a separate object as well so administrators can check the system resource consumption of Lync/Skype for Business Server in general and of each process individually. Each process is monitored independently and displayed as a separate object in the console. Key performance metrics are constantly monitored for all the Lync/Skype for Business Server processes. LyncServerWebConferencingEdge(RTCDATAPROXY)įigure 1 - Monitoring a Windows Service 2/Processes LyncServerAudio/VideoAuthentication(RTCMRAUTH) LyncServerReplicaReplicatorAgent(REPLICA) LyncServerAudio/VideoConferencing(RTCAVMCU) LyncOnlineTelephon圜onferencing(RTCACPMCU) LSConferencingApplicationSharing_RTCASMCU LyncServerBandwidthPolicyService (RTCPDPCORE) LSApplicationPolicyDecisionPoint_RTCPDPCORE LyncServerBandwidthPolicyService(Authentication)(RTCPDPAUTH)
LSApplicationPolicyDecisionPoint_RTCPDPAUTH LSApplicationConferencingAutoAttendant_RTCCAA LyncServerConferencingAnnouncement(RTCCAS) LSApplicationCallAnnouncementService_RTCCAS This parameter will trigger an alarm if the service is stopped and a warning if the service is in an intermediate state (stop pending, paused, etc.). The “Status” parameter reports the status of the service. Each service is represented with a separate object in the console. The status of the services listed in the table below is monitored by the solution. The solution monitors a mixture of Windows services, processes, Windows Event Logs and performance counters that are grouped based upon which component of Lync/Skype for Business Server they relate to.
#MS LYNC 2013 AUTO START WHEN WINDOWS STARTS ARCHIVE#
The architecture of Microsoft Lync Server 2013/Skype for Business can be quite complex as it involves several systems with different roles, where each role runs different components of Lync/Skype for Business Server: Archive Servers, Edge Servers, Quality Monitoring Servers, Microsoft SQL Server, etc.
#MS LYNC 2013 AUTO START WHEN WINDOWS STARTS HOW TO#
This article simply explains how to import this pre-built configuration and customize it to monitor your Microsoft Lync/Skype for Business environment.
Sentry has created a configuration for Monitoring Studio KM to monitor Microsoft Lync Server 2013/Skype for Business. More information about Monitoring Studio KM is available here on Sentry’s Web site. The "setup" of the monitoring is stored in the PATROL Agent's configuration. Typically, a PATROL administrator will use Monitoring Studio KM's GUI to "create" the monitoring of anything which the administrator does not have a built-in KM for. Our solution relies on Monitoring Studio KM for PATROL, which is a configurable module for BMC PATROL (and therefore BMC TrueSight Operations Management).
#MS LYNC 2013 AUTO START WHEN WINDOWS STARTS SOFTWARE#
Sentry Software cannot be held responsible for any use which may be made of the provided file. It may need to be customized to suit your specific needs. This configuration has been designed to monitor Microsoft Lync Server 2013/Skype for Business based on a standard environment. Our goal is to monitor Microsoft Lync Server 2013/Skype for Business in BMC PATROL and/or BMC TrueSight Operations Management to detect failures, errors and performance problems.