Blog Archives

Carry on learning about Microsoft SOF!

SOF is continuously developed and enhanced by Microsoft. That’s why you should check out what changed to benefit of it by adopting SOF. On January 17th a webinar will take place which will update your knowledge on SOF. You can find the registration for the SOF January 2017 webinar >>here<< and a list on all training materials for >>here<<.

What adds and fixes Skype for Business Server 2015 cumulative update 4?

Microsoft released cumulative update (CU) 4  / Nov ’16 for Microsoft Skype for Business Server 2015. The CU adds the following new features:

  • Support of Multiple Emergency Numbers up to 100
  • Support of Location Based Routing for SfB mobile app clients
  • Support of E911 is now supported for SfB Mac 2016 client

Additionally, of course, it includes some fixes (see also Microsoft KB):

  • 3203706 Long silence when you dial into a meeting in Skype for Business Server 2015 that has name recording disabled
  • 3203153 You experience intermittent message delivery delay or failure in Skype for Business Server 2015 Persistent Chat rooms
  • 3203152 Lync Phone Edition telephones cannot put a call on hold if “Music on Hold” feature is disabled
  • 3203148 Front End server of Skype for Business Server 2015 crashes upon restart
  • 3203707 Japanese characters in the subject of a missed call notification message are garbled
  • 3203150 Calls to mobile clients fail if Skype for Business Server 2015 has advanced privacy mode enabled
  • 3203147 LS Storage Service event 32054 after you upgrade to Skype for Business from Lync 2013

For further details please see KB. Download the latest cumulative update (CU) >>here<<  and  read KB article >>here<<.

Minor changes to the Skype for Business user interfaces coming soon

The Skype for Business (CTR version, via O365 SFB Online) user interface is about to get some minor changes soon (depending on your deployment (current/deferred) on O365). How it  might look like you can see on the NextHop Blog >>here<<. It might be subject to change. I guess that these updates will follow afterwards for on premise users/client versions by the default update paths (Microsoft Update) which is not yet mentioned on the blog post.

%d bloggers like this: