EXAMPLE 1

The command shown in Example 1 merges topology information and trusted service entries from Communications Server 2007 R2 or Communications Server 2007 with a new installation of Lync Server. The required parameter TopologyXmlFileName is used to indicate the path to the output file generated when you run the Merge-CsLegacyTopology cmdlet.

	Copy Code
Merge-CsLegacyTopology -TopologyXmlFileName C:\New_Topology.xml

EXAMPLE 2

Example 2 is a variation of the command used in Example 1. In Example 2, however, the UserInputFileName parameter is included in order to merge Edge Server information into the topology. The parameter value C:\EdgeServers.xml points to a custom XML file containing Edge Server information for Office Communications Server.

	Copy Code
Merge-CsLegacyTopology -TopologyXmlFileName C:\New_Topology.xml -UserInputFileName C:\EdgeServers.xml

The Merge-CsLegacyTopology cmdlet is the first tool to use when migrating from an earlier version of Office Communications Server (either Office Communications Server 2007 R2 or Office Communications Server 2007) to Lync Server. The Merge-CsLegacyTopology cmdlet is used to migrate trusted service entries and topology information for the following components: domains, user services, Registrar, Mediation Server, and Edge Server. In addition, the cmdlet migrates trusted service entries for the Conferencing Attendant application; Communicator Web Access; and conferencing directories. (A trusted service entry is an Active Directory record that represents a server trusted by Lync Server.) Merging the topology information enables users homed on Lync Server to communicate with users homed on Communications Server 2007 or Communications Server 2007 R2.

Before you can run the Merge-CsLegacyTopology cmdlet you must first install the Windows Management Instrumentation (WMI) Backward Compatibility interfaces package; this application is installed by running OCSWMIBC.msi. (OCSWMIBC.msi can be found on the installation DVD in the Setup.) After installing the Compatibility interfaces package, the Merge-CsLegacyTopology cmdlet can then be called. The Merge-CsLegacyTopology cmdlet will use WMI to read legacy data from the earlier version of Office Communications Server; it will then take the retrieved data and create corresponding objects in Lync Server. For example, for each SIP domain found in your installation of Office Communications Server, a corresponding SIP domain will be created in your new installation of Lync Server.

After running the Merge-CsLegacyTopology cmdlet, you should then run the Import-CsLegacyConfiguration cmdlet and the Import-CsLegacyConferenceDirectory cmdlet.

The Merge-CsLegacyTopology cmdlet needs to be run at least twice: once at the start of a migration (in order to introduce the Communications Server 2007 or Communications Server 2007 R2 topology), and once at the end of migration, when the previous Office Communications Server environment has been decommissioned. You will also need to run the cmdlet any time you make a change to your legacy Office Communications Server environment. For example, if you add a Mediation Server to or decommission a pool from your Office Communications Server topology, you will need to re-run the Merge-CsLegacyTopology cmdlet in order to import the modified topology.

The Import-CsLegacyConfiguration cmdlet and the Import-CsLegacyConferenceDirectory cmdlet depend on values configured by the Merge-CsLegacyTopology cmdlet. That means that you might receive error messages from either the Import-CsLegacyConfiguration cmdlet or the Import-CsLegacyConferenceDirectory cmdlet that instruct you to run the Merge-CsLegacyTopology cmdlet as a possible solution to the problem that just occurred. If you do not re-run the Merge-CsLegacyTopology cmdlet, then additional errors can occur, especially if an item is removed from the Office Communications Server environment while it is still in use by Lync Server.

If you need to merge Edge Servers from a previous installation of Office Communications Server you must first create a custom XML file that contains your Edge Server; you must create the file yourself because Edge Server settings are not stored in Active Directory, and, as a result, cannot be retrieved by the Merge-CsLegacyTopology cmdlet. After you have created this XML file (see the Lync Server Deployment Guide for information on how to create this file) you must include the path to that file and the UserInputFileName parameter when running the Merge-CsLegacyTopology cmdlet. If you do not do this no Edge Servers will be included in your merged topology.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Merge-CsLegacyTopology cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Merge-CsLegacyTopology"}

None. The Merge-CsLegacyTopology cmdlet does not accept pipelined input.

The Merge-CsLegacyTopology cmdlet does not return any objects or values.