(If Applicable) Configure Internal A/V ServicesĬomplete this step if you did not collocate A/V Services on your front-end servers. IP Addresses of your front-end servers (K and L from the deployment example) IP addresses of your front-end servers (K and L from the deployment example) IP address for the FQDN of the Internal Enterprise Lync Pool However, for Lync 2013, you can choose to use cookie persistence instead. In these settings, source IP persistence is recommended. If you have deployed any of the features in Table 2, add the service for the feature. Persistence Type – Select Cookie Insert or Cookie Passive.In the service settings, scroll to the Load Balancing section.For the HTTPS_Front service only, configure cookie persistence.Testing port 5061 for this service is recommended because port 135 always passes the TCP port check, even if Lync Services are not responding. Testing Method – Select TCP Port Check.In the Edit Server window, scroll to the Server Monitor section and specify these settings:.Next to each real server entry in the Configured Servers table, click Edit.For the DCOM_WMI_Front service only, enable TCP port monitoring for each real server associated with the service.Lync 2010 requires changes to the Session Timeout setting for each service configured for Lync on the Barracuda Load Balancer ADC to ensure compliance with Microsoft specifications. The Barracuda Load Balancer ADC is preconfigured with default settings that work with most applications. To add a real server, click Add Server and enter the IP address and port for the server. For each service, click Add Service and enter the values in the corresponding fields. Go to the BASIC > Services page in the web interface.Īdd all of the services listed in Table 1, along with their real servers.Perform the following steps on the internal-facing Barracuda Load Balancer ADC. If you encounter connectivity issues with your deployment, you can use the Remote Connectivity Analyzer:Ĭonfigure all services needed for an internal Lync deployment.
If you have deployed Director servers, you must also complete the following task:ĭo this on the Director Barracuda Load Balancer ADC.Ĭomplete the following tasks after all Services are configured on the Barracuda Load Balancer ADC:ĭo this on the server where Topology Builder is installed.Ĭonfigure Mobility Services and configure the Barracuda Load Balancer ADC as a reverse proxy:
If you have an edge deployment, you must also complete the following tasks:ĭo this on the external-facing Barracuda Load Balancer ADC. (If applicable) Configure Internal A/V Servicesĭo this on the A/V Pool Barracuda Load Balancer ADC. If you did not collocate A/V Services on your Front End Servers, you must also do the following: Configure Enterprise Pool Servicesĭo this on the internal-facing Barracuda Load Balancer ADC. To deploy the Barracuda Load Balancer ADC in a Lync 2010 or 2013 environment, complete the following tasks: Deployment Task If your Barracuda Load Balancer ADCs are clustered, the configuration between the active and passive units is synchronized you only need to configure the active Barracuda Load Balancer ADC.
Complete this worksheet as you perform the tasks to deploy the Microsoft Lync Server. Print or copy the IP Worksheet and use it to record your configuration.
For Lync Mobility, Apple iPhone and iPad Android phone Windows Phone 7 and Nokia mobile devicesįor a full list of the prerequisites for this deployment, see Microsoft Lync 20 Server Deployment.Microsoft ® Lync ® Server 2010 or 2013 Enterprise Edition.This article applies to the Barracuda Load Balancer ADC 5.1 and above, with