įrom the Windows PowerShell command-line interface, run the following command: add-pssnapin Microsoft.Adfs. For more information, see the "Federation server certificates" section of the Plan for and deploy AD FS for use with single sign-on topic at. For details, see the Active Directory Federation Services 2.0 Deployment Guide at Ĭreate certificates for AD FS. This configuration does not apply to Lync mobile clients. Typically, a token life of 240 minutes is sufficient.
LYNC WEB APP 2013 WINDOWS 7
The BranchCache feature in Windows 7 and Windows Server 2008 R2 can interfere with Lync Web. The Lync Server 2013 version of Lync Web App supports. When you establish a relying party trust between Lync Server and AD FS servers, assign a token life that is long enough to span the maximum length of your Lync meetings. Deploying Lync Web App in Lync Server 2013 Enabling Multi-Factor Authentication for Lync Web App. It’s a light program that takes up very little space on your hard drive and is relatively quick to start. If you use hardware load balancers, enable cookie persistence on the load balancers so that all requests from the Lync Web App client are handled by the same Front End Server. Lync Web App is the browser-based version of Lync 2010 that allows people who don’t have a Lync account and haven’t installed the Lync client to participate in Lync meetings, using either a Windows or Macintosh operating system. Multi-factor ADFS authentication does not work for Lync federated users because the Lync server web infrastructure does not currently support it.
Multi-factor ADFS authentication works if the meeting participant and organizer are both in the same organization or are both from an AD FS federated organization. The following are important considerations if you plan to configure AD FS for multi-factor authentication: