Lync/SfB Server: Manually update the Edge Server Configuration

In a recent support case we had a case that the customer had some urgency to add a new Allowed Domain to be quickly pushed to his Skype for Business 2015 Edge Servers.

However, the replication wasn’t working:

Get-CsManagementStoreReplicationStatus | ft -AutoSize
https://technet.microsoft.com/en-us/library/gg399052.aspx

An easy solution to this is to perform a manual update and then fix the replication.

First, we need a copy of the latest configuration:

Export-CsConfiguration -FileName C:\UCLobby\SfB-Config_20170224.zip
https://technet.microsoft.com/en-us/library/gg398627.aspx

Now copy the file to each Edge Server and execute the following PowerShell cmdlet:

Import-CsConfiguration -FileName C:\UCLobby\SfBConfig_20170224.zip -LocalStore
https://technet.microsoft.com/en-us/library/gg398800.aspx

Note: In this case we need to specify the LocalStore switch so it updates the local database.

This is also possible if we run, on each Edge ServerStep 1 from the Skype for Business Server Deployment Wizard:

Please note that manually updated the Edge Server configuration probably won’t fix the replication issue:

These steps are valid to Lync Server 2010/2013 and Skype for Business Server 2015.

This should be only use as a quick workaround to update the local store while we fix the replication issue.

MSPL: How to monitor calls that are allowed/blocked by CallerIDBlock

While reviewing a comment on Missed call notification when the call is blocked by CallerIDBlock MSPL Script we realize that the calls blocked by the CallerIDBlock are hard to track.

An easy way to get an event for each blocked call is to use the Log function:

MSPL built-in functions > Log
https://msdn.microsoft.com/en-us/library/office/dn439170.aspx

The CallerIDBlock previous version (1.1) sends the log to the debug log, to view this log we need the APILogger.exe. For more details please check:

Deploying and Troubleshooting Lync Server 2010 MSPL Applications
https://blogs.technet.microsoft.com/nexthop/2012/03/14/deploying-and-troubleshooting-lync-server-2010-mspl-applications/

However, the MSPL Log function has the ability to send it to the Event Viewer.

Since we may not want to have the Event Viewer full of events, we added a new .config file:

CallerIDBlock.config

The file can be changed on-the-fly like the BlockedTelephoneNumbers.txt. This means that we don’t need to reload the script if we want to change the log setting.

For reference, the following code was change from:

To:

Here is an example if we configure the log setting to rejected:

We can also set it to both, then the CallerIDBlock will also log the allowed calls:

Note: We only recommend to the setting both for troubleshooting purposes.

The CallerIDBlock v1.2 can be downloaded from TechNet Gallery:

MSPL: Blocking Calls on Lync Server/Skype for Business 2015 Based on CallerID
https://gallery.technet.microsoft.com/MSPL-Blocking-Calls-on-e6d52de9