Merge Using Topology Builder Merge Wizard (Office Communications Server 2007 Migration)
Topic Last Modified: 2011-04-11
Topology Builder is a new tool introduced in Microsoft Lync Server 2010. With Topology Builder you can create, edit, and publish a Lync Server 2010 deployment topology. Additionally, the 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.
For details about an alternative method to using Topology Builder, see Migrate Using Lync Server Management Shell (optional) (Office Communications Server 2007 Migration).
The merge process does not move monitoring data or archiving data. The data you back up prior to decommissioning the legacy environment will be your history of activity in the Office Communications Server 2007 environment. For details about how archiving and monitoring work during the migration process, see Migrating Archiving and Monitoring Servers (Office Communications Server 2007 Migration).
To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged on as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper user rights for adding server roles. For details, see Delegate Setup Permissions in the Deployment documentation. For other configuration changes, only membership in the RTCUniversalServerAdmins group is required.
To merge topology information
Log on to the computer where Topology Builder is installed as a member of the Domain Admins group and the RTCUniversalServerAdmins group.
To open Topology Builder from the Standard Edition server or Front End Server, click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.
Select Download topology from existing deployment, and then click OK.
In the Save Topology As dialog box, select the Topology Builder file you want to use, and then click Save.
In the Actions pane, click Merge 2007 or 2007 R2 Topology, and then click Next.
In Specify Edge Setup, click Add.
In Specify Edge Version, select Office Communications Server 2007 Edge Server.
In Specify Internal Edge Settings Information, enter the relevant information for your Edge pool’s internal fully qualified domain name (FQDN) and ports as needed, and then click Next.
In Specify Federation Setting, select This Access Edge is used for federation and public IM connectivity. If you have multiple Edge Servers deployed, only one of them will be enabled for federation. If you do not select this check box and you decide later that you want to enable federation, you must run the Topology Builder Merge wizard again, and then publish your topology again.
In Specify Next Hop, enter the FQDN of the next hop location in your environment. In the following figure, the legacy Director from the Office Communications Server 2007 deployment is shown. Click Finish.
In Specify Edge Setup, if all your Communications Server 2007 Edge Servers have been added, click Next. If you have more Communications Server 2007 Edge Servers to add, repeat steps 6 through 10.
In Specify Internal SIP port, select the default settings (that is, if you did not modify the default SIP port). Change the settings as appropriate if you are not using a default port of 5061, and then click Next.
In Summary, click Next to begin merging the topologies.
The wizard page verifies that the merging of the topologies was successful.
In the Status column, verify that the value is Success, and then click Finish.
In the left pane of Topology Builder, you should now see BackCompatSite, which indicates that your Office Communications Server 2007 environment has been merged with Lync Server 2010.
From the Actions pane, select Publish Topology, and then click Next.
When the Publishing wizard completes, click Finish to close the wizard.
It is important that you complete the next topic, Import Policies and Settings (Office Communications Server 2007), to ensure that the legacy policy settings are imported into Lync Server 2010.