Microsoft_Lync_Director_Servers

Introduction

Directors can authenticate Lync Server user requests, but not home user accounts, or provide presence or conferencing services. Directors are most useful in deployments that enable external user access, where the Director can authenticate requests before sending them on to internal servers. Directors can also improve performance in organizations with multiple Front End pools. Monitors SIP 503 and 504 response rates.

Discovery with the agent

Collector Type: Agent

Category: Application Monitors

Application Name: Microsoft Lync Director Servers

Global Template Name : Microsoft Lync Edge Servers DotNet v4

Pre-requisites

For Lync monitors need Microsoft .NET Framework 3.5

Need Lync specific WMI classes. Please follow below steps to validate the presence of classes in the target devices.

Run -> WBEMTest -> Run the below mentioned WMI Queries
If the query is not exists in WBEMTEST check it in Perfmon (Run -> Type Perfmon) in the perfmon if the object is exists we have the command to load the objects from perfmon to WBEMTEST follow the below step.
Go to this path C:\Windows\System32\wbem -> lodctr.exe /r . After doing this command the classes are loaded from perfmon to WBEMTEST forcefully.
To refresh the wbemtest after loading the classes from perfmon to WBEMTEST use this: C:\Windows\System32\wbem -> WMIADAP.EXE /r

Collected Metrics

Metric Name	Display Name	Description
SIP_503ResponseRate	SIP_503ResponseRate	This component monitor returns the rate of 503 responses generated by the server, per second. The 503 code corresponds to the server being unavailable. On a healthy server, you should not receive this code at a steady rate. However, during ramp up, after a server has been brought back online, there may be some 503 responses. Once all users get back in and the server returns to a stable state, there should no longer be any 503 responses returned.
SIP_504ResponseRate	SIP_504ResponseRate	This component monitor returns the rate of 504 responses generated by the server, per second. A few 504 responses to clients (for clients disconnecting abruptly) is to be expected, but this counter mainly indicates connectivity issues with other servers. It can indicate connection failures or delays connecting to remote servers. Check the number of SIP (Session Initiation Protocol) sends outstanding to validate this issue.