Rules

Secret ingredients to quality software

Edit
Info

Do you know how to troubleshoot Lync connectivity or configuration issues?

Created on 17 Apr 2012 | Last updated by Tiago Araujo on 19 Apr 2017 06:09 PM (almost 4 years ago)

At times especially during the initial implementation, you may encounter some issues with Lync. The following are some of the useful tools which will assist you in identifying where the problem lies.

Remote UC Troubleshooting Tool (RUCT) for Lync will show that the DNS records used by the Lync mobility clients to auto-discover the Lync mobility service have been added. This tool can be acquired from Inside OCS blog.

Specifically, you now have the option of querying the locally configured DNS server for the following records:

  • Lyncdiscover. (both CNAME or A record)
  • Lyncdiscoverinternal. (both CNAME or A record)
  • From the same screen, you can ping the resulting hostname or test the port availability on any of the Lync DNS record matches

lync auto discovery
Figure: Lync Auto-Discovery Mobility DNS record

Lync Monitoring Reports

The Monitoring Server collects data from the call detail recording (CDR) and Quality of Experience (QoE) databases and presents that data with the help of the SQL Server Reporting Services and the predefined Monitoring reports. These reports will show statistics which will assist in identifying issues such as network issues such as latency and packet loss.

Internet Network connectivity tests

Tools such as VisualRoute 2010 will assist in highlight problems related latency and packet loss.

visualroute tool
Figure: VisualRoute 2010 tool showing a test to a Google DNS server

Read more about implementing Microsoft Lync.

Adam CoganAdam Cogan

We open source. This page is on GitHub