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

Somehow a bunch of our RGS Agent Groups had values for both "DistributionGroupAddress" and "AgentsByUri" properties. This was causing the Response Group migration to stop dead in its tracks! Thankfully Russ over on the MS forums had a solution:

http://social.technet.microsoft.com/Forums/lync/en-US/d712b09c-606b-4a1e-abba-146948ba83d9/only-one-of-distributiongroupaddress-and-agentsbyuri-must-be-set-during-movecsrgsconfiguration?forum=lyncdeploy

Migrate UM contact objects from Lync 2010 to Lync 2013

There is a very easy way to get this done - one line of PowerShell actually:

Get-CsExUmContact -Filter {RegistrarPool -eq “pool01.domain.com”} | Move-CsExUmContact -Target pool02.domain.com

Microsoft's migration documentation actually misses this step, so hopefully this will save you some time recreating them all on your new Lync 2013 pool. Unfortunately for me I found this after the fact!

Migrate un-assinged numbers from Lync 2010 to Lync 2013

Following the Microsoft documentation for migrating between Lync 2010 and Lync 2013 I noticed there was nothing on how to migrate un-assigned numbers. I did a quick Google search but nothing came up so I wrote a PowerShell script that copies existing un-assigned numbers to a new Lync pool.

I have since found that the Lync 2013 Resource Kit includes a tool that migrates all un-assigned numbers from one pool to another.

While this renders my script nearly useless I thought I would still make it available to everyone. This could be useful for anyone that would prefer not to migrate all, and would rather copy then delete, or maybe modify the script to copy with an improved naming convention etc.

The script also includes a section that creates a new announcement and links it to a new un-assigned number range.

Get the script here.