Be careful using Lync Control Panel and Powershell together to manage Voice Routing

If you have an environment where you have multiple Lync administrators who manage voice routing, you may come across an issue where voice routes seemingly disappear.  This can happen when an administrator using the Lync Control Panel commits changes after another administrator adds voice routes using the Lync Command Shell.


The Lync Control Panel reads all the voice routing information into a Binary Large OBject (BLOB) when it starts up.  Say a Lync administrator then creates 100 new voice routes using the Lync Command Shell or another Lync Control Panel.  Now if the first administrator creates creates one voice route and commits the change, that BLOB will overwrite the changes made by the other admin because it has the later timestamp.  Ugh.  By the way, Microsoft says this expected behavior.

Let’s be careful out there.