It’s becoming more and more common to see Lync deployments with a single SIP domain in organizations that have multiple geographically dispersed pools. However, deploying Lync within this scenario can cause quite the confusion due to the different URLs Lync uses in each pool. Typically, you can only have one set of URLs for an entire SIP domain, regardless of the number of pools. The biggest problem: How do you keep conference URLs active for everyone else when one pool fails? In this article, I will focus only on deploying dedicated Simple URLs for a multi-pool company: Contoso, LLC.
Let’s make a few assumptions about the example organization up front:
Contoso has spun off from Microsoft to become its own LLC (they were tired of all the jokes about being a fake company)
Contoso never jumped ship to use Google Apps and are quite happy with the Microsoft Office Suite, SharePoint 2010 and Lync Server 2010
Contoso has 2 Pools; NAPool & EUPool
Sip domain is contosollc.com
Conferencing is heavily used to hold meetings with their business partner, Adatum – located in Europe and the United States
Pool Resiliency is required; if the NA Pool fails, users will re-register to the EU Pool and vice-versa
The basic Topology for Contoso LLC is represented in the following illustration:
Setting up the URLs
During the deployment stages, the New Topology Wizard walks you through the steps to complete your topology for publishing. The Simple URLs are created by default to use Dialin and Meet along with the SIP Domain for the URL. These are completely editable, as I show below. I changed my Simple URLs to represent the conferences hosted in the NA Pool, I then created the required DNS entries (dialin-na.contosollc.com, etc) to point users to the NA Pool servers.
So the conferencing capabilities are setup at this point so users in both the NA and EU pools can send out invites. Conferences are hosted on the NA Pool Servers, but as mentioned above: 1) conferencing is very important and 2) Pool Resiliency is a must. Failure Scenarios
So what happens if the North America Pool goes down in this scenario? Well, the NA users failover to EU with limited capabilities, as expected. But the users currently homed on the EU Pool should still have all the functionality of Lync available to them, correct? You would think so, however… In this scenario, EU users are impacted quite heavily. All Lync functionality stays the same for them with the exception of conferencing. If they attempt to create a conference, the conference will failbecause the NA pool was hosting the URLs and URLs don’t failover. Now, all of Contoso LLC is in a world of hurt, not just Contoso NA. Because no one can have conferences with Adatum and that has a profound effect on their widget-making business.
Unfortunately, in the Edit Properties screen cap above, you cannot just add in the URLs for the EU pool. The Simple URLs added to that properties box can only support a single active URL. If you add EU URLs, all conferences are hosted on EU, so now the point of failure is just shifted to EU. Not all is lost however, because we can add the additional set of URLs using the Lync Management Shell! Shout out toHaiku! Adding the Additional URLs to Each Pool This step is mandatory for the URLs and must be read carefully. The commands must reflect the new URLs you want to use for the additional Pool(s) and also the Site name created for the pool(s). We will keep the NA URLs above, so the NA Pool is taken care of with https://dialin-NA.contosollc.com and https://meet-na.contosollc.com. This step is to create https://dial-eu.contosollc.com and https://meet-eu.contosollc.com.
Open the Lync Server Management Shell
At the Lync Management Shell, enter the following command: