Voice Routing

Voice routes and how they are impacted during a migration to Lync Server 2013 is an important item to cover. When you are in a period of coexistence with a Lync Server 2010 pool that includes Lync Server 2010 mediation servers, you probably have gateways and/or SBCs associated with Lync Server 2010 mediation server or Mediation Server pool. Voice routing interoperability between Lync Server 2010 and Lync Server 2013 is fully supported, meaning that you can have users homed on Lync Server 2010 and use a Lync Server 2010 or a Lync Server 2013 mediation server/pool, or have users homed on Lync Server 2013 and use a Lync Server 2013 or Lync Server 2010 mediation server/pool. The point here is that before decommissioning the Lync Server 2010 environment, you will need to configure Lync Server 2013 Mediation Servers or Pools with the gateways and/or SBCs and also configure the Voice over IP gateways and/or SBCs to direct inbound traffic to the Lync Server 2013 Mediation Servers.

Another important note here is that a Lync Server 2013 SBA (Survivable Branch Appliance) is not supported in a Lync Server 2010 pool.

Before you decommission the Lync Server 2010 environment, there are a few configuration changes that need to be made before you can call the migration task complete. This first is to update internal DNS SRV records for every SIP domain that is supported by your environment. The process that follows describes how to complete this task. Complete this task from a server that has the DNS administrative tools installed:

1. On the DNS server, click Start, Administrative Tools, DNS.

2. In the console tree for your SIP domain, expand Forward Lookup Zones, expand the SIP domain in which Lync Server 2013 is installed, and navigate to the _tcp setting.

3. In the right pane, right-click _sipinternaltls and select Properties.

4. In Host Offering This Service, update the host FQDN to point to the Lync Server 2013 pool (if the pool is a Standard Edition Server, enter the server FQDN). This is shown in Figure 16.13.

Figure 16.13. Update SRV record for all SIP domains supported.

5. Click OK.

Earlier you read about the Central Management Server. If you recall, the Central Management Server is still associated with the Lync Server 2010 pool. You need to move the Central Management Server to the Lync Server 2013 pool. This process is outlined next.

If you deployed Lync Server 2013 Standard Edition, here are the steps for preparing the environment:

1. On the Lync Server 2013 Standard Edition Front End Server where you want to relocate the Central Management Server: Log on to the computer where the Lync Server Management Shell is installed, as a member of the RTCUniversalServerAdmins group.

2. Open the Lync Server Deployment Wizard.

3. In the wizard, click Prepare First Standard Edition Server.

4. On the Executing Commands page, SQL Server Express is installed as the Central Management Server. Necessary firewall rules are created. When the installation of the database and prerequisite software is completed, click Finish.

5. To create the Central Management Store, you need to complete this process from the Lync Server 2013 Management Shell. Type the following:

Click here to view code image

Install-CsDatabase -CentralManagementDatabase -SQLServerFQDN "lync.companyabc.
com" -SQLInstanceName RTC

6. Confirm that the status of the Lync Server Front End service is Started.

If you deployed Lync Server 2013 in a Enterprise Pool configuration, here are the steps for preparing the environment:

1. On the Lync Server 2013 Standard Edition Front End Server where you want to relocate the Central Management Server: Log on to the computer where the Lync Server Management Shell is installed, as a member of the RTCUniversalServerAdmins group.

2. Open the Lync Server 2013 Management Shell.

3. To create the new Central Management store in the Lync Server 2013 SQL Server database, in the Lync Server Management Shell, type this:

Install-CsDatabase -CentralManagementDatabase -SQLServerFQDN "SQL01.companyabc.com"-SQLInstanceName LYNC

4. Confirm that the status of the Lync Server Front End service is Started.

Now that you have prepared the environment and created a blank XDS and LIS database, you can move the Central Management Server to the Lync Server 2013 pool. To do that, you have a few more commands to run:

1. On the Lync Server 2013 server that will be the Central Management Server: Log on to the computer where the Lync Server Management Shell is installed, as a member of the RTCUniversalServerAdmins group. You must also have the SQL Server database administrator user rights and permissions.

2. Open Lync Server Management Shell.

3. In the Lync Server Management Shell, type this:

Enable-CsTopology

4. On the Lync Server 2013 Front End Server or from one of the Front End pool servers in an Enterprise pool, in the Lync Server Management Shell, type this:

Move-CsManagementServer

5. Lync Server Management Shell displays the servers, filestores, database stores, and service connection points of the Current State and the Proposed State. Read the information carefully and confirm that this is the intended source and destination. Type Y to continue, or N to stop the move.

6. Review any warnings or errors generated by the Move-CsManagementServer command and resolve them.

7. On the Lync Server 2013 server, open the Lync Server Deployment Wizard.

8. In the wizard, click Install or Update Lync Server System, click Step 2: Setup or Remove Lync Server Components, click Next, review the summary, and then click Finish.

9. On the Lync Server 2010 server, open the Lync Server Deployment Wizard.

10. In the wizard, click Install or Update Lync Server System, click Step 2: Setup or Remove Lync Server Components, click Next, review the summary, and then click Finish.

11. To confirm that replication with the new Central Management store is occurring. In the Lync Server Management Shell, type this:

Get-CsManagementStoreReplicationStatus

If you had Lync Server 2010 Archiving or Monitoring roles installed and associated with the Lync Server 2010 pool, those associations will need to be removed before the decommissioning of the Lync Server 2010 environment. Details on that process are not given here.

Okay, you are on the home stretch. Migration from Lync Server 2010 to Lync Server 2013 involves quite a few components, as you might have been able to tell. You have a few more items left, and then you can go grab a cup of coffee!

Call Admission Control (CAC) has a component called PDP (Policy Decision Point). This component is responsible for making CAC decisions and adhering to the policies defined. That service is hosted on a single pool in each site. You need to move this configuration to the Lync Server 2013 environment. Following is the process:

1. Open Topology Builder.

2. Right-click the site node, and then click Edit Properties.

3. Under Call Admission Control setting, make sure that Enable Call Admission Control is selected.

4. Under Front End Pool to Run Call Admission Control (CAC), select the Lync Server 2013 pool that is to host CAC, as shown in Figure 16.14. Click OK.

Figure 16.14. Update PDP, Call Admission Control configuration.

5. Publish the topology.

After the topology has been published, it is important to update the Lync Server 2010 and Lync Server 2013 pools so that the CAC Services are removed and added correctly. To do that, complete the following steps on each pool:

1. In Lync Server Deployment Wizard, click Install or Update Lync Server System, click Step 2: Setup or Remove Lync Server Components, click Next, review the summary, and then click Finish.

2. On the Lync Server 2010 server, open the Lync Server Deployment Wizard.

3. In the wizard, click Install or Update Lync Server System, click Step 2: Setup or Remove Lync Server Components, click Next, review the summary, and then click Finish.

Now that all dependent services have been moved to the Lync Server 2013 environment, it is time to remove the Lync Server 2010 configuration.

The first thing you need to do is stop services and prevent new sessions to the Lync Server 2010 pool:

1. From each server in the pool, run the following command:

Stop-CsWindowsService

Lync Server 2010 Enterprise Edition does not exist as a stand-alone computer. At least from a Lync Server Topology perspective, you always need to define a pool, and in the pool you define the Enterprise Edition Servers. The process the follows guides you through removing an individual Front End Server from an existing environment:

1. Open the Lync Server 2013 Front End Server, and open Topology Builder.

2. Navigate to the Lync Server 2010 node.

3. Expand Enterprise Edition Front End Pools, expand the Front End pool with the Front End Server that you want to remove, right-click the Front End Server that you want to remove, and then click Delete.

The final step is removing the actual Lync Server 2010 Standard Edition or Enterprise Edition pools from the topology.

To remove an Enterprise Edition Front End Server pool, follow this procedure:

1. Open Topology Builder.

2. Navigate to the Lync Server 2010 node.

3. Expand Enterprise Edition Front End pools, expand the Front End pool, right-click the Front End pool that you want to remove, and then click Delete.

4. Publish the topology, check the replication status, and then run the Lync Server Deployment Wizard as needed.

To remove a Standard Edition Front End Server, follow this procedure:

1. Open Topology Builder.

2. Navigate to the Lync Server 2010 node.

3. Expand Standard Edition Front End Servers, right-click the Front End Server that you want to remove, and then click Delete.

4. Expand SQL stores, right-click the SQL Server database that is associated with the Standard Edition Front End Server, and then click Delete.

5. Publish the topology, check the replication status, and then run the Lync Server Deployment Wizard as needed.

So that’s it—if you are reading this, you survived a Lync Server 2010 to Lync Server 2013 migration. If you followed the steps in this chapter you should have great success with your migration efforts.