We are using both but with the intention that Skype goes away. Teams is relatively new to us so not many people are comfortable with it yet.
We have moved our lync over to sfb and getting good call quality in some areas has been a real @#$% to figure out. Using some newer netflow tools has helped to get the QOS under control but this sfb isn't all it was cracked up to be and I'm not sure it's really 100% anywhere at all but it is what we have now. Everyone thought this would save us money going this route but it's often worse than what we had before. I hope the new stuff is better than this... that's all I can say. Basically anything might be better than sfb.
Depending on the Solarwinds products you own, you should be able to set up QoE and SAM and WPM testing solutions that verify functionality and that detect and display problem areas.
Our MS rep told us this month that Skype is being replaced by Team. I'll be interested to see what the final product environment looks like.
Having used EOC, it wasn't the solution my organization needed, but I can see where it is appropriate for other organizations.
I realize you targeted another Thwackster, but thought you might like knowing my organization uses screen sharing very frequently. I use it about a dozen times any given day during meetings. It works perfectly for me internally. Getting it going between our internal clients and other businesses' clients across the Internet sometimes is a little flaky, but MS and our VAR have been helpful getting the kinks worked out. Often the issue is new ports or poorly-documented functionality requirements, resulting in changes needing to be made to our servers or firewalls.
We've not found anything we haven't been able to work out yet, but it took years to get to this state. I REALLY don't like the Internet/DMZ/Internal server/firewall rules required for the resilience and functionality we need. They are the most complex solutions I've ever implemented, and it's hard not to think they weren't kluged together without a great plan and top-notch design overview for efficiency.
Here's praying that Team will be easier to deploy and more reliable.
Interesting. Our Skype voice is reliable. Occasionally I'll see an individual workstation or headset that's problematic, one which consistently works OK for 30 minutes then drops. I haven't found the cause, but it may be associated with a specific model/version of PC or headset.
My PC & headset work well, and have since Day One. Better than Skype has.
That's too bad. Internal Skype has worked well for us, and we only occasionally ran into issues with SFB when using it across the Internet with other Skype customers--usually when trying to share screens.
It's gotten better, but still, anytime you've got something that wants QoS across the Internet to work well, it's a rotten design.
We were looking at going from Lync to Skype because it is the "next" thing, but Skype has some issues with various OS and Office versions we have deployed. It also kills the older chat clients, leaving people cut off if you can't complete the rollout all at once. If we go Teams we get the brand new experience (for better or worse) but can leave the old chat client there for people to use during the rollout. It is Teams for the whole company, and in a smaller scale IT has Slack in case the Microsoft stack fails.
From what I've read too Microsoft Teams is a very different product, although both fulfill some of the same requirements. We've had issues with Skype at some sites. Some was tied to misconfigured virtual firepower sensors which didn't have enough memory or cpu and adjustments helped there.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.