microsoft lync 2013 architecture diagram

The following diagram shows the configuration for external Lync clients described in the deployment guide. You use F5 GTM in your environment and would like to take advantage of F5’s Lync Site Resiliency solution. The Enhanced Gateway is typically -located with Microsoft co Mediation server at the enterprise’s headquarters.

You want to use the F5 iApp template to deploy Lync Server rapidly. as many instances, physical or virtual, as your architecture requires. The LyncServer2010EdgeServerReferenceArchDiagrams.zip file contains diagrams for the Single Consolidated Edge, Scaled Consolidated Edge (DNS Load Balanced), and Scaled Consolidated Edge.You want to use intelligent logic (such as pool member status, least connection load balancing, and more) to make the initial client connection to the Front End, Edge, or Mediation pool.You are federated with an organization using legacy clients or servers (see examples in the previous bullet) or public IM services/XMPP.You are using legacy clients or servers (Office Communication Server (OCS), pre-2010 SP1 Exchange Unified Messaging).However, there are advantages to using the BIGIP system to load balance these connections in certain scenarios: Microsoft Lync Server supports DNS Load Balancing for distributing non-HTTP based connections to Lync Front End, Edge, and Mediation Servers. This F5 deployment guide contains instructions on configuring F5 Global Traffic Manager (GTM) and BIG-IP Local Traffic Manager (LTM) modules to support site resiliency for Microsoft Lync Server 20.

Microsoft lync 2013 architecture diagram