Configuring support for Autodiscover in Lync Server 2013
Topic Last Modified: 2013-01-21
The Lync Server web services Autodiscover service first appeared in the Lync Server 2010 Cumulative Update: November 2011. This update was accompanied by the initial release of Lync Mobile clients. The autodiscover service exposed the mobility services, known as the Mcx service.
The autodiscover service acts as a single location for all clients to request information on what services and features are available, and how to contact the sevices – either by a fully qualified domain name or a web uniform resource locator reference. Autodiscover exposes a number of features, and each client will make requests based on the features that the client can use. For example, a desktop Lync 2013 client will use autodiscvoer to determine the external web services, but will not use the mobility (Mcx) services. To properly define and enable your clients to use the features available to them, the scenarios that allow a client to effectively find and use autodiscover entries should be defined. To use autodoscover, your deployment requires that a reverse proxy publishes the Lync Server web services, that DNS records are configured to resolve DNS queries for the Lync Server autodiscover service and Lync Server web services, and that certificate services are properly configured for your specific scenario.
|For technical details on what the elements within the autodiscover request/response do, see Understanding Autodiscover in Lync Server 2013.|
The following information and tables define, per scenario, what configurations (if any) you need to implement to provide the full and effective use of the autodiscover service. The information in the following topics is specific to Microsoft Lync Server 2013. If you are looking for guidance on how to plan Mobility for Lync Server 2010, see http://go.microsoft.com/fwlink/?LinkId=275113. To deploy Mobility for Lync Server 2010, see http://go.microsoft.com/fwlink/?LinkId=275114