How to Deploy with Microsoft Lync Server 2010

This article refers to firmware version 3.6.1.009 and higher running on a configured Barracuda Load Balancer 340 or higher.

This article applies to:

Microsoft^® Lync^® Server 2010
For Lync Mobility, Apple iPhone and iPad; Android phone; Windows Phone 7; and Nokia mobile devices

Microsoft Lync References:

For a list of requirements, refer to Microsoft Lync Server 2010 Deployment
For deployment options, refer to Understanding Microsoft Lync Server 2010 Deployment Options
For mobility deployment details, refer to the Microsoft TechNet article Deploying Mobility

Use the IP Worksheet to record your configuration. Barracuda Networks recommends completing this worksheet as you perform these tasks to assist you when running the Topology Builder in Task 7.

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

Deployment Task	Where

Deployment Task	Where
Task 1. Modify TCP and UDP Connections Settings.	Do this on all active Barracuda Load Balancers, both internal and external.
Task 2. Configure Enterprise Pool Services.	Do this on the internal-facing Barracuda Load Balancer.
If you did not collocate A/V Services on your Front End Servers, you must also complete step 3:
Task 3. Configure Internal A/V Services (if applicable).	Do this on the A/V Pool Barracuda Load Balancer.
If you have an edge deployment, you must also complete the following tasks:
Task 4. Configure Internal Edge Services.	Do this on the internal-facing Barracuda Load Balancer.
Task 5. Configure External Edge Services.	Do this on the external-facing Barracuda Load Balancer.
If you have deployed Director servers, you must also complete the following task:
Task 6. Configure Director Services.	Do this on the Director Barracuda Load Balancer.
Complete the following tasks after all Services are configured on the Barracuda Load Balancer:
Task 7. Run Topology Builder.	Do this on the server where Topology Builder is installed.
Task 8. Enable Cookie Persistence.	Do this on the internal-facing Barracuda Load Balancer.
Configure Mobility Services and configure the Barracuda Load Balancer as a reverse proxy:
Task 9. Configure Lync Mobility Services.	Do this on the internal-facing Barracuda Load Balancer.
Task 10. Configure the Barracuda Load Balancer as a Reverse Proxy for Lync Mobility Services.	Do this on the external-facing Barracuda Load Balancer.

If your Barracuda Load Balancers are clustered, the configuration between the active and passive systems is synchronized; there is no need to modify any passive Barracuda Load Balancers.

Task 1. Modify TCP and UDP Connections Settings

Do the following on all active Barracuda Load Balancers, both internal (the Barracuda Load Balancer configured with the front-end servers) and external (if there is a Barracuda Load Balancer deployed with Edge servers).

The Barracuda Load Balancer comes configured with default settings that work with most applications. Lync 2010 requires changes to the default TCP and UDP connection settings on the Barracuda Load Balancer to ensure compliance with Microsoft specifications.

To modify the TCP and UDP Connections settings on the System Settings page:

Go to the ADVANCED > System Settings tab in the web interface.
In the TCP Connections Timeout box, enter 1800 (30 minutes).
In the UDP Connections Timeout box, enter 1800 (30 minutes).

Task 2. Configure Enterprise Pool Services

To configure all Services needed for an internal Lync deployment, perform the following steps on the internal-facing Barracuda Load Balancer:

Go to the BASIC > Services page. Make sure the Add New Service section is in the advanced view.
Add each Service listed in the table using the steps that follow; all Services are required:
For the HTTPS Front Service only:
- In the Persistence section, set Persistence Type to HTTP Cookie and Persistence Time to 1200. Leave Cookie Name blank.
- In the Advanced Options section, set Session Timeout to 0 (session never times out).
For the DCOM WMI Front Service only, edit each Real Server associated with the Service by clicking the Edit icon next to each Real Server entry in the table. On the Real Server Detail page that appears:

- In the Server Monitor section, set the Testing Method to TCP Port Check.
- In the Port field, enter the value 5061. It is better to test port 5061 for this Service because port 135 always passes the TCP port check even if Lync Services are not responding.

The following Services are optional; add each Service only if you have deployed that feature:

Service Name	Service Type	Virtual IP Address	Real Servers

Service Name	Service Type	Virtual IP Address	Real Servers
Application Sharing (optional)	TCP Proxy	IP for FQDN of Internal enterprise Lync Pool; Port is 5065	IP address of every Front-End Server in your Lync Pool (K and L from the example⁽¹⁾)
QoE Agent (optional)	TCP Proxy	IP for FQDN of Internal Enterprise Lync Pool; Port is 5069	IP address of every Front-End Server in your Lync Pool (K and L from the example⁽¹⁾)
Response Group Service (optional)	TCP Proxy	IP for FQDN of Internal Enterprise Lync Pool; Port is 5071	IP address of every Front-End Server in your Lync Pool (K and L from the example⁽¹⁾)
Conferencing Attendant (optional)	TCP Proxy	IP for FQDN of Internal Enterprise Lync Pool; Port is 5072	IP address of every Front-End Server in your Lync Pool (K and L from the example⁽¹⁾)
Conferencing Announcement	TCP Proxy	IP for FQDN of Internal Enterprise Lync Pool; Port is 5073	IP address of every Front-End Server in your Lync Pool (K and L from the example⁽¹⁾)
Outside Voice Control (optional)	TCP Proxy	IP for FQDN of Internal Enterprise Lync Pool; Port is 5074	IP address of every Front-End Server in your Lync Pool (K and L from the example⁽¹⁾)
Note: ⁽¹⁾See Understanding Microsoft Lync Server 2010 Deployment Options for deployment examples.