Export (0) Print
Expand All
Expand Minimize

Import-CsRgsConfiguration

Lync Server 2013
 

Topic Last Modified: 2014-02-04

Imports Response Group configuration data that was previously exported using the Export-CsRgsConfiguration cmdlet. The ability to export and import Response Group configuration data is particularly useful disaster recovery scenarios. This cmdlet was introduced in Lync Server 2013.

Import-CsRgsConfiguration -Destination <RgsIdentity> -FileName <String> [-Force <SwitchParameter>] [-OverwriteOwner <SwitchParameter>] [-ReplaceExistingRgsSettings <SwitchParameter>] [-ResolveNameConflicts <SwitchParameter>]

The command shown in Example 1 imports a previously exported collection of Response Group application settings, and then applies those settings to the Response Group installation hosted by the Application Server on atl-cs-001.litwareinc.com.

Import-CsRgsConfiguration -FileName "C:\Export\RgsExport.zip" -Destination "ApplicationServer:atl-cs-001.litwareinc.com"

The Export-CsRgsConfiguration cmdlet and the Import-CsRgsConfiguration cmdlet enable you to export data about your current implementation of the Response Group application (including such things as workflows, queues, agent groups, holiday sets and business hours, as well as audio files and service configuration settings) and then later import (or re-import) that information. This can be extremely useful in a disaster recovery scenario (for example, in a case where the server hosting the Response Group application has failed) or if you simply need to transfer the Response Group application to a different pool.

Note that the Export-CsRgsConfiguration cmdlet and the Import-CsRgsConfiguration cmdlet are designed to work only with Lync Server 2013. If you want to migrate Response Group data from Microsoft Lync Server 2010 to Lync Server 2013, you should use the Move-CsRgsConfiguration cmdlet instead.

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 "Import-CsRgsConfiguration"}

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

 

Parameter Required Type Description

Destination

Required

Microsoft.Rtc.Rgs.Management.RgsIdentity

Identity of the Response Group instance where the configuration settings are being imported. For example:

-Destination "ApplicationServer:atl-rgs-001.litwareinc.com"

FileName

Required

System.String

Path to the .ZIP file created by the Export-CsRgsConfiguration cmdlet. For example:

-FileName "C:\Exports\RgsConfig.zip"

Force

Optional

System.Management.Automation.SwitchParameter

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

OverwriteOwner

Optional

System.Management.Automation.SwitchParameter

When present the current owner of the Response Group objects will be overwritten with the service identity of the new Response Group pool.

ReplaceExistingRgsSettings

Optional

System.Management.Automation.SwitchParameter

When specified, all the existing service settings for the destination pool are replaced with the imported settings. If not specified, then service settings will remain as-is and only Response Group object (such as workflows and agent groups) will be imported.

ResolveNameConflicts

Optional

System.Management.Automation.SwitchParameter

When present, duplicate names will be resolved by appending a unique identifying number. For example, if there are two workflows named Help Desk Workflow one of the two will be renamed Help Desk Workflow (2).

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

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