Tuesday, May 24, 2016

Conferencing Modalities No Longer Function - MS16-065

Microsoft recently published a KB article related to a security bulletin MS16-065:

After you install the Microsoft .NET Framework Security Update MS16-065 on a Front End or Standard Edition server for Lync Server 2010, Lync Server 2013, or Skype for Business Server 2015, several conferencing modalities no longer function for internal users.

For a complete list of the .NET Framework updates that can cause this problem, see the 
Microsoft Security Bulletin MS16-065 - Important topic on the Microsoft TechNet website.

The following are known modalities affected by this issue:

·         Whiteboards
·         Uploading PowerPoint Presentations
·         Sharing Notes
·         Polls
·         Q&A

The error messages that users may receive when this problem occurs include the following:
·         We can’t connect to the server for presenting right now.
·         Network issues are keeping you from sharing notes and presenting whiteboards, polls and uploaded Pow…
·         An error occurred during the Skype Meeting.

I ran into this but it was not immediately apparent to which KB's this correlates to so I thought I would list out the ones that will cause this behavior and save someone else some time hunting:

Server 2008 R2:


Server 2012:


Server 2012 R2:




This also breaks the Lync Web App in Lync Server 2010 which is not documented in the KB at the time of this post. You will also need to add the following reg keys in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\System.Net.ServicePointManager.SchSendAuxRecord]:

DWORD Name: C:\Program Files\Microsoft Lync Server 2010\OCSMCU\Web Meeting Conferencing\MeetingMCUSvc.exe
DWORD Value: 0

DWORD Name: C:\Windows\System32\inetsrv\w3wp.exe
DWORD Value: 0

Then restart the RTCMEETINGMCU service as well as perform an IISReset.

Friday, May 6, 2016

Mobility - Topology Doesn't Have Required SIP Listening Port Setting

I had a client with a Lync 2010 deployment recently phone me and tell me that some users were unable to login to their mobile client when outside of the organization. The first thing I did was check the MCX service on the pool that the users were homed to. I was immediately greeted with Server Error in MCX application:

I attempted to recycle the external MCX application pool which typically fixed this issue, however it did not resolve it. I then started digging through the event logs on the server and noticed the following error Application Event ID 1309:

To which the following portion of the error specifically caught my eye:

Exception message: Topology doesn't have required sip listening port setting

I then ran:

Get-CsService -Identity WebServer:FQDNOFFEPOOL.com

Which showed that the value for McXSipExternalListeningPort was $null:

Then I ran the following to set the MCX External Listening and Primary Listening ports to the correct values:

Set-CsWebServer -McxSipExternalListeningPort 5087 -McxSipPrimaryListeningPort 5086 -Identity WebServer:FRONENDSERVERFQDN.com

Then running the get-csservice command again showed that the values were correct:

At which point I invoked CMS replication, verified it had completed replicating and then performed and IISReset and the mobility service was working once again: