This “Take 2” at the November CU updates the Core and Web Components from 5.0.8308.974 to 5.0.8308.977, addressing this issue that snuck into the last update:
Kb3212869: Searching for a user on Lync Mobile returns no results after the November 2016 Cumulative Update for Lync Server 2013 is installed.
Just the above.
Nothing apparently.
Continue reading ‘Lync 2013 Server Update – December 2016’ »
I noted in my recent post about CU4 that I’d seen a recurrent 32270 error in my Lab after the install, and that it took another reboot to banish.
Roll forward a few weeks to my current customer deployment and I’ve been seeing recurrent PDP (Call Admission Control) errors… since the moment CU4 went on.
These are popping out roughly every 5 minutes:
Event 36023, LS Bandwidth Policy Service (Core) Disconnected from server. Machine FQDN server1.contoso.com (IP address: 10.10.10.10, TCP listening port: 448, Type: Intracluster) in pool myfepool.contoso.com Cause: If the specified server is removed from the topology or is currently draining or is stopped, this behavior is expected; otherwise, a network issue may have caused the disconnect. Resolution: If this behavior is unexpected, resolve the network issues between the two servers. Ensure that the service is listening on the specified port and FQDN.
Continue reading ‘PDP (CAC) Errors After Installing SfB 2015 CU4’ »
Our pre-Christmas update (KB3127976) takes the Office 2013-based Lync/SfB client from 15.0.4875.1001 to 15.0.4885.1000, and boy is it bursting with Christmas cheer!
This update fixes the following issues:
Continue reading ‘Lync 2013 / SfB 2015 Client Update – December 2016’ »
Guess what happens if you setup your CsHostingProvider incorrectly when deploying Skype for Business on-premises with Office 365 UM? Calls won’t make it to voicemail and a somewhat inaccurate error message from SfB might distract you from the fix.
Here’s the relevant part of the trace of a call that the Edge server is trying to send to O365 UM:
TL_ERROR(TF_DIAG) [sfbedgepool\contoso_svr00]0694.08E8::12/01/2016-09:47:52.868.00002010 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(833)) [3238978885] $$begin_record Severity: error Text: Split domain (cross-premise) routing is disabled Result-Code: 0xc3e93d8a SIPPROXY_E_EPROUTING_MSG_SPLIT_DOMAIN_DISABLED SIP-Start-Line: INVITE sip:greig@contoso.com;ms-organization=Contoso.onmicrosoft.com SIP/2.0 SIP-Call-ID: 0f5de291-6adb-457e-b12d-60b3a207748a SIP-CSeq: 253 INVITE Peer: exap.um.outlook.com:5061 Data: cause="Possible server configuration issue";summary="Shared address space routing (hosting of users on multiple deployments) is disabled";external-domain="contoso.com";external-type="domain-type-local";internal-domain="contoso.com";internal-type="domain-type-local" $$end_record
Continue reading ‘Shared Address Space Routing is Disabled’ »
As of ~8th December this update has been withdrawn by Microsoft:
“An issue was discovered in the Lync Server 2013 November 2016 Update (build 8308.974) that causes contact searches on mobile clients to return no results. Because of this issue, the November 2016 Update is no longer available for public download. The Skype for Business team is working on a fix that is scheduled to be delivered soon in a new update“.
15th December: … and fixed here.
This CU updates four components from 5.0.8308.956 & .965 to 5.0.8308.974.
Continue reading ‘Lync 2013 Server Update – November 2016’ »
It’s been a big year of content for Skype for Business Cumulative Updates, and CU4 doesn’t let us down.
This update takes the server from 6.0.9319.259 to 6.0.9319.272 & updates 8 components on my Front-End.
Continue reading ‘SfB 2015 Server Update CU4 – November 2016’ »
This week’s update (KB3127934) takes the Office 2013-based Lync/SfB client from 15.0.4867.1000 to 15.0.4875.1001.
This update fixes the following issues:
Nothing documented.
Continue reading ‘Lync 2013 / SfB 2015 Client Update – November 2016’ »
This week’s security update takes the Office 2013-based Lync/SfB client from 15.0.4859.1000 to 15.0.4867.1001. It’s listed as Critical as there’s the risk of remote code execution.
Kb3118348 “MS16-120: This security update resolves vulnerabilities in Microsoft Lync 2013 and Skype for Business. The vulnerabilities could allow remote code execution if a user opens a specially crafted document or visits a webpage that contains specially crafted embedded fonts.
To learn more about the vulnerabilities, see Microsoft Security Bulletin MS16-120. For a complete list of affected software, see Microsoft Knowledge Base article 3192884.”
As well as the critical issue above, this security update contains fixes for the following nonsecurity issues:
Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – October 2016’ »
At some point you’ll have performed enough upgrades or migrations to have encountered a DCOM error while trying to move users from one pool to another. It’s generally well-documented: Anthony, Michael, Paul, Michael or others might have shown you the light. It’s usually a permissions thing. You don’t have enough of them.
I was a little surprised when I encountered “it” this week, and burnt a little more time than I’d like to admit in search of the cause – but in my defence, I ended up on a tangent down a rabbit-hole chasing red herrings in search of a wild goose.
Annoyingly, my occurrence didn’t fit the more common mould. This one didn’t blame my Front-End, the load balancer or report a cryptic error code I could just Google:
This update takes Phone Edition from 4.0.7577.4487 to 4.0.7577.4512, primarily adding multiple emergency number support (new in CU3 of SfB 2015). In addition, an extra KB is slipped into the Polycom version:
Kb3194836 LCD display issues in Lync Phone Edition for Polycom CX500, Polycom CX600, and Polycom CX3000
“Issue 1 – After you apply the December 2015 cumulative update (KB3108721), the LCD background display changes from blue to green.
Issue 2 – The display contents are misaligned vertically. This causes the first character on the left to be removed.”
Download the relevant CAB files from here:
28th September 2016: This is the initial post.
-G.