Migrate from OCS 2007 R2 to Lync 2010 (Part II)

 

Lync 2010 Topology Builder Prerequisites

Windows Management Instrumentation (WMI) Backward Compatibility Package must be installed before running Topology Builder Merge wizard. Lync Server 2010 stores its configuration information in a Central Management store hosted on SQL Server 2008 SP1 or SQL Server 2005 Service Pack 3. Microsoft Office Communications Server 2007 R2 used Windows Management Instrumentation (WMI) framework. WMI Backward Compatibility Package enables Lync Server 2010 to merge WMI information from Office Communications Server 2007 R2 into the new format in Lync Server 2010.

 

 

To Install WMI Backward Compatibility Package:

1. On Standard Edition server or Front End Server, log on to computer with a member account of the Administrators group.

    2. From your installation media, navigate to \SETUP\AMD64\SETUP\OCSWMIBC.MSI.

    3. Install OCSWMIBC.MSI.

 

 

Running Topology Builder

Topology Builder is a new tool launched in Microsoft Lync Server 2010. You can create, edit, and publish a Lync Server 2010 deployment topology. Merge feature allows you to import information from your previous Office Communications Server environments and integrate it into a consolidated view alongside your Lync Server 2010 deployment.

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. It is also possible to hand over the proper administrator rights and permissions for adding server roles. Only membership in the RTCUniversalServerAdmins group is required for other configuration changes.

 

To Merge Topology Information:

  1. From Standard Edition server or Front End Server, click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.
  2. Select the option to Download topology from existing deployment, and then click OK.
  3. Click Save.
  4. In the Actions pane, click Merge 2007 or 2007 R2 Topology.
  5. Click Next.
  6. In Specify Edge Setup, click Add.
  7. In Specify Edge Version, select Office Communications Server 2007 R2 Edge Server, and then click Next.
  8. In Specify Edge Type, enter type of Edge Server configuration, and click Next. This example uses the Single Edge Server option.
  9. n Specify Internal Edge Settings Information, enter relevant information for your Edge pool’s internal FQDN and ports as needed, and then click Next.
  10. In Specify External Edge, enter the web conferencing FQDN information for your Edge Server.
  11. Check the This Edge pool is used for federation and public IM connectivity check box if you plan to use this Edge Server for federation. If multiple Edge Servers are deployed, only one of them will be enabled for federation. If you do not check this box and later decide that you want to enable federation, you must run the Topology Builder Merge wizard again, and then re-publish your topology.
  12. In Specify Next Hop, enter fully qualified domain name (FQDN) of next hop location in your environment. Click Finish.
  13. In Specify Edge Setup, if all your Communications Server 2007 R2 Edge Servers have been added, click Next. Repeat steps 6 through 12 if you need to add more Communications Server 2007 R2 Edge Servers.
  14. In Specify Internal SIP port setting, select default setting (if the default SIP port is not modified). Change appropriately if you are not using a default port of 5061, and click Next.
  15. In Summary, click Next to merge the topologies.
  16. Wizard page verifies that merging of topologies was successful.
  17. In Status column, verify that the value is Success, and then click Finish.
  18. In left pane of Topology Builder, you should see the BackCompatSite. This indicates that your Office Communications Server 2007 R2 environment has been merged with Lync Server 2010.
  19. From Actions pane, click Publish Topology, and then click Next.
  20. Click Finish when wizard completes.

 

Import OCS 2007 R2 Policies to Lync 2010

After you merge your Microsoft Office Communications Server 2007 R2 topology information with your Microsoft Lync Server 2010 pilot pool, you need to run a Lync Server Management Shell cmdlet to migrate your Office Communications Server 2007 R2 policies and configuration settings to your Lync Server 2010 pilot pool.

The Import-CsLegacyConfigurationcmdlet imports policies, dial plans, Communicator Web Access URLs, voice routes, and dial-in access numbers to Lync Server 2010.

 

To Migrate Policies and Settings:

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

2. Start the Lync Server Management Shell: Click Start > All Programs > Microsoft Lync Server 2010 > Lync Server Management Shell.

3. Run: Import-CsLegacyConfiguration
After policies are imported, use the procedure that follows to see the imported policies in the Lync Server 2010 Control Panel.

 

To View Imported Policies:

1. Log on to computer with a member account of the RTCUniversalServerAdmins group or of the CsViewOnlyAdministrator role.

2. Open a browser window, and enter Admin URL to open Lync Server Control Panel. Click Voice Routing and view imported policies.

3. Click Conferencing and view imported policies.

4. Click External User Access and view imported policies.

5. Click Monitoring and Archiving and view imported policies.