Missed Call Notification – Not Working…..

Since November 2015 there has been issues with Missed Call Notification from Lync/S4B to Outlook.
There has been written many blogpost about this, but I will here try to summarize how to fix it – Until Microsoft release a permanent fix for the issue.

The following Windows Update’s are relevant for this issue.

I have been trying to solve this at several customers, but made a breaktrough today.

I have been searching for KB3101496 – Nothing to find!
Searched in Registry clearly shows that the patch is installed, but it’s not visible in Control Panel

Additional research pointet me in the direction of KB3114351.

Looking for KB3114351 in Control Panel showed that this patch was installed.
Did a Uninstall of this patch, with a following reboot.
After a reboot, the KB3101496 was again visible in Control Panel.
Did a uninstall of this patch as well, following with a reboot.

After a reboot, I checked the “About Skype for Business”, and the version was clearly changed.

About S4B

Did a test call, and VOILA – Missed Call Notification is restored !

In Short:

  • Unistall KB3114351
    • Reboot Computer
  • Unistall KB3101496
    • Reboot Computer

I hope this wil help others that has this problem, and that Microsoft will release a patch that fixes this forever…..


OneLiner: Move Lync users to another Lync pool, based on AD Group


The following PS OneLiner move users to another pool, based on AD Group.

Get-ADGroup “AD GroupName” | Get-ADGroupMember -Recursive | ForEach-Object {Move-CsUser $_.SamAccountName -MoveConferenceData -Target “New Lync Pool FQDN” -Confirm:$false}

This might come in handy, when you need to move users based on AD Groups.

Thanks to Joakim Erdal in Atea, for helping with command sequence..

Lync 2013 Mobility and IIS ARR

Since MS TMG server was withdrawn from the marked, IIS ARR has become the most common solution to publish Lync, Exchange and Sharepoint solutions.

There are good guides on how to configure IIS ARR and hos to publish Lync 2013.

One thing that I have been noticing, is that mobile users have been complaining about the following Message: “Your server configuration has changed. Please restart Lync”


After some searching on the topic, there was some info that told us to increase the Proxy Timeout value.
One very important info is:

You will need to increase the Proxy Timeout value for the Web External Publishing Rule.

I have had success with increasing the value to 960 Seconds.

Lync Server 2013 on Windows Server 2012 R2

As you all probably know, Lync Server 2013 is fully supported on Windows Server 2012 R2.
To gain Lync Server 2013 Support on Windows Server 2012 R2, Update Lync 2013 With the latest CU.

One very important change is to alter the TLS mechanism in Windows Server 2012 R2.
Windows Server 2012 R2 has changed how the TLS sessions are being cached, and this doesn’t work well with Lync 2013.
The following article describes a required registry modification:

As the article describes – “Lync Server 2013 is supported by Windows Server 2012 R2 when this registry workaround is performed.”

Continue to Lync – Happy Lync’ing 😉

IIS ARR as Reverse Proxy for Lync 2013

I have recently been trying to get IIS ARR to work as a reverse proxy for Lync 2013, and today I made a breakthrough 🙂

I have been following the NextHop article on how to set it up, but I didn’t manage to get it working 100% with all services – Office WebApps Server, LyncDiscover and Lync SimpleURL.

The issues I had was that I didn’t manage to get all services to respond correctly at the same time – And that must be one of the goals 🙂

After some “trial and error”, I came up with a URL ReWrite ruleset that worked.
The following URL Rewrite ruleset worked:

After I enabled the abowe ruleset Office WebApp Server, LyncDiscover and Lync SimpleURL’s gave the expected result.

Hope this helps anyone facing the same issues….

Lync 2010 SBA with RODC – How to get it work…

Lately I have been troubleshooing a Lync 2010 SBA installed in a Lync 2010 infrastructure.
The SBA was unstable, and the Lync Registrar service (Lync FrontEnd) didn’t always start.
Yes – Not Always !
Sometimes it started, and sometime is didn’t…..

My experience is that the following Active Directory Supportability statement don’t make much sence.

Support for Read-Only Domain Controllers

Lync Server 2010 supports Active Directory Domain Services (AD DS) deployments that include read-only domain controllers or read-only global catalog servers, as long as there are writable domain controllers available.

I asked Microsoft what this statement really ment, and I got the following reply:

We are aware of the statement, but not sure if it means “We work with an
RODC as long as we need to read and require a RWDC if we need to write” or “We
have no problem with RODC’s being there but we ignore them and can only work
with a normal DC”.

The reply really got me thinking, and didn’t bring calm to my chest !!

I created a MS Support ticket for this – As I need to get to the bottom of this…

While I was waiting for the reponse on the Support Ticket, I did some Wireshark trace on the SBA during the start of the Lync FrontEnd service.

The Active Directory in this case is designed with multiple AD Sites. The site where the SBA is placed only contains a RODC, but RWDC are available at other sites – And accessible from the SBA.

This is, as I see it, covered by the Active Directory Supportability!

During the analyse of Wireshark traces, I saw that the SBA was randomly selecting DC’s to talk to based on DNS lookup – This is as expected, and I didn’t find any issues with this.
What I did notice is that the RODC was never among the DC’s that is was initialy communication with.
This is also expected as the RODC only register sites spesfic info in DNS.
Further into the Wireshark trace, I saw the following:

  1. When the Lync FrontEnd service was able to start, the SBA was communicating with the RODC.
  2. When the Lync FrontEnd service didn’t start, the SBA did never communicate with the RODC.

This lead me back to Active Directory Sites and Services, and the following – How can I ensure that the SBA is communicating with the closest RWDC ?

I have previously been told that “Lync ignores the configuration in Active Directory Sites and Services, and is not AD Sites and Services Aware – As Exchange are.”

Well, I was really not sure about the AD Sites and Services part, so I did a change !

I added the IP address of Lync SBA into the closest AD Site with a RWDC.

I added the following in Subnets:
– IP: “Lync SBA IP/32”

I added the host IP address newly added in Subnets to the closest AD Site with a RWDC.

The SBA was restarted to make the server pick up that AD Sites and Services change.
Once restartet, I used the following command to verify the change: nltest /dsgetsite
The command verified that the server had changed AD Site, and is now belonging to a AD Site with RWDC’s

The Lync Management Shell was used, and the following command was issued: start-cswindowsservice

To my big surprise, the services started immidiately!
This lead to more questions that answers, and I’m currently working the MS Support Case to get the full story around Lync 2010/2013 supportability for RODC!

For now the SBA is running without issues, and I have not reverted it back to the original AD Site.
I am awaiting the final conclusion of the MS Support Ticket.

To be continued……