Check out the most comprehensive, actively managed Lync blog roll in the known universe, your one-stop source for links to over 100 of the very best Lync blogs. Here you will also find weekly blog highlights and a feed for a dozen of the top blogs.
Lync Server Support Home
Top Lync Solutions RSS Feed
Microsoft Senior Support engineers walk you through real-life support cases, giving you an insider’s view into the systematic approach they use to troubleshoot Lync Server issues.
These short videos focus on specific tasks and show you how to accomplish them for Microsoft Lync Server 2010.
Autodiscover, also known by the Domain Name System (DNS) record Lyncdiscover.<domain name> and Lyncdiscoverinternal.<domain name>, provides a way for client applications to locate resources, such as the user’s home pool and request web tickets. Autodiscover is not new to Lync Server. Lync Server 2010 Cumulative Update: November 2011 introduced the Microsoft Lync Server 2010 Autodiscover Service and Lync Mobility Service. In Lync Server 2013, the Autodiscover Service also locates these resources for the Lync Windows Store app.
This article provides guidance on how to install the Autodiscover Service and configure the settings to implement the service on Lync Server 2010 and Lync Server 2013.
Author: Rick Kingslan, Microsoft Senior Technical Writer
Publication date: November 8, 2012
Product version: Lync Server 2010, Lync Server 2013 and Lync Windows Store app for Windows 8 and Windows RT
If you planned, deployed, and configured the Cumulative Update for Lync Server 2010: November 2011, you likely understand the basics of the Microsoft Lync Server 2010 Autodiscover Service. The Lync Server Autodiscover Service provides a way for client applications, such as Microsoft Lync Web App or Lync Mobility Services to locate key resources, such as a user's home pool or the URL for joining a dial-in conference. The Lync Windows Store app uses the Autodiscover Service in the same way.
Lync Server 2013 has the required services and settings available to deploy support for the Lync Windows Store app. Lync Server 2010, however, requires the installation of additional cumulative updates.
The overview guidance provided in this article may seem simplistic. The key message is that if you plan and deploy a Lync Server 2010 or Lync Server 2013 internal and external infrastructure, the Autodiscover Service is a natural and intended feature that is available by default. The simple steps to accomplish the goal are--Plan, Deploy, Test. The support for advanced clients, such as the Lync Windows Store app is empowered through the Autodiscover Service.
Important: This article is not a step-by-step guide on how to plan, deploy, and configure Lync Server. Refer to the Planning and Deployment documentation in the Microsoft TechNet Library, as follows:
Lync Server 2010 requires the latest cumulative update. As of this writing, the most recent update is Cumulative Update for Lync Server 2010: October 2012. Install this update for the most current service capabilities for Lync Server 2010.
Note: Cumulative updates are exactly what the name implies. If the cumulative update that you are applying to Lync Server 2010 is the seventh cumulative update that has been made available, it will contain all fixes and updates that were issued in the previous six updates. You need apply only the most recent cumulative update to be completely up-to-date with all previous cumulative updates. For clarification, as of this writing, there have been no cumulative updates issued for Lync Server 2013.
The following list defines the basic expectations for supporting the Autodiscover Service for internal and external clients, including the Lync Winsows Store app:
If all of these requirements are in place, the Autodiscover Service will be working and functional. You should follow the Lync Windows Store app client documentation to install and configure the client.
If you have not completed the installation for Lync Server to support the Autodiscover Service, you must complete the following steps, either partially, if you have a current deployment, or completely, if you are just starting your lab or production deployment:
1. For Lync Server 2010, review Planning Primer: Planning for Your Organization. For Lync Server 2013, review Planning Primer: Planning for Your Organization.
2. Deploy the Lync Server internal infrastructure. Define and configure your internal and external network infrastructure to support Lync Server.
a) For Lync Server 2010, review Determining Your Infrastructure Requirements. For Lync Server 2013, review Network Planning for Lync Server.
b) Plan your requirements for the Lync Server Front End Server or Front End Server pool. For Lync Server 2010, review Planning IM and Presence and Planning for Conferencing. For Lync Server 2013, review Planning IM and Presence and Planning for Conferencing.
c) Deploy and configure the Front End servers or pools. Review Deploying Lync Server 2010 or Deploying Lync Server 2013.
3. Deploy Edge Servers or Edge Server pools and reverse proxies.
a) For Lync Server 2010, review Planning for External User Access. For Lync Server 2013, review Planning for External User Access.
b) Deploy Edge Servers to support external users and clients. For Lync Server 2010, review Deploying Edge Servers. For Lync Server 2013, review Deploying External User Access.
c) Deploy and configure reverse proxies to provide access to Web services and Lync Server features. For Lync Server 2010, review “Set Up Reverse Proxy Servers.” For Lync Server 2013, review Setting Up Reverse Proxy Servers.
4. Configure the Microsoft Lync Server 2010 Autodiscover Service.
a) Lync Server uses the same Autodiscover features for mobility as it does for other client features. For Lync Server 2010, review Planning for Mobility. For Lync Server 2013, review Planning for Mobility
b) Deploy and configure the Autodiscover Service. For Lync Server 2010, review Deploying Mobility. For Lync Server 2013, review Deploying Mobility.
Important: If you have a deployment that includes both Lync Server 2010 and Lync Server 2013, you must set the Lyncdiscoverintal.<domain> DNS A record to resolve to the internal Web services of the Lync Server 2010 pool. The Lyncdiscover.<domain> DNS A record must point to the external Web services for the Lync Server 2010 pool.
5. Confirm the proper configuration and operation of your external configurations with the Office Communications Server and Lync Server Remote Connectivity Analyzer.
Note: The Mobility services that enable mobile functionality in Lync Server 2010 and Lync Server 2013 also enable the Lync Windows Store app. This, when you successfully plan and deploy your Lync Server 2010 or Lync Server 2013 for Mobility, the Autodiscover Service will be configured to provide services for internal and external users using the Lync Windows Store app.
Microsoft Lync Server 2010 Autodiscover Service is an integral part of Lync Server 2010 (since the Cumulative Update for Lync Server 2010: November 2011) and Lync Server 2013. Successfully deploying Lync Server Front End servers or pools, deploying Edge Servers, and deploying reverse proxies for external Web services offered by Lync Server enables the Autodiscover services and features of Lync Server for external and internal clients.
To learn more, check out the following articles:
Keywords: autodiscover, lyncdiscover, Lync Windows Store app