Update 3: Announcing the Release of the Lync Server Networking Guide v2

Updates to the Lync Server Networking Guide

January 2014 - The .zip file has been updated on the Download Center to include updated queries and a KHI spreadsheet for Lync Server 2013.

November 2013 - We've updated some of the queries to address the issues you identified and posted a new version of the files to download. Look for the 2013 KHIs to be added soon.

An updated version of the Networking Guide is now available here: Lync Server Networking Guide v2. New sections, authored by Andrew Sniderman, Kent Tilger (Appendix D), Brandon Bernier (KHI spreadsheet and PowerShell script), and Jens Trier Rasmussen, include:

  • Appendix C: Call Quality Methodology – a practical approach
    This section covers the Lync Call Quality Methodology or CQM.  CQM is a holistic way to systematically define and assert call quality based upon the methods outlined in the Networking Guide. CQM divides a Lync implementation into ten discrete areas that impact quality, defining targets and a remediation plan for each one. CQM is a framework to tackle call quality problems – you can modify or extend it to address the particular conditions on your network.
  • Appendix D. Troubleshooting Poor Streams
    This section includes techniques to troubleshoot poor streams that CQM surfaces.

The Networking Guide download also now includes the list of Lync 2010 KHIs to validate server health and the complete set of CQM queries referenced in the guide.

Thanks for all the feedback on CQM - keep it coming!  Thanks to you we've found and fixed a few issues with the queries. Please let us know of anything else you find. We will refine the content and post an updated version to the Download Center in a couple of weeks.  If you would like to get any updates in advance, send us an email at the address listed in the documents.

Comments (8)
  1. fbifido says:


    Can you do a step-by-step video on this VM setup:

    outside dns info:
    *.contoso.com eg: mail.contoso.com, sip.contoso.com, etc…

    inside dns info:


    software use:
    Windows Server 2012 R2
    Windows 8.1 Enterprise
    Exchange 2013 U3 (all features enable, including UM)
    Lync 2013 (enable all features)
    SQL 2012 SP1
    SharePoint 2013
    Office 2013 Pro Plus

    do a server-to-server trust between Exchange 2013, Lync 2013, SharePoint 2013.
    make outlook have access to exchange address book, & can call or text each other using lync from outlook address book.
    create a group of users who can call outside using sip trunk & call skype user

    Is there a way to just have one user management interface, like Active Directory, for all user in Exchange/Lync/AD ?
    so that if you add a user to AD, that using will automatically get an email address, and a lync account (Enterprise Voice + Archiving)

    Do meeting & conferencing between client1, client2 & client3 using outlook 2013.
    Do voice, video & text between client1, client2 & client3 using outlook 2013.
    Allow a group of users to sharing & editing of a document.

    I want to tie all these Microsoft products together so that they work seamlessly, while utilizing all the features of these software.

    plus have a tight security, as in all internet traffic must go through the firewall, and the firewall has a default setting to block all outgoing & incoming, with the exception of the manually added ports:
    out: 80,21,22,443,110,995, etc…, 25 only from mail.contoso.lan.
    in: (pop3s,imaps,smtp,smtps,587) all email related ports to mail.contoso.lan

    user files on files.contoso.lan:
    Users\Signature files.html ( for replies & forwarding)
    Users\Stationary files.html (for new emails only)

    Z: = \files.contoso.landata\
    Y: = \files.contoso.lanshare

  2. Chris Lehr says:

    Feel free to try and integrate, but the massaging of CSV data was a pain, so I developed this:

Comments are closed.

Skip to main content