Topic Last Modified: 2011-04-05
The migration process is carried out by a series of Lync Server Management Shell cmdlets.
The Merge-CsLegacyTopology cmdlet is used to migrate trusted service entries and configuration settings from Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010. This cmdlet creates an output file that contains the merged information from Office Communications Server 2007 R2. This file is then used to publish information to the Lync Server 2010 Central Management store. Additionally, the Merge-CsLegacyTopology cmdlet allows you to input an XML file that contains Edge Server information. If you do not plan to import Edge Server information, remove the -UserInputFileName D:\input.xml parameter from Step 2 in the following procedure.
|Before running any of the migration cmdlets, be sure the account used is a member of the RTCUniversalServerAdmins group.|
The steps to migrate are:
- Start the Lync Server Management Shell: Click Start,
click All Programs, click Microsoft Lync Server 2010,
and then click Lync Server Management Shell.
Merge-CsLegacyTopology -TopologyXmlFileName D:\output.xml -UserInputFileName D:\input.xml
Publish-CsTopology -FileName D:\output.xml
Note: To verify that this step completed successfully, see Verify Topology Information.
Note: You might see a warning, similar to the following, indicating a legacy policy setting name includes characters that are being replaced with an underscore. You can safely ignore this warning. This policy setting name is a default policy that was included with Office Communications Server 2007 R2. Lync Server 2010 will import this policy but replace the offending characters with an underscore.
- Connect the pilot pool to the legacy Edge Servers by following
the procedure in Connect Pilot Pool to
Legacy Edge Servers.
Now that the merge has completed you can use Topology Builder and Lync Server Control Panel to administer the pool and view the overall side-by-side topology. For additional steps that you should run after migration has completed, see Phase 6: Verify Your Pilot Migration.