UC Unleashed

While implementing some Response Groups, I noticed that users who went to Tools>Response Group Settings in the Lync client would land at a page that said “You are not a member of any group. For assistance, contact your support team“. The happened for all users of all response groups. It’s critical that users be able to access this page, especially if they are agents of a response group set for a formal participation policy, as this is the page a user goes to to sign into and out of a response group.

I found some info by Drago Totev, who mentioned that some settings in the topology builder file are now case sensitive. The RTM and later versions of Lync require “urn:application:RGS” – notice the case, but some RC versions used lower case. This environment never had RC code in place – migrating from OCS 2007 R2 directly to Lync RTM code. I exported the topology to a .tbxml file anyways, made a copy for backup, and opened it in XML Notepad 2007*, and I searched for and found several instances of “urn:application:Rgs” (see screenshot below). I replaced all four of the instances of the lower case “urn:application:Rgs” with the upper case RGS version.

XML Notepad

Then I re-imported the file into Topology Builder and published it. Once I verified that replication had completed via Get-CsManagementStoreReplicationStatus, I restarted the Response Group service on my front end servers.

After restarting the Lync client, going to Tools>Response Group Settings now takes the user to the correct page showing the response groups that the user is a member of.

Response Groups

Users now also see the notification in the Lync client notifying them they’ve been added to a Response Group:

Response Group notification

* Note: Do not use Notepad to edit the topology XML. Doing so can result in system instability.