Topic Last Modified: 2013-03-06

Moves an existing conference directory from one pool to another. Conference directories are used to help dial-in conferencing users locate conference information. This cmdlet was introduced in Lync Server 2010.


Move-CsConferenceDirectory -Identity <XdsGlobalRelativeIdentity> -TargetPool <String> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]]



The command shown in Example 1 moves the conference directory with the Identity 3 to the pool

Copy Code
Move-CsConferenceDirectory -Identity 3 -TargetPool


The command shown in Example 2 is a variation of the command shown in Example 1. In this case, however, the Force parameter is included to ensure that the move takes place even if the target pool is currently unavailable.

Copy Code
Move-CsConferenceDirectory -Identity 3 -TargetPool -Force


Example 3 moves all the existing conference directories to the target pool To carry out this task the command first uses the Get-CsConferenceDirectory cmdlet to return a collection of all the conference directories currently in use in the organization. This collection is then piped to the Move-CsConferenceDirectory cmdlet, which moves each directory in the collection to the target pool.

Copy Code
Get-CsConferenceDirectory | Move-CsConferenceDirectory -TargetPool 

Detailed Description

When you create a dial-in conferencing Uniform Resource Identifier (URI), those URIs are assigned unique SIP addresses. However, SIP addresses are difficult to translate to devices that are not SIP-aware; for example, a public switched telephone network (PSTN) telephone can’t translate a SIP address. Because of that, Lync Server uses conference directories as a way to help these devices locate, and connect to, dial-in conferences. This is done by creating a SIP conference directory that is associated with each dial-in conferencing URI, and is identified by an integer value rather than a SIP URI. PSTN telephones and other devices can then use these numbers instead of a SIP URI when connecting to conferences; the directory number is included in the PSTN conference identification users enter when connecting to a dial-in conference.

Occasionally, you might need to move a conference directory from one pool to another; for example, if you decommission a pool you might need to move your existing conference directories to a new location. The Move-CsConferenceDirectory cmdlet enables you to move conference directories to a different pool.

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


Parameter Required Type Description




Numeric identity of the conference directory to be moved.




Fully qualified domain name (FQDN) of the pool where the conference directory is to be moved. For example: -Identity




Prompts you for confirmation before executing the command.




When present, moves the conference directory even if the target pool is currently unavailable. By default, the Move-CsConferenceDirectory cmdlet will not move directories if the target pool cannot be contacted.

Before running the Move-CsConferenceDirectory cmdlet with the Force parameter you should use Dbimpexp.exe to manually export the legacy data and then import this data to the target Registrar pool. Dbimpexp.exe can be found in the root folder of the Lync Server installation media.




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

Input Types

None. The Move-CsConferenceDirectory cmdlet does not accept pipelined input.

Return Types


See Also