Topic Last Modified: 2012-10-05

Response Group is an Enterprise Voice call management feature. This topic describes what you need to have in place before you can configure Response Group and the administrative credentials and permissions you need to perform configuration tasks.

This section assumes that you have read the planning documentation related to Response Group. For details, see Planning for Call Management Features in the Planning documentation.

Configuration Tools and Administrative Roles

You can use the following administrative tools to configure Response Group:

  • Lync Server Control Panel

  • Response Group Configuration Tool

  • Lync Server Management Shell

To configure response groups, you must be a member of at least one of the following administrative roles:

Active Directory Security Group (1)

Create Workflow

Assign Manager

Create /assign agents, queues

Create / manage holiday and business hours

Activate / deactivate workflow

Configure workflow (IVR or Hunt Group)


















(1) An Active Directory Domain Services user object must be a member of the specified Active Directory security group listed. An administrator or other delegated Active Directory group member with appropriate permissions to add users to a security group (For example, Administrator, Account Operators) must add a user object to the listed security group or group for the user to be able to perform the functions listed. (2) Only for workflows that the CsResponseGroupAdministrator has assigned to the CsResponseGroupManager. (3) A Response Group Manager can assign another member of CsResponseGroupManager to a workflow that the current manager already manages. (4) CsViewOnlyAdministrator can only run verb "Get" Lync Server Management Shell cmdlets.

Response Group Configuration Prerequisites

Response Group requires the following components:

  • Application service

  • Response Group application

  • Language packs

  • File store (to hold audio files)

  • Web Services (includes the Response Group Configuration Tool and the agents' sign-in and sign-out console)

All of these components are installed by default when you deploy Enterprise Voice.

You might need to perform the following tasks before configuring Response Group:

  • Enable users for Lync Server 2013 and Enterprise Voice.

  • Modify a configuration file to be compliant with Federal Information Processing Standards (FIPS).

  • Modify the database collation to support Yi, Meng, and Zang characters for queue names and agent group names.

Enabling Users

The first step in configuring Response Group is to create agent groups. Before you can create an agent group, you must enable the users who will be agents for Response Group for Lync Server 2013 and Enterprise Voice. Enabling users for Lync Server 2013 is typically a step in the Enterprise Edition server or Standard Edition server deployment. For details about enabling users for Lync Server 2013, see Disable or Re-Enable User Account for Lync Server. Enabling users for Enterprise Voice is typically a step in the Enterprise Voice deployment. For details, see Enable Users for Enterprise Voice.

Complying with FIPS requirements

This section applies to you only if your organization needs to comply with Federal Information Processing Standards (FIPS).

To be compliant with FIPS, you need to modify the application-level Web.config file to use a different cryptography algorithm after you install Web Services. You need to specify that ASP.NET use the Triple Data Encryption Standard (3DES) algorithm to process view state data. For the Response Group application, this requirement applies to the Response Group Configuration Tool and the agent sign-in and sign-out console. For details about this requirement, see Microsoft Knowledge Base article 911722, "You may receive an error message when you access ASP.NET webpages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0," at

To modify the Web.config file, do the following:

  1. In a text editor such as Notepad, open the application-level Web.config file.

  2. In the Web.config file, locate the <system.web> section.

  3. Add the following <machineKey> section to in the <system.web> section:

    Copy Code
    <machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
  4. Save the Web.config file.

  5. Restart the Internet Information Services (IIS) service by running the following command at a command prompt:

    Copy Code

Supporting Yi, Meng, and Zang Characters

This section applies to you only if your organization needs to support Yi, Meng, or Zang characters.

For information on what the Yi, Meng, and Zang characters are and why they may be important to your deployment, see the information on the GB18030 character sets

To support Yi, Meng, or Zang characters, you need to modify the collation for the Rgsconfig database. Change the collation of the Name column in the following tables in each Rgsconfig database:

  • dbo.AgentGroups

  • dbo.BusinessHours

  • dbo.HolidaySets

  • dbo.Queues

  • dbo.Workflows

For SQL Server 2008 R2 and SQL Server 2012, use the Latin_General_100 (Accent Sensitive) collation. If you use this collation, all object names are not case-sensitive.

You can change the collation by using Microsoft SQL Server Management Studio. For details about using this tool, see "Using SQL Server Management Studio" at Follow these steps to change the collation:

  1. Be sure that SQL Server Management Studio is configured to allow changes that require tables to be recreated. For details, see "Save (Not Permitted) Dialog Box" at For details about setting a column collation, see "How to: Set Column Collation (Visual Database Tools)" at

  2. Using Microsoft SQL Server Management Studio, connect to the Rgsconfig database.

  3. Find the table you want to change in the Rgsconfig database, right-click the table, and click Design.

  4. Change the collation of the Name column and save the table.