Udostępnij za pośrednictwem

Remote Conferencing with Lync Web App with Forefront Threat Management Gateway 2010 Reverse Proxy: Part 1

  • Artykuł

Microsoft Lync Web App is the new Microsoft browser-based client solution for the Microsoft Lync Server 2010 communication software instant messaging and conferencing features. The Lync Web App client can provide remote user access to internally hosted Lync Server 2010 conferences. This is done 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 first part of a two-part series that provides you with a step-by-step solution for configuring Microsoft Forefront Threat Management Gateway 2010 as a reverse proxy that provisions remote access for Lync Web App conferencing users. Part two explains the type of network connectivity that is required to adequately use all the conferencing features of the remote Lync Web App client.

This article is being reviewed and updated. We will repost the article when revisions are complete.

Author: Mike Adkins

Publication date: February 2011

Product version: Microsoft Lync Web App, Microsoft Forefront Treat Management Gateway 2010, Microsoft Lync Server 2010

Comments

  • Anonymous
    March 21, 2011
    The comment has been removed

  • Anonymous
    June 01, 2011
    Dear DrRez, great article. I have publish the LWA thru my TMG. But i have a some issue here, the simple URL for  dialin.domain.com, if i try to signin and get error as follow: "The operation failed with an unexpected error. If the problem persists, contact your system administrator" do you have article about dialin publishing.? Thanks

  • Anonymous
    November 03, 2011
    Hi. Can you confirm, or supply the reference material to confirm that  a TMG Array can or can’t be used to load balance Lync HTTPSTraffic?  instead of a HLB. ? Thanks Mark

  • Anonymous
    November 20, 2011
    Hi Mark Brumby, Did you find the answer to your question?   I have the same question Regards

  • Anonymous
    December 02, 2011
    The comment has been removed

  • Anonymous
    September 12, 2012
    I know that the post is old, anyway, you need to enable the option to “Forward the original host header instead of the actual one specified in the Internal site name field on the previous page” when creating the Reverse Proxy Web Publishing rule. If you don't do that, you have a blank page calling meet, dialin and so on. The correction is from the  Jamie Schwinn blog waveformation.com/.../lync-host-header-forwarding