I beg to differ on this.. we use Skype for business and have heard nothing but complaints.
One personal beef I have with it is IM messages don't sync between devices. I start a chat with someone on my workstation then when I leave my desk and try to see it on my phone it's unavailable. Or same issue when switching between an RDP and local session.
It sucks... but you can still get to them if you have access to Outlook.
Newer versions do support server side logging to your Outlook mailbox too but it must be configured by the SfB and Exchange admins.
And that's just the issues we have trying to send text, don't get me started on the video and audio.
Seriously. On what planet is this ever acceptable. It seems like a sophomore joke.
What a piece of garbage.
We have SfB handling everything at work - including PSTN - and it works fabulously all the time.
You can blame Microsoft for the confusion since they renamed Lync to SfB in order to leech off the (non-enterprise) Skype brand. I wonder if they will rename SfB again should the "Skype" become more toxic.
From "robot voice" to poor sound quality to randomly dropped calls, to screen shares not working, have been a daily occurrence for me.
Settings revert a lot.
It's damn slow for remote sessions. Barely usable, really. File transfers don't work most of the time (and are slow).
Phone service? Call quality is really really bad.
The mobile app (Android at least) eats battery like candy, fails to send messages and is crashing a lot.
Lync/Skype for Business is a daily pain to suffer here.
The company I was working for had Skype for Business, and the video calls were such a disaster that people would secretly use Hangouts for every meeting that didn't have higher-ups participating.
It's like the SfB team still lives in the "everybody uses Windows" mindset of the 90's.
The only alternative on Linux is tel.red, which works, but only for an incredibly loose definition of the word "work". I've never used a buggier piece of software.
From what I'm told, the Skype for Business back-end is not enterprise-ready, by which I mean the back-end is written to assume that one user or one set of users has admin control over all the lines set up in the system. So one user or set of users remains in charge of all of the telephony details (role-based accounts, response groups, etc.). A proper enterprise-ready program allows the admin capabilities to be limited to groups of users and delegate functionality to those groups for certain lines. This arrangement lets you have multiple simultaneous admins edit different non-conflicting details (such as setup for two different response groups) simultaneously with no problems. This means large organizations with lots of somewhat independent groups have to set up work queues where someone in each group files a request for the Skype for Business admin(s) to work on requests (e.g. Please make 123-555-1234 a response group set up in the following way...). This slows down an admin in any of those groups considerably as those admins wait for their work requests to be fulfilled or further questions to be sent back in response.
Also some of the limits in Skype for Business strike me as silly: one of them concerns response groups (a Skype for Business term for how inbound calls are routed to a series of receptionists called "agents" in Skype for Business parlance). If you want a response group where some of the agents are allowed to decide whether they want to receive the calls (known as a "formal login" response group in Skype for Business parlance), and other users are required to receive the calls (an "informal login") you can't have both of these kinds of agents in the same response group. You have to set it up so that, say, the informal login agents get the call first and (if they don't take the call after a few seconds) the call is passed to the formal login agents.
From what I'm told, Skype for Business doesn't handle nested directory service groups properly when those groups contain sets of agents (which I understand Skype for Business treats as distribution lists when one uses Microsoft's directory server Active Directory). If that's so, this means that organizations that keep tidy directory service hierarchies can't reuse their groups efficiently.
We also frequently use it for video meetings on our Microsoft surface (or whatever that 80” touch screen thing is called) and it works like a charm.
Private or normal Skype is one of the worst apps I’ve tried in 2018 though.
I wonder if it’s because they tore out the peer-to-peer stuff that made Skype great in the oldendays and replaced it with azure.