Lync Windows Store app requirements for Lync Server 2013
Topic Last Modified: 2013-12-03
Organizations with an on-premises deployment of Lync Server must meet the following requirements to support Lync Windows Store app.
For Lync Server 2010, run the cumulative update for Lync Server 2010: February 2012 (available at https://go.microsoft.com/fwlink/?linkid=3052&kbid=2670352) or later on all servers. To enable users to join meetings, run the cumulative update for Lync Server 2010: October 2012 (available at https://go.microsoft.com/fwlink/?linkid=3052&kbid=2737915) on the servers.
Enable the Autodiscover, Lync Web App, and Web Ticket services on the server.
Enable certificate authentication on the Front End Server or Front End pool. (The user registration process on the Front End Server or Front End pool is often referred to as the registrar.) For details, see Create Registrar configuration settings in Lync Server 2013.
Publish the DNS alias (CNAME) resource records for the Autodiscover service.
It is no longer a requirement to make sure the Certificate Revocation List (CRL) Distribution Point (CDP) for the certificates issued to Lync server points to an HTTP resource instead of an LDAP resource. However, make sure that client computers have the latest Windows updates installed.
Configure HTTP proxies in the enterprise to allow Lync server related HTTP traffic. Add exceptions for the Autodiscover, Lync Web App, and WebTicket services, if necessary.
On clients, install Windows 8.1 and the latest version of Lync Windows Store app to fix a sign-in issue that generally occurs when using multiple domains (for example, when the SIP URI is userA@domainZ.com but the Edge Server is sip.domainX.com).
If your organization subscribes to Lync Online or Microsoft 365 and you are using your own domain name, you must take some extra steps to set up your network for autodiscovery of the Lync servers. The network configuration requirements are the same for Lync Windows Store app and Lync on mobile devices.