Export (0) Print
Expand All

Move a Conference Directory and Dial-in Conferencing Contact Objects

Lync Server 2010
 

Topic Last Modified: 2011-04-06

If you deployed dial-in conferencing, you must move or remove all conference directories for each pool in the deployment. Each conference directory corresponds to a dial-in conferencing access number. If the following is true:

  • your topology includes conference directories that you imported from Microsoft Office Communications Server 2007 R2 or Microsoft Office Communications Server 2007

  • you are in the process of performing a side-by-side migration

  • you are in the phase during which migrated dial-in conferencing access numbers exist in both your pools running a previous release of Office Communications Server and in your Microsoft Lync Server 2010 pools

Then, do not remove the conference directories that were created using a previous release of Office Communications Server along with the conference directories hosted on Lync Server 2010 pools. Instead, move or remove the conference directories individually.

To move the data associated with conference directories, use the Lync Server 2010, Resource Kit Tools. You can use the WebConfDataTool.exe tool to move users' conference data to another server conference directory.

  1. Log on to the computer where Lync Server Management Shell is installed as a member of the RTCUniversalServerAdmins group or a role-based access control role to which you have assigned the Get-CsConferenceDirectory and the Remove-CsConferenceDirectory cmdlet.

  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. To use the Get-CsConferenceDirectory cmdlet to display all of the conference directories configured for use in your organization and the Remove-CsConferenceDirectory cmdlet to remove all conference directories, type:

    importantImportant:
    The following code removes all conference directories. If you have conference directories that you imported from Microsoft Office Communications Server 2007 R2 or Microsoft Office Communications Server 2007, do not remove them. Instead, see the "To remove individual conference directories" procedure later in this topic.
    Get-CsConferenceDirectory | Remove-CsConferenceDirectory
    

  1. Log on to the computer where Lync Server Management Shell is installed as a member of the RTCUniversalServerAdmins group or a role-based access control role to which you have assigned the Get-CsConferenceDirectory and the Remove-CsConferenceDirectory cmdlet.

  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. To use the Get-CsConferenceDirectory cmdlet to display all the conference directories configured for use in your organization, type:

    Get-CsConferenceDirectory
    
    noteNote:
    You can use the ServiceID property to identify conference directories imported from previous versions. The ServiceID property is based on the fully qualified domain name (FQDN) of the pool that hosts the conference directory. Do not remove conference directories that correspond to a legacy pool.
  4. To use the Remove-CsConferenceDirectory cmdlet to remove an individual conference directory, type:

    Remove-CsConferenceDirectory -Identity <XdsGlobalRelativeIdentity> [-Force <SwitchParameter>]
    

    For example:

    Remove-CsConferenceDirectory -Identity 2 -Force
    

    In the preceding example, the cmdlet removes the conference directory with the Identity "2." Furthermore, the Force parameter removes the conference directory even if the pool that hosts the directory is currently unavailable. By default, Remove-CsConferenceDirectory does not remove directories if the corresponding pool cannot be contacted.

  5. Repeat the previous step for all conference directories that were not created using a previous release of Office Communications Server.

  1. Log on to the computer where Lync Server Management Shell is installed as a member of the RTCUniversalServerAdmins group or a role-based access control role to which you have assigned the Get-CsConferenceDirectory and the Move-CsConferenceDirectory cmdlet.

  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. To use the Get-CsConferenceDirectory cmdlet to display all the conference directories configured for use in your organization and the Move-CsConferenceDirectory cmdlet to move all conference directories, type:

    importantImportant:
    The following code moves all conference directories. If you have conference directories that you imported from Microsoft Office Communications Server 2007 R2 or Microsoft Office Communications Server 2007, do not move them. Instead, see the "To move individual conference directories to another pool" procedure later in this topic.
    Get-CsConferenceDirectory | Where-Object {$_.ServiceId -match "UserServer:<PoolFQDN>"} | Move-CsConferenceDirectory - Target <DestinationServerPoolFQDN>
    

    Where <DestinationServerPoolFQDN> is the pool where you want to move the conference directories.

  1. Log on to the computer where Lync Server Management Shell is installed as a member of the RTCUniversalServerAdmins group or a role-based access control role to which you have assigned the Get-CsConferenceDirectory and the Move-CsConferenceDirectory cmdlet.

  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. To use the Get-CsConferenceDirectory cmdlet to display all the conference directories configured for use in your organization, type:

    Get-CsConferenceDirectory
    
    noteNote:
    You can identify conference directories imported from previous versions by the ServiceID property. The ServiceID property is based on the FQDN of the pool that hosts the conference directory. Do not move conference directories that correspond to a Microsoft Office Communications Server 2007 R2 or earlier version.
  4. To use the Move-CsConferenceDirectory cmdlet to move an individual conference directory, type:

    Move-CsConferenceDirectory -Identity <XdsGlobalRelativeIdentity> [-Force <SwitchParameter>]
    

    For example:

    Move-CsConferenceDirectory -Identity 2  -Target <DestinationServerPoolFqdn> -Force
    

    The command shown in the preceding example moves the conference directory with the Identity "2" to the pool <DestinationServerPoolFqdn>. Further, the Force parameter moves the conference directory even if the pool that hosts the directory is currently unavailable. By default, Move-CsConferenceDirectory does not move directories if the corresponding pool cannot be contacted.

  5. Repeat the previous step for all conference directories that were not created using a previous release of Office Communications Server.

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