Lync Server 2010

The Lync Server deployment process is not for the faint of heart. It ranks up there with some of the more complex Microsoft deployments and could be compared, in its level of complexity, to an Exchange 2010 Deployment.

WTI Networks can help you navigate though the decision points you will face during a Lync deployment. It is important to give you everything you need and allow for future growth, without going overboard. All components and servers should be well thought out and justified. Our experience with this product gives us an experienced point of view when it comes to important decision points.

Even the most straight forward version of a Lync 2010 deployment (Single Consolidated Server) is anything but intuitive.

The reference topology below refers to an implementation with high availability and a single data center. It is designed for a small-to-medium size organization with one central site. The exact topology in the following diagram is for an organization of 15,000 users. Typically, the type of topology shown in the following diagram is recommended for organizations with 5,000 to 30,000 users, but it can support over 30,000 users.


Reference topology with high availability and a single data center

MORG reference

  • Active Directory Deployment All Microsoft Lync Server 2010 deployments reside in a single Active Directory forest. For this topology, the customer has Lync Server 2010 deployed in the child domain, retail.contoso.com.

  • To Accommodate More Users, Add More Front End Servers The exact topology in this diagram has two Front End Servers, so it supports up to 16,000 users. If you have a single central site and more users, you can simply add Front End Servers to the pool. One Front End pool can have as many as 10 servers, so a single Front End pool at a single site can support up to 80,000 users.

    However, the single site topology can support even more users by adding another Front End pool to the site. To support these extra users, you need to add only one additional Front End pool (that is, just one pool each of A/V Conferencing Servers, Edge Servers, and Directors are sufficient, although more servers may need to be added to these pools).

  • A/V Conferencing Can Be Collocated in Smaller Organizations If this organization has 10,000 or fewer users, you could decide to collocate A/V Conferencing Services with the Front End pool, instead of deploying a separate A/V Conferencing pool. For organizations with 10,000 or more users, collocating these services is not recommended for performance reasons.

  • Monitoring Server Database Options In this topology, the Monitoring Server is using the same pair of database servers that the Front End pool uses. A topology in which the Monitoring Server has its own database servers is also supported. In each case, we recommend a cluster of more than one database server, for high availability.

  • High Availability for All Server Pools In this example organization with 15,000 users, just one Director server, Edge Server and A/V Conferencing server would be sufficient for performance. However, there are pools of two servers of each type deployed to provide high availability for each feature.

  • Branch Site Deployment Options The organization in this topology has Enterprise Voice deployed as their voice solution. Branch Site 1 does not have a resilient wide area network (WAN) link to the central site, so it has a Survivable Branch Appliance deployed to provide telephone service in case the WAN link to the central site goes down. Branch Site 2 however has a resilient WAN link, so only a public switched telephone network (PSTN) gateway is needed. The PSTN gateway deployed there supports media bypass, so no Mediation Server is needed at Branch Site B.

  • DNS Load Balancing The Front End pool, Edge Server pool, and the Director pool have DNS load balancing for SIP traffic deployed. This eliminates the need for hardware load balancers for the internal interface of the Edge Servers, and significantly lessens the setup and maintenance of the hardware load balancers for the other pools, as the hardware load balancers are needed only for HTTP traffic.

  • Exchange UM Deployment This reference topology includes an Exchange Unified Messaging (UM) Server, which runs Microsoft Exchange Server, not Lync Server 2010. The Exchange UM routing functionality for Lync Server 2010 runs on the Front End pool.

  • Edge Servers Recommended Although deploying an Edge Server is not required, it is recommended for any size of deployment. It is also recommended when external or federated access is required.. You can maximize your Lync Server 2010 investment by deploying an Edge Server to provide service to users currently outside your organization’s firewalls. The benefits include the following:

    • Your organization’s own users can use Lync Server 2010 functionality, if they are working from home or are out on the road.

    • Your users can invite outside users to participate in meetings.

    • If you have a partner, vendor or customer organization that also uses Lync Server 2010, you can form a federated relationship with that organization. Your Lync Server 2010 deployment would then recognize users from that federated organization, leading to better collaboration.

    • Your users can exchange instant messages with users of public instant messaging (IM) services (including Windows Live, AOL, and Yahoo!) and XMPP-based providers and servers (for example, Google Talk and Jabber). A separate license might be required for public IM connectivity with Windows Live, AOL, and Yahoo!