We are aware of an issue impacting Application Sharing on Lync Server 2013 and Skype for Business Server 2015 after applying the July 10, 2018 Security Patches for Windows operating systems. The Windows team has removed all bad packages from Windows Update and systems should no longer attempt to download an update which exposes this problem. New updates are being published through Windows Update and should be available for all operating systems by end of day July 17th.
The NextHop Team recommends that customers use Windows Update or update the catalogs on their own SUS servers to ensure the latest version of the update is available for installation on your Lync Server 2013 and Skype for Business Server 2015 Servers. Doing so will avoid any possible disruption to the ASMCU service which was impacted by the July 10th update.
Problem: Desktop or Application Sharing fails while in a meeting
The following events might be reported:
Log Name: Lync Server
Source: LS ApplicationSharing Conferencing Server
Event ID: 32011
Description: The Application Sharing Server has failed to create a conference because of an internal failure.
Log Name: Lync Server
Source: LS User Services
Event ID: 32026
Description: Conference rollover failed.
Updated packages are now available via the regular release channels: Windows Update, Catalogue, WSUS. These updates should be applied based upon the operating system version you are using with Lync Server 2013 or Skype for Business Server 2015. When using Windows Update to apply an update, you will need to initiate a manual request in the Windows UI to find and download updates.
For Windows 2016, the update will be applied as a replacement to the package delivered on July 10th. Customers running Skype for Business Server 2015 on Windows Server 2016 should ensure that the latest operating system updates are applied. These updates are available now and can be applied to a production system regardless of previous updates installed.
For operating systems prior to Windows 2016, the update will be applied as an additional update to the updates released on July 10th. This means you must apply the July 10th update and then may need to execute Windows Update again to receive the additional update to fully resolve the issue. The updates for these operating systems should be fully published to all geographies on Windows Update by end of day July 18th (PDT).
The table below outlines the impacted KB for each operating system and the associated KB which must be applied to resolve the issue. In the case where there are multiple updates listed for an operating system, only one of the updates should be required. The presence of two updates is indicative of whether a rollup or individual security update is being used to update the operating system.
|Operating System||Impacted Update||Update which must be applied|
|Windows Server 2016||KB 4338814||KB 4345418|
|Windows Server 2012R2||KB 4338824||KB 4345424|
|KB 4338815||KB 4338831|
|Windows Server 2012||KB 4338820||KB 4345425|
|KB 4338830||KB 4338816|
|Windows Server 2008R2 SP1||KB 4338823||KB 4345459|
|KB 4338818||KB 4338821|
|Windows Server 2008||KB 4295656||KB 4345397|