How to Deploy with Microsoft Lync Server 2010 and 2013

How to Deploy with Microsoft Lync Server 2010 and 2013

Product Versions and Prerequisites

This article applies to the Barracuda Load Balancer ADC 5.1 and above, with

  • Microsoft® Lync® Server 2010 or 2013 Enterprise Edition

  • For Lync Mobility, Apple iPhone and iPad; Android phone; Windows Phone 7; and Nokia mobile devices

For a full list of the prerequisites for this deployment, see Microsoft Lync 2010 and 2013 Server Deployment.

Before You Begin

Print or copy the IP Worksheet and use it to record your configuration. Complete this worksheet as you perform the tasks to deploy the Microsoft Lync Server. The worksheet will help you when you run the Topology Builder.

If you want additional information on deployment requirements and options, the following Microsoft Lync References are available:

Before Running Lync Topology Builder

Before Running Lync Topology Builder

Do not run the Lync Topology Builder until instructed to do so by this deployment guide. All of the services on the Barracuda Load Balancer ADC must be configured before running the Topology Builder.

Deployment Tasks

Configuring Clustered Barracuda Load Balancer ADCs

Configuring Clustered Barracuda Load Balancer ADCs

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.

To deploy the Barracuda Load Balancer ADC in a Lync 2010 or 2013 environment, complete the following tasks:

Deployment Task

Where

Deployment Task

Where

Task 1. Configure Enterprise Pool Services

Do this on the internal-facing Barracuda Load Balancer ADC.

If you did not collocate A/V Services on your Front End Servers, you must also do the following:

Task 2. (If applicable) Configure Internal A/V Services

Do this on the A/V Pool Barracuda Load Balancer ADC.

If you have an edge deployment, you must also complete the following tasks:

Task 3. Configure Internal Edge Services

Do this on the internal-facing Barracuda Load Balancer ADC.

Task 4. Configure External Edge Services

Do this on the external-facing Barracuda Load Balancer ADC.

If you have deployed Director servers, you must also complete the following task:

Task 5. Configure Director Services

Do this on the Director Barracuda Load Balancer ADC.

Complete the following tasks after all Services are configured on the Barracuda Load Balancer ADC:

Task 6. Run Topology Builder

Do this on the server where Topology Builder is installed.

Task 7. Configure SSL Settings

Do this on the internal-facing Barracuda Load Balancer ADC.

Configure Mobility Services and configure the Barracuda Load Balancer ADC as a reverse proxy:

Task 8. Configure Lync Mobility Services

Do this on the internal-facing Barracuda Load Balancer ADC.

Task 9. Configure the Barracuda Load Balancer ADC as a Reverse
Proxy for Lync Mobility Services

Do this on the external-facing Barracuda Load Balancer ADC.

If you encounter connectivity issues with your deployment, you can use the Remote Connectivity Analyzer:

Troubleshooting

Task 1. Configure Enterprise Pool Services

Configure all services needed for an internal Lync deployment. Perform the following steps on the internal-facing Barracuda Load Balancer ADC.

  1. Go to the BASIC > Services page in the web interface.

  2. Add all of the services listed in Table 1, along with their real servers. For each service, click Add Service and enter the values in the corresponding fields. To add a real server, click Add Server and enter the IP address and port for the server.
    Table 1. Enterprise Pool Services

  3. For the DCOM_WMI_Front service  only, enable TCP port monitoring for each real server associated with the service. 

    1. Next to each real server entry in the Configured Servers table, click Edit.

    2. In the Edit Server window, scroll to the Server Monitor section and specify these settings:

      • Testing Method – Select TCP Port Check.

      • Port – Enter 5061. Testing port 5061 for this service is recommended because port 135 always passes the TCP port check, even if Lync Services are not responding.

  4. For the HTTPS_Front service  only, configure cookie persistence.

    1. In the service settings, scroll to the Load Balancing section.

    2. Configure these settings:

    •  

      • Persistence Type – Select Cookie Insert or Cookie Passive.

      • Persistence Time – Enter 1200. 

  5. If you have deployed any of the features in Table 2, add the service for the feature.
    Table 2. Services for Optional Features

Task 2. (If Applicable) Configure Internal A/V Services