Export (0) Print
Expand All
Expand Minimize

Import-CsLegacyConferenceDirectory

 

Topic Last Modified: 2014-07-01

The Import-CsLegacyConferenceDirectory cmdlet enables you to import conference directories from Microsoft Office Communications Server 2007 R2 to Lync Server. This helps provide interoperability between Lync Server and Office Communications Server 2007 R2. This cmdlet was introduced in Lync Server 2010.

Import-CsLegacyConferenceDirectory [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Report <String>] [-WhatIf [<SwitchParameter>]]

The command shown in Example 1 imports conferencing directories from Communications Server 2007 R2 to Lync Server.

Import-CsLegacyConferenceDirectory

The Import-CsLegacyConferenceDirectory cmdlet is used in conjunction with the Merge-CsLegacyTopology cmdlet to enable organizations to migrate from Office Communications Server 2007 R2 to Lync Server. The Import-CsLegacyConfiguration cmdlet imports conferencing directories from Communications Server 2007 R2 to Lync Server.

Before you can run the Import-CsLegacyConferenceDirectory 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 Lync Server installation DVD in the Setup folder.) After installing the Backward Compatibility interfaces package, you should next run the Merge-CsLegacyTopology cmdlet.

When the Merge-CsLegacyTopology cmdlet finishes running, you can call the Import-CsLegacyConferenceDirectory cmdlet. The Import-CsLegacyConferenceDirectory cmdlet first uses WMI to read legacy data from Communications Server 2007 R2, then takes the retrieved data and creates corresponding objects in Lync Server: for each conferencing directory found in your installation of Communications Server 2007 R2, a corresponding directory will be created in your new installation of Lync Server.

The Import-CsLegacyConferenceDirectory cmdlet should be rerun anytime conferences directories are added, deleted, or moved in the Communications Server 2007 R2 environment. The Import-CsLegacyConferenceDirectory cmdlet should also be run anytime the Merge-CsLegacyTopology cmdlet is run; this helps to ensure the conference directories and the topology remain in sync.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Import-CsLegacyConferenceDirectory 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 "Import-CsLegacyConferenceDirectory"}

 

Parameter Required Type Description

Confirm

Optional

System.Management.Automation.SwitchParameter

Prompts you for confirmation before executing the command.

Force

Optional

System.Management.Automation.SwitchParameter

Suppresses the display of any non-fatal error message that might occur when running the command.

Report

Optional

System.String

Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\ImportDirectories.html"

WhatIf

Optional

System.Management.Automation.SwitchParameter

Describes what would happen if you executed the command without actually executing the command.

None. The Import-CsLegacyConferenceDirectory cmdlet does not accept pipelined input.

The Import-CsLegacyConferenceDirectory cmdlet does not return any objects or values.

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