![]() Support is provided by the third party for their solution. You can also view third parties that have submitted documentation for their product to Microsoft. ![]() For hardware load balancers and firewalls that provide reverse proxy features, check with your vendor for specific instructions on how to configure their product to provide reverse proxy support for Lync Server. ![]() Also, many third party hardware load balancers and firewalls provide reverse proxy support. TMG is still a fully supported product, and is still available for sale on appliances sold by third parties. In November, 2012, Microsoft ceased license sales of ForeFront Threat Management Gateway 2010, or TMG. Internet Information Server Application Request Routing (IIS ARR) is a fully tested and supported option for implementing a reverse proxy for Lync Server 2010 and Lync Server 2013. If you are using a different reverse proxy, consult the documentation for that product and map the requirements defined here to the associated features in other reverse proxies. The detailed steps in this section describe how to configure Forefront Threat Management Gateway 2010, and the steps for configuring ISA Server 2006 are almost identical. You can use Microsoft Forefront Threat Management Gateway 2010, Microsoft Internet Security and Acceleration (ISA) Server 2006 SP1, or Internet Information Server 7.0, 7.5 or 8.0 with Application Request Routing (IIS ARR) as a reverse proxy. You also need to publish the external Autodiscover Service URL. The simple URLs can be handled by a dedicated web publishing rule, or you can add it to the public names of the web publishing rule for the Director. (If this is not the user’s home pool, it will redirect them onward to the Web Services on the user’s home pool). If you have not deployed a Director, you need to designate one pool to handle requests to the simple URLs. If the organization has a Director or Director pool, the HTTP reverse proxy listens for HTTP/HTTPS requests to the simple URLs and proxies them to the external Web Services virtual directory on the Director or Director pool. In addition, you need to publish the simple URLs. You need one publishing rule for each Standard Edition server, Front End pool, or Director or Director pool in your organization. Publishing ExternalFQDN/* publishes all IIS virtual directories for a pool. We recommend that you configure your HTTP reverse proxy to publish all Web Services in all pools. Some of the features that require external access through a reverse proxy include the following:Įnabling external users to download meeting content for your meetings.Įnabling external users to expand distribution groups.Įnabling remote users to download files from the Address Book service.Īccessing the Dial-in Conferencing Settings webpage.Įnabling external devices to connect to Device Update web service and obtain updates.Įnabling mobile applications to automatically discover and use the mobility (Mcx) URLs from the Internet.Įnabling the Lync 2013 client, Lync Windows Store app and Lync 2013 Mobile client to locate the Lync Discover (autodiscover) URLs and use Unified Communications Web API (UCWA). For Microsoft Lync Server 2013 Edge Server deployments, an HTTPS reverse proxy in the perimeter network is required for external clients to access the Lync Server 2013 Web Services (called Web Components in Office Communications Server) on the Director and the user’s home pool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |