Happy new year! It’s barely January and we have a fresh update to the client – albeit a relatively small one, but with what looks like a doozie of a fix. Our December update took us to 15.0.4989.1000 and today Kb 4011638 nudges us up a few builds to 15.0.4997.1000. What’s Fixed This update fixes …
Continue reading ‘Lync 2013 / SfB 2015 Client Update – January 2018’ »
Our November update took us to 15.0.4981.1000 and today Kb 4011284 nudges us up a few builds to 15.0.4989.1000. What’s Fixed This update fixes the following issues: Kb 4054669 Can’t set the maximum number of contacts for a Skype for Business 2015 (Lync 2013) user Kb 4054671 “The requested operation was blocked by policy” error …
Continue reading ‘Lync 2013 / SfB 2015 Client Update – December 2017’ »
Our October Security update took us to 15.0.4971.1000 and today Kb 4011255 jumps us up 10 builds to 15.0.4981.1000. What’s Fixed This update fixes the following issues: Kb 4051054 Phone number instead of contact name is displayed for an Active Directory contact in Skype for Business 2015 (Lync 2013) Kb 4051055 A contacts group is …
Continue reading ‘Lync 2013 / SfB 2015 Client Update – November 2017’ »
This week’s Security Update seems to have touched a few items and of course the Office 2013-based Lync/SfB client is no exception. Our September update took us to 15.0.4963.1000 and today we jump to 15.0.4971.1000. Kb 4011179: This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens …
Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – October 2017’ »
It’s been a month since our last update to the Office 2013-based Lync/SfB client took us to 15.0.4953.1000. Today, a security update takes us to 15.0.4963.1000. Kb 4011107: This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about …
Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – September 2017’ »
It’s been 3 weeks since our last update to the Office 2013-based Lync/SfB client. Today we go from 15.0.4945.1000 to 15.0.4953.1000, aka Kb 4011046. What’s Fixed A handful of items are addressed in this update: Kb 4035431 “Call forwarding settings failed” dialog occurs after you sign out Skype for Business 2015 (Lync 2013) if RCC …
Continue reading ‘Lync 2013 / SfB 2015 Client Update – August 2017’ »
It’s been 3 weeks since our last update to the Office 2013-based Lync/SfB client. Today we go from 15.0.4933.1000 to … 15.0.4933.1000 – although the article (kb3213574) and other evidence – see below – confirms it’s 15.0.4945.1000. What’s Fixed This one contains a solo update: Kb 4032344 Low Internet Explorer performance when Skype for Business …
Continue reading ‘Lync 2013 / SfB 2015 Client Update – July 2017’ »
It’s been 3 months since our last security update to the Office 2013-based Lync/SfB client, and five weeks since this one. Today we go from 15.0.4927.1000 to 15.0.4933.1000. It addresses a risk of remote code execution. Kb 3191939: This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user …
Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – June 2017’ »
Our April update to the Office 2013-based Lync/SfB client (Kb 3178731) follows last month’s Security Update and takes us from 15.0.4911.1000 to 15.0.4919.1000. What’s Fixed This update fixes the following issues: Kb 4016107 Supports to join a meeting in Lync Web App when you don’t sign in to Skype for Business 2015 (Lync 2013) Kb …
Continue reading ‘Lync 2013 / SfB 2015 Client Update – April 2017’ »
By my reading it’s been 5 months since our last security update to the Office 2013-based Lync/SfB client, and this one takes us from 15.0.4903.1001 to 15.0.4911.1000. It’s listed as Critical as there’s the risk of remote code execution. Kb 4013075 “This security update resolves vulnerabilities in the Microsoft Graphics Component on Microsoft Windows, Microsoft …
Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – March 2017’ »