Topic Last Modified: 2013-02-22

Moves a Lync Server 2013 meeting room object from one Registrar pool to another. A meeting room is a conferencing device designed to address video conferencing and collaboration scenarios in small conference rooms. This cmdlet was introduced in Lync Server 2013.

Syntax

Move-CsMeetingRoom -Identity <UserIdParameter> -Target <Fqdn> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Force <SwitchParameter>] [-IgnoreBackendStoreException <SwitchParameter>] [-PassThru <SwitchParameter>] [-ProxyPool <Fqdn>] [-WhatIf [<SwitchParameter>]]

Examples

Example 1

The command shown in Example 1 moves the meeting room with the display name "Room 14" to the pool atl-cs-001.litwareinc.com.

Copy Code 
Move-CsMeetingRoom -Target "atl-cs-001.litwareinc.com" -Identity "Room 14"

Example 2

Example 2 moves all the meeting rooms in the organization to the pool atl-cs-001.litwareinc.com. To do this, the command first calls the Get-CsMeetingRoom cmdlet without any parameters; that returns a collection of all the meeting rooms configured for use in the organization. That collection is then piped to the Move-CsMeetingRoom cmdlet, which moves each meeting room in the collection to the new pool.

Copy Code 
Get-CsMeetingRoom | Move-CsMeetingRoom -Target "atl-cs-001.litwareinc.com"

Detailed Description

In Lync Server, meeting rooms are self-contained computer appliances that are installed in conference rooms and supply advanced meeting capabilities such as:

  • One touch meeting join experience

  • Multi-view video gallery

  • Touch-enabled white-boarding on the front of room screen

  • Calendar integration to provide access to scheduled meetings

  • Content sharing and switching

In order to manage these new endpoint devices you must, among other things, create and enable a Microsoft Exchange Server 2013 resource mailbox account for the device, then enable that resource account for Lync Server 2013. Note that, for Lync Server, there are no cmdlets for creating or removing meeting rooms. Instead, you use the Enable-CsMeetingRoom cmdlet to enable meeting rooms and the Disable-CsMeetingRoom cmdlet to disable meeting rooms. The resource account must already exist in order for you to enable the meeting room, and disabling a meeting room only removes that room from your collection of meeting rooms; it does not delete the resource mailbox account.

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 command-line interface prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Move-CsMeetingRoom"}

Lync Server Control Panel: The functions carried out by the Move-CsMeetingRoom cmdlet are not available in the Lync Server Control Panel.

Parameters

Parameter Required Type Description

Identity

Required

Microsoft.Rtc.Management.AD.UserIdParameter

Indicates the Identity of the meeting room to be moved. Meeting rooms can be specified using one of four formats: 1) the room's SIP address; 2) the room's user principal name (UPN); 3) the room's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the room's Active Directory display name (for example, Main Conference Room). User Identities can also be referenced by using the room's Active Directory distinguished name.

Target

Required

Microsoft.Rtc.Management.Deploy.Fqdn

The FQDN (for example, atl-cs-001.litwareinc.com) of the Registrar pool where the meeting room should be moved.

Confirm

Optional

System.Management.Automation.SwitchParameter

Prompts you for confirmation before executing the command.

DomainController

Optional

Microsoft.Rtc.Management.Deploy.Fqdn

Enables you to connect to the specified domain controller in order to move a meeting room. To connect to a particular domain controller, include the DomainController parameter followed by the computer name (for example, atl-dc-001) or its fully qualified domain name (FQDN) (for example, atl-dc-001.litwareinc.com).

Force

Optional

System.Management.Automation.SwitchParameter

When present, instructs the Move-CsMeetingRoom cmdlet to ignore all errors that might occur when carrying out the move operation. As a general rule, you should avoid using the Force parameter unless absolutely necessary.

IgnoreBackendStoreException

Optional

System.Management.Automation.SwitchParameter

When present, instructs the computer to ignore any errors that might occur with the backend database and attempt to the move meeting room despite those errors.

PassThru

Optional

System.Management.Automation.SwitchParameter

Enables you to pass a meeting room object through the pipeline that represents the meeting room being moved. By default, the Move-CsMeetingRoom cmdlet does not pass objects through the pipeline.

ProxyPool

Optional

Microsoft.Rtc.Management.Deploy.Fqdn

This parameter is not used with the on-premises version of Lync Server 2013.

WhatIf

Optional

System.Management.Automation.SwitchParameter

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

Input Types

The Moves-CsMeetingRoom cmdlet accepts pipelined instances of the Microsoft.Rtc.Management.ADConnect.Schema.OCSADMeetingRoom object.

Return Types

None.

See Also