Export (0) Print
Expand All

Migrate Response Groups

Lync Server 2010
 

Topic Last Modified: 2012-10-17

You can migrate response group settings (agent groups, queues, and workflows) that you created on Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010. When you migrate Response Group settings, all the configuration settings, audio files, and contact objects are moved from the Office Communications Server 2007 R2 pool to the Lync Server 2010 pool, and all calls to migrated response group phone numbers are handled by Lync Server 2010. Calls to migrated response groups will no longer be handled by Communications Server 2007 R2.

To migrate Response Group settings from Office Communications Server 2007 R2 to Lync Server 2010, you need to run a migration cmdlet and then update the URL that users need to sign into and out of their response groups. If the Back End server in your Microsoft Office Communications Server 2007 R2 environment runs on SQL Server 2005, you first need to install the SQL Server 2005 Native Client on the Lync Server 2010 computer where you plan to run the Response Group migration cmdlet.

noteNote:
The Response Group migration cmdlet requires that the Response Group application is installed in your Lync Server 2010 pilot pool. You can ensure that Response Group is installed by running the Get-CsService –ApplicationServer command.
importantImportant:
The Response Group migration cmdlet moves settings for the entire pool. You cannot select specific groups, queues, or workflows to migrate.
noteNote:
The following procedure for migrating Response Group settings assumes that you have a one-to-one relationship between Office Communications Server 2007 R2 and Lync Server 2010 pools. If you plan to consolidate or split up pools during your migration and deployment, you need to plan which Office Communications Server 2007 R2 pool maps to which Lync Server 2010 pool.
noteNote:
After you run the Response Group migration cmdlet, a roll back to your Office Communications Server 2007 R2 pool is not possible. If you need to move your Response Group deployment back to the Office Communications Server 2007 R2 pool, you need to remove the migrated response groups from the Lync Server 2010 pool and redeploy them to your Office Communications Server 2007 R2 pool.

After you migrate Response Group, use Lync Server Control Panel or Lync Server Management Shell cmdlets to verify that all agent groups, queues, and workflows moved successfully.

  1. If the Back End Server in your Office Communications Server 2007 R2 pool runs on SQL Server 2005, download the Feature Pack for Microsoft SQL Server 2005 - December 2008 (SQLNCLI.MSI package) from the Microsoft Download Center at http://go.microsoft.com/fwlink/p/?LinkId=204105, and then install it on the computer where you plan to run the Response Group migration cmdlet.

  2. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or has equivalent administrator rights and permissions.

  3. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

  4. Run:

    Move-CsRgsConfiguration -Source <source pool FQDN> -Destination <destination pool FQDN>
    

    For example:

    Move-CsRgsConfiguration -Source se-r2.contoso.net -Destination lync-se.contoso.net
    
  5. If you deployed the Response Group tab for Microsoft Office Communicator 2007 R2 in your Office Communications Server 2007 R2 environment, remove the tab from the Office Communicator 2007 R2 tabs.xml file.

    noteNote:
    Formal agents used the Response Group tab to sign in to their response groups before they could receive calls. If you deployed the Response Group tab, you chose the location for the Office Communicator 2007 R2 tabs.xml file when you deployed it.
  6. Provide users with the updated URL that agents need to sign into and out of their response groups.

    noteNote:
    The URL is typically https://webpoolFQDN/RgsClients/Tab.aspx, where webpoolFQDN is the fully qualified domain name (FQDN) of the web pool that is associated with the pool that you just migrated to Lync Server 2010.
    noteNote:
    This step is not required after users upgrade to Microsoft Lync 2010 because the URL is available from the Tools menu in Lync 2010.

  1. Log on to the computer with an account that is a member of RTCUniversalReadOnlyAdmins group or is minimally a member of the CsViewOnlyAdministrator role.

  2. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.

  3. In the left navigation pane, click Response Groups.

  4. On the Workflow tab, verify that all the workflows in your Office Communications Server 2007 R2 environment are included in the list.

  5. Click the Queue tab, and verify that all the queues in your Office Communications Server 2007 R2 environment are included in the list.

  6. Click the Group tab, and verify that all the agent groups in your Office Communications Server 2007 R2 environment are included in the list.

  1. Log on to the computer with an account that is a member of RTCUniversalReadOnlyAdmins group or is minimally a member of the CsViewOnlyAdministrator role.

  2. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

    For details about the following cmdlets, run:

    Get-Help <cmdlet name> -Detailed
    
  3. Run:

    Get-CsRgsAgentGroup
    
  4. Verify that all the agent groups in your Office Communications Server 2007 R2 environment are included in the list.

  5. Run:

    Get-CsRgsQueue
    
  6. Verify that all the queues in your Office Communications Server 2007 R2 environment are included in the list.

  7. Run:

    Get-CsRgsWorkflow
    
  8. Verify that all the workflows in your Office Communications Server 2007 R2 environment are included in the list.

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