"Only one of DistributionGroupAddress and AgentsByUri must be set" during Move-CsRgsConfiguration RRS feed

  • General discussion

  • I couldn't find ANY info about this error so I will post how I resolved the issue.

    Topic: Migration from Lync Server 2010 to Lync Server 2013

    Situation: Migrating Response Groups using "Move-CsRgsConfiguration"

    Error: Only one of "DistributionGroupAddress" and "AgentsByUri" must be set.

    For some reason (maybe by design, maybe not), many of our Response Group Agent Groups had values for both "DistributionGroupAddress" and "AgentsByUri" properties.  In the Control Panel, if you change the "Agents" drop-down box back to "Define a custom group of agents", you don't see any agents listed.  However, the custom list of agents DOES still exist in the properties of the Agent Group.  You can see this by using the PowerShell command "get-csrgsagentgroup".  

    Resolution: In the Control Panel, for each Agent Group whose "Agents" type is "Use an existing email distribution list", I...

    1. Changed Agents type to "Define a custom group of agents"
    2. Commited the change
    3. Switched it back to "Use an existing email distribution list" (email address automatically reappears)
    4. Commited the change again
    5. Run "get-csrgsagentgroup" again to make sure each group doesn't contain values for both "DistributionGroupAddress" and "AgentsByUri".
    6. Run "Move-CsRgsConfiguration" and it completes successfully!

    You might be able to remove the "AgentsByUri" value programatically using PowerShell but I didn't try it that way.

    • Edited by Russ-ASID Thursday, January 24, 2013 4:39 PM Minor cosmetic edits
    Thursday, January 24, 2013 4:37 PM

All replies

  • hanks Russ.  That is exactly what happened to us during our 2010 to 2013 migration. Your post was very helpful and saved a lot of time researching that issue.
    Monday, April 22, 2013 7:24 PM
  • Great post!

    Thank you

    Sunday, April 28, 2013 4:08 PM
  • Same issue here, used your suggestion and all was well.  Thanks.
    Monday, May 6, 2013 11:17 PM
  • Thanks for this post. This helped us identify the issue with our response group migration but we have over 300 agent groups that use distribution lists, so changing them by hand wasn't something we were willing to do. We tried clearing AgentsByUri using PowerShel $x.AgentsByUri.Clear(), but it didn't work as the agent list would get populated immediately from an AD lookup. We tried removing DistributionGroupAddress using PowerShell $x.DistributionGroupAddress.Remove function and that didn't work either (also tried .Replace with blank). In the end, we inserted a bogus distribution list using $x.DistributionGroupAddress = but kept an identifier in the bogus name so we can restore the distribution list after migration. After inserting bogus names, we restarted RTCRGS on all front-ends to clear AgentsByUri. The migration of close to 600 response group configurations ran successfully and completed in 4 mins. We then restored DistributionGroupAddress on affected agent groups with the correct distribution list and restarted RTCRGS on all 2013 front-ends to speed up the process.
    Sunday, September 29, 2013 7:39 AM
  • Thanks!
    Wednesday, October 23, 2013 2:02 PM
  • THANKS!!!!!

    Andrew Morpeth
    Lync Server Specialist - Auckland, NZ
    LinkedIn Profile

    Wednesday, November 6, 2013 9:20 PM
  • Thank you for publishing your solution for this problem. It was of great help and much appreciated!

    Monday, December 9, 2013 9:09 AM