Microsoft release a new version of Key Health Indicators for Lync Server 2013 and Skype for Business Server 2015

Microsoft releases today an updated version of the Key Health Indicators for Lync Server 2013 and Skype for Business Server 2015.

Key Health Indicators (KHI) are Performance Counters with recommended thresholds aimed at revealing problems that can impact the user experience.
The resources in this download contain the KHI Guide, which outlines the operational process and remediation steps. A sample PowerShell script used to configure KHI Data Collectors. Lastly, the Analysis and Definitions Workbook which can analyze KHI performance data.

Download: Key Health Indicators for Lync Server 2013 and Skype for Business Server 2015

This new version, contains a long waited list of new features, especially around analyzing the gathered data at once and be able to produce a valuable report with indicate on potential problems, so instead of analyzing a file at a time, or using 3rd party script, now a folder with all the CSV file can be analyzed at once:


Another major change in the new version of the KHI is regarding how the KHI is being analyzed reported:

A ring structure outlining the priority of the KHIs. While all the KHIs are important, we’ve grouped them into logical groupings of which ones stand to have the biggest impact.

  • Ring 0 is comprised of all System KHIs (e.g. CPU, Disk, Memory and Network). When KHIs in this ring are beyond threshold, there is high likelihood that KHIs in Ring 1 and Ring 2 are beyond threshold. Therefore, when developing a remediation plan, focus on Ring 0 before taking other actions to resolve KHIs in other rings.
  • Ring 1 mostly contains request queue latencies, SIP problem indicators and network response queues. There are typically other KHIs in Ring 0 contributing to these issues.
  • Ring 2 is all remaining KHIs.

The results can be viewed on different level, and also allow you to filter through the counters which are below optimal range or at optimal range:







And the most important part, is the troubleshooting part in which Microsoft provide a great amount of details on every counter being gathered with detailed explanations on how to troubleshooting and recommendations, as well as the impact of that counters and its result on the environment: