Export (0) Print
Expand All

Run Migration Cmdlets (Office Communications Server 2007 Migration)

Lync Server 2010
 

Topic Last Modified: 2011-04-06

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 to Microsoft Lync Server 2010. This cmdlet creates an output file that contains the merged information from Office Communications Server 2007. 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 don’t plan to import Edge Server information, remove the UserInputFileName D:\input.xml parameter from Step 2 in the following procedure.

importantImportant:
Before running any of the migration cmdlets, be sure the account used is a member of the RTCUniversalServerAdmins group.

The steps to migrate are:

  1. Log on to the computer where Lync Server Management Shell is installed as a member of the RTCUniversalServerAdmins group or with the necessary user rights as described in Delegate Setup Permissions.

  2. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

  3. Run:

    Merge-CsLegacyTopology -TopologyXmlFileName D:\output.xml -UserInputFileName D:\input.xml
    

    Where D:\output.xml is the path where Merge-CsLegacyTopology will write its output file. D:\input.xml is the path where Merge-CsLegacytopology expects to find the Edge Server input.xml file, defined earlier. Change the paths to match your environment accordingly.

  4. Run:

    Publish-CsTopology -FileName D:\output.xml
    

  5. Run:

    Enable-CsTopology
    
    noteNote:
    To verify that this step completed successfully, see Verify Topology Information (Office Communications Server 2007 Migration).
  6. Run:

    Import-CsLegacyConfiguration
    
    noteNote:
    You may see a warning, similar to the following figure, 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. Lync Server 2010 will import this policy but replace the offending characters with an underscore.
    Windows PowerShell Import Legacy Config warning

  7. Connect the pilot stack to the legacy Edge Servers by following the procedure in Connect Pilot Stack to Legacy Edge Servers (Office Communications Server 2007).

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 Stack Migration (Office Communications Server 2007 Migration).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft