:: infotechGuyz.com ::
> For the IT community by the IT community

Migrate from OCS 2007 to Lync 2010 (Part III)

 

 

Join Lync 2010 to Legacy Edge Servers

After deploying Lync 2010, a federation route for this site is not configured. To use the federated route that is being used by Office Communications Server 2007 R2, Lync 2010 must be configured to use this route.

To enable the Lync 2010 site to use the Director and Edge Server of the BackCompatSite, use Topology Builder to associate the legacy Edge pool.

To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. You can also hand over the proper administrator rights and permissions. Only membership in the RTCUniversalServerAdmins group is required for other configuration changes.

 

To Associate the Legacy Edge Pool by using Topology Builder:

 1. Start Topology Builder: Click Start, clickAll Programs, click MS Lync 2010, and then click Lync Topology Builder.

2. Select your Lync 2010 site.

3. On the Actions menu, click Edit Properties.

4. Under Site federation route assignment, select Enable, and then select the Office Communications Server 2007 R2 Director listed.

5. Click OK to close the Edit Properties page.

6. In Topology Builder, navigate to the Standard Edition server or Front End pool, right-click the pool, and then click Edit Properties.

7. Under Associations, select the check box next to Associate Edge pool (for media components).

8. From the list, select the Edge Server for the BackCompatSite.

9. Click OK to close the Edit Properties page.

10. In Topology Builder, select the top-most node, Lync 2010.

11. From the Actions pane, click Publish Topology, and then click Next.

12. When the Publishing wizard completes, click Finish.

 

 

Connect Lync 2010 to Office OCS R2 Edge Server

For each Lync 2010 Front End Server or Standard Edition server and each Director in your pilot pool, the list of internal servers that are authorized to connect to the Office Communications Server 2007 R2 Edge Server must be updated. Without these updates, external audio/visual (A/V) conferencing for users joining by using the legacy Edge Server will not work. This topic explains how to add the Lync 2010 Front End Server or Standard Edition server and Director in your pilot pool to the list of servers that are authorized to connect to the Office Communications Server 2007 R2 Edge Server.

Authorize Connection to Office Communications Server 2007 R2 Edge Server:

1. Log on to Office Communications Server 2007 R2 Edge Server with a member account of the RTCLocalServerAdmins group.

2. From Office Communications Server 2007 R2 Edge Server, from the Administrative Tools group, open the Computer Management snap-in.

3. In console tree, expand Services and Applications.

4. Right-click Office Communications Server 2007 R2, and then click Properties.

5. Click the Internal tab.

6. Under Add Server, click Add.

7. In the Add Office Communications Server dialog box, enter the appropriate information:

• Specify the fully qualified domain name (FQDN) of each Lync 2010 Front End Server or Standard Edition server.
• Specify the FQDN of the Lync 2010 Director if you configured a static route on the pool that specifies the next hop computer by its FQDN.
  

8. After you have added an entry for each Lync 2010 Front End Server or Standard Edition server and Director, click OK to close the Properties page.

 

Connect Lync 2010 to Office OCS R2 Mediation Server

After deploying MS Lync 2010, a Mediation Server for this site is not configured. Lync 2010 must be configured to use this server in order to use the Mediation Server being used by MS Office Communications Server 2007.

If a Voice Route and Voice Policy existed in the legacy pool, after you merge Office Communications Server 2007 R2 with Lync 2010 and run the Import-CsLegacyConfigurationcmdlet, the Lync 2010 pilot pool now has all the necessary configuration information to route outbound calls through the legacy Office Communications Server 2007 R2 Mediation Server and route inbound calls from the legacy pool to the Lync 2010 pool

To enable the Lync 2010 pilot pool to use the legacy Mediation Server, you must have a Voice Route and Voice policy configured that point to the legacy Mediation Server. If you do not have a legacy Voice Route or Voice Policy, use the following the procedure to configure these settings using Lync 2010 Control Panel or by using the Lync Management Shell.

 

To create a voice route to the Legacy Mediation Server by using Lync Control Panel:

1. Log on to the computer with a member account of the RTCUniversalServerAdmins group or is assigned to the CsVoiceAdministrator administrative role.

2. Open a browser window, and then enter the Admin URL to open the Lync Control Panel. Click Voice Routing, and then click the Route tab.

3. Click New to create a New Voice Route.

4. Enter a name for the voice route. Enter a description for the voice route.

5. Until you reach Associated gateways, skip all remaining sections. Then click Add. Select listed default gateway and click OK.

6. Under Associated PSTN Usages, click Select.

7. From the Select PSTN Usage Record page, select the legacy Mediation Server fully qualified domain name (FQDN), and click OK.

8. From the New Voice Route page, click OK to create the Voice Route.

9. From the Voice Routing page, select Route.

10. Move the newly created route to the top of the list, and click Commit.

 

 

To create a voice route to the Legacy Mediation Server by using Lync Management Shell:

1. Log on to the computer with a member account of the RTCUniversalServerAdmins group or is assigned to the CsVoiceAdministrator administrative role.

2. Start Lync Management Shell: Click Start > All Programs > MS Lync 2010 > Lync Management Shell.

3. Run the following command to get the FQDN of the legacy Mediation Server:

Get-CsService –MediationServer

 

The Identity parameter will contain the name of the legacy Mediation Server.

 

4. Run the following command to verify that a voice policy exists for the legacy Mediation Server: Get-CsVoicePolicy

The PSTNUsages parameter should not be empty, but return a value of {Local} or the name of any customer PSTNUsage created on the legacy Mediation Server.

5. After verifying that a legacy Mediation Server exists and has a voice policy, create a route in the Lync 2010 pool that points to this legacy Mediation Server.

The following code defines a generic voice route that routes any outbound calls from the Lync 2010 pool to the legacy Mediation Server:

New-CsVoiceRoute -Name W13PSTNRoute -NumberPattern ".*" -PstnUsages Local -PstnGatewayList@{Add="MediationServer:medsvr01.domain.net"}

6. Run the following command to set the default voice route for this pool:

Set-CsVoiceRoute -Identity W13PSTNRoute -Priority 0

7. Run the Get-CsVoiceRoutecmdlet to verify voice route settings. For example, identity parameter should be set to W13PSTNRoute. PSTNUsages should be set to {Local} and PSTNGatewayList should point to FQDN of legacy Mediation Server, Mediation:medsvr01.domain.net.

 

Move Office OCS R2 User to Lync 2010

You can move a pilot user to the new MS Lync 2010 deployment using MS Lync 2010 Control Panel and Lync Management Shell methods. Certain requirements must be met to make sure a smooth transition to Lync 2010.

When you move a user to a Lync 2010 pool, the data for the user is moved to the back-end database that is associated with the new pool.

To move a user by using the Lync 2010 Control Panel:

1. Log on to Standard Edition server or Front End Server with a member account of the RTCUniversalServerAdmins group or a member of the CSAdministrator or CsUserAdministrator administrative role.

2. Click Start > All Programs > MS Lync 2010 > Lync Control Panel.

3. Click Users, click Add Filter, build the following query Legacy user Equal to True, and click Find.

4. In search results, select a user.

5. Click Action. Click Move selected users to pool.

6. In Move Users, select Destination registrar pool, which is your Lync 2010 pool, and click OK.

7. Verify that Registrar pool column for the user now contains the Lync 2010 pool. This indicates that the user has been moved successfully.

 

To move a user by using the Lync Management Shell:

1. Start Lync Management Shell: Click Start > All Programs > MS Lync 2010 > Lync Management Shell.

Make sure user account you are using is a member of the RTCUniversalServerAdmins group or a member of the CSAdministrator or CSUserAdministrator administrative role.

2. At the command line, type the following:

Get-CsUser -OnOfficeCommunicationServer

 Using a legacy user’s sip address as a parameter, run the Move-CsLegacyUsercmdlet.

Move-CsLegacyUser -Identity "sip address" -Target "pool_FQDN"

 

For example, to move one of the legacy users to the Lync 2010 pilot pool, run:

Move-CsLegacyUser -Identity "sip:kate@domain.net"-Target "lync-se.domain.net"

 

3. At the command line, type the following:

Get-CsUser"sip address"

 

The RegistrarPool identity now will point to the pool you specified as “pool_name” in the previous step. This identity confirms that the user has been moved successfully.

For more details about the Get-CsUsercmdlet described in this section, run: Get-Help Get-CsUser -Detailed

You can also verify that these users have been moved by viewing Registrar pool column through the Lync Control Panel.