Merge-CsLegacyTopology enables you to migrate configuration settings from a previous version of Office Communications Server (e.g., Microsoft Office Communications Server 2007 R2) to Microsoft Communications Server 2010.0 Merge-CsLegacyTopology should be used in conjunction with the Import-CsLegacyConfiguration and Import-CsLegacyConferenceDirectory cmdlets.
Syntax
Merge-CsLegacyTopology -TopologyXmlFileName <String> [-UserInputFileName <String>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-LocalStore <SwitchParameter>] [-Report <String>] [-WhatIf [<SwitchParameter>]] |
Merge-CsLegacyTopology -Reserved <PSObject> [-UserInputFileName <String>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-LocalStore <SwitchParameter>] [-Report <String>] [-WhatIf [<SwitchParameter>]] |
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
TopologyXmlFileName |
Required |
String |
Path to the output file to be created when Merge-CsLegacyTopology is run. Note that this file differs from the file specified using the -Report parameter; the latter file is used for recording error information while the Topology XML file contains your newly-created Microsoft Communications Server topology. This file will later be used by the Publsih-CsTopology cmdlet to publish the new topology. If the specified file already exists it will be overwritten when you run Merge-CsLegacyTopology. |
|
UserInputFileName |
Optional |
String |
Path to the XML file used to import Edge server data from a previous version of Office Communications Server. This XML file (which you must create yourself following the guidelines detailed in the Microsoft Communications Server Deployment Guide) is required because Edge server settings are not stored in WMI. If you do not need to import Edge server information then this parameter can be omitted. |
|
Report |
Optional |
String |
Path to the file where information will be recorded regarding any errors that may occur when you run Merge-CsLegacyTopology. |
|
Force |
Optional |
Switch Parameter |
|
|
Reserved |
Optional |
Switch Parameter |
|
|
LocalStore |
Optional |
Switch Parameter |
This parameter is for testing purposes only. |
|
WhatIf |
Optional |
Switch Parameter |
Describes what would happen if you executed the command without actually executing the command. |
|
Confirm |
Optional |
Switch Parameter |
Prompts you for confirmation before executing the command. |
Detailed Description
The Merge-CsLegacyTopology cmdlet is the first tool to use when migrating from a previous version of Office Communications Server (either Office Communications Server 2007 or Office Communications Server 2007 R2) to Communications Server 2010. Merge-CsLegacyTopology is used to migrate trusted service entries and configuration settings for the following components: domains; user services; Registrar; Mediation server; and Edge server. In addition, the cmdlet migrates trusted service entries for Conferencing Attendant; Communicator Web Access; and conferencing directories. (A trusted service entry is an Active Directory record that represents a server trusted by Communications Server.)
Before you can run Merge-CsLegacyTopology you must first install WMI Backcompat; this application is installed by running the OCSWMIBC.msi. After installing WMI Backcompat Merge-CsLegacyTopology can then be called. The cmdlet will use WMI to read "legacy" data from the previous version of Office Communications Server; it will then take that data and create corresponding objects in Communications 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 Communications Server.
After running Merge-CsLegacyTopology you should then run the cmdlets Import-CsLegacyConfiguration and Import-CsLegacyConferenceDirectory.
Return Types
Merge-CsLegacyTopology does not return any objects or values.
Examples
-------------------------- Example 1 ------------------------
 Copy Code |
|
|---|---|
Merge-CsLegacyTopology -TopologyXmlFileName C:\New_Topology.xml |
|
The command shown in Example 1 merges configuration settings and trusted service entries from Office Communications Server 2007 (or Office Communications Server 2007 R2) with a new installation of Communications Server. The required -TopologyXmlFileName is used to indicate the path to the output file generated when you run Merge-CsLegacyTopology.