Import-CsLegacyConfiguration 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.Import-CsLegacyConfiguration cannot be used until you have first run the Merge-CsLegacyTopology cmdlet.
Syntax
Import-CsLegacyConfiguration [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-ReplaceExisting <SwitchParameter>] [-Report <String>] [-WhatIf [<SwitchParameter>]] |
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Report |
Optional |
String |
Path to the file where information will be recorded regarding any errors that may occur when you run Import-CsLegacyConferenceConfiguration. |
|
ReplaceExisting |
Optional |
Switch Parameter |
If present, this parameter instructs Import-CsLegacyConfiguration to handle any "name collisions" by overwriting an existing Microsoft Communications Server object with an object being imported. |
|
Force |
Optional |
Switch Parameter |
|
|
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
Import-CsLegacyConfiguration is used, in conjunction with the Merge-CsLegacyTopology cmdlet, to enable organizations to migrate from a previous version of Office Communications Server (either Office Communications Server 2007 or Office Communications Server 2007 R2) to Communications Server 2010. Import-CsLegacyConfiguration is used to migrate voice policies; location profiles (i.e., dial plans); voice routes; and voice normalization rules.
Before you can run Import-CsLegacyConfiguration you must first install WMI Backcompat; this application is installed by running the OCSWMIBC.msi. After installing WMI Backcompat, you should next run Merge-CsLegacyTopology. After you have called Merge-CsLegacyTopology you can then call Import-CsLegacyConfiguration. This 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 voice policy found in your installation of Office Communications Server a corresponding voice policy will be created in your new installation of Communications Server.
Return Types
Import-CsLegacyConfiguration does not return any objects or values.
Examples
-------------------------- Example 1 ------------------------
 Copy Code |
|
|---|---|
Import-CsLegacyConfiguration |
|
The command shown in Example 1 merges voice-related policies and settings from Office Communications Server 2007 (or Office Communications Server 2007 R2) with a new installation of Communications Server.
-------------------------- Example 2 ------------------------
| Copy Code |
|
|---|---|
Import-CsLegacyConfiguration -ReplaceExisting |
|
The command shown in Example 2 is a variation of the command shown in Example 1. In this case, however, the -ReplaceExisting parameter is included. This parameter instructs the cmdlet to use the imported data to deal with potential name collisions. For example, suppose you try to import a voice route named LocalRoute, and a voice route by that name already exists in your Communications Server installation. In that case, and because you included the -ReplaceExisting parameter, the Communications Server route will be replaced by the voice route being imported.