Using the Lync Server Topology Builder expand the Enterprise Edition Front End Pool and view the properties on the pool object.This Override FQDN is then either pointed to just one of the Front End servers (when no load balancing solution is present) or the virtual IP of a separate load balancer configured to forward web service requests to any server in the Front End pool. The topology configuration will require the definition of a new FQDN which will be passed to Lync client during on-band provisioning for all web services URLs that is different that the standard pool name. When using DNS Load Balancing for Lync Front End pools it is not required to actually have a separate load balancer to handle the web traffic, although that would not provide any level of resiliency for the web services. This new environment consists of a single Active Directory domain and split-brain DNS configuration ( jds.net) with two Enterprise Edition Lync 2010 Servers. EnvironmentĪ completely new Lync server environment was deployed and utilized for this article as all previous articles on this site have utilized a Standard Edition deployment ( ).
Microsoft lync for mac shutdown full#
It is only intended to be used for full load balancing scenarios where the LB handles all Lync traffic and not just web server requests.
KEMP Technologies publishes and maintains a detailed deployment guide covering various Lync topologies (Front End, Director, Edge) but as highlighted at the end of Section 3 that guide does not cover the DNS Load Balancing scenarios where the HLB is only used for web traffic. Although operation is identical between each, the Hyper-V version (also available as a VMware instance) was used for this deployment. What is unique about this setup though is that the HLB is not actually a hardware solution, as the KEMP VLM is a virtualized service. This article addresses a standard DNS Load Balanced scenario utilizing a Hardware Load Balancer (HLB) for web server requests only.
0 kommentar(er)
