Microsoft Lync Web App is the new Microsoft browser-based client solution for the Microsoft Lync Server 2010 communications software. Lync Web App can provide remote user access to internally hosted Lync Server 2010 conferences by using a reverse proxy configuration that many web proxy server solutions offer. Microsoft Forefront Threat Management Gateway 2010 supports a reverse proxy configuration that can host the remote Lync Web App conferencing client.
This article is the second part of a two-part series that provides users with helpful explanations of the type of network connectivity that is required to adequately use all the conferencing features of the remote Lync Web App client.
Part 1 provides a step by step solution for configuring Forefront Threat Management Gateway TMG as a reverse proxy that provisions remote access for Lync Web App conferencing users.
This article is being reviewed and updated. We will repost the article when revisions are complete.
Author: Mike Adkins
Publication date: February 2011
Product versions: Microsoft Lync Web App, Microsoft Forefront Treat Management Gateway 2010, Microsoft Lync Server 2010, Microsoft Lync 2010
While finding extremely interesting the document posted I'm having an issue in identifying the requirements for one of my user cases tied to a major stakeholder.
While all the conference is initialized inside the trusted zone, using a Lync 2010 client, I've an external user that has the need to participate in the conference (viewing the shared desktop session, whiteboard and poll).
Being from a governmental agency they have extremely strict security policies and I would need to pinpoint what ports would be required.
Is figure 2 the one to keep in mind even if it all is started by a Lync 2010 client?
The external webapp user would need to open which ports?
Thank you for your time and patience,