You’ve heard the phrase, “an overabundance of choice?” We’ve reached that point for video conferencing solutions.
After I did the Video Interop Server post, I looked around a little more at video conferencing solutions. I found an enormous selection out there: Zoom, MegaMeeting, Join.me, Google Meet, MeetMonk, GoToMeeting, Vox.io, WebEx, WhatsApp, and so on…
We don’t need this many. Which compelled me to blog about the topic…because it can cause a serious problem with business-to-customer communication. Let me illustrate.
Too Many Video Conferencing Alternatives Clog Up Real Communication
In Ye Olden Conferencing Days, you used the phone lines. Conferences focused on audio first, and later, emailed files. Video came from an expensive equipment add-on, or not at all.
Now we’ve swung way off in the opposite direction. Video’s easier than audio to start up, on dozens of different platforms.
The market drives some of this, I know. Seems like we’re outpacing the market though, in a mad dash to find ‘the next video innovation’ before anyone else does. Problem is, this leaves a pile of mostly-functional, good-enough video solutions on the table from which businesses must pick.
Even worse: Some of these conferencing solutions won’t/can’t talk to each other!
For instance, Skype for Business and Zoom will integrate for video.
If you want to join a Skype Meeting with a GoToMeeting client? Got some bad news for you…
What Too Many Solutions Results in for the Video Conferencing World
In terms of ‘boon’ or ‘brambles,’ I think we’ve passed the boon stage. Video conferencing is ubiquitous; any business can run its meetings from virtually anywhere. That’s the good part.
The bad part is, we’re in a ‘Brambles’ stage now. Too many solutions, not enough interoperability. A thousand islands with not a bridge in sight.
This causes the major problem I referenced above: If your business uses one video conferencing solution, and your customer uses a different one, odds are high you won’t be able to use video in your communications!
“But Chris,” you might ask, “We have Zapier now! This isn’t a big deal anymore.”
True! We do have the Zapier connectors/”Zaps”, and I’m very glad for those. They have a good number for video calls.
However, this goes around the problem instead of solving it. An add-on can’t always match native functionality. Some internal networks won’t allow add-ons either.
Now, Zapier can’t halt the spread of video solutions, nor should they try. They’re responding to an existing market with their apps, and I wish them continued success.
Unfortunately, the brambles continue to grow.
Companies making the video solutions want to ‘own’ their customers’ communications. Interoperability, for whatever reason, doesn’t appear a high priority. Even though it could easily extend a solution’s long-term use.
Where does this go? I see two possible paths:
1. Continued Fragmentation. People keep their platforms. The existing software gains more users. A few may choose to inter-communicate, but mostly keep to their own systems. This preserves the frustrations of one business having conferences with another. We end up with a minefield of video solutions, each jealously guarding ‘their’ user base.
2. Slow Consolidation. People begin to move to similar platforms, for the sake of integrated communications with other companies (e.g. vendors). Some platforms die out, whether by choice (Microsoft retiring Skype for Business in favor of Teams) or by withering (users move away from the platform to another option).
If one of these seems more likely to you (or you have a third option), please comment below.
In the meantime, if a business doesn’t have a video conferencing solution & wants one, what should they choose?
2-Minute Guide on How to Pick a Video Conferencing Solution
This by-no-means-comprehensive guide should help you select a few video solutions to test. That way you’re not spending hours comparing features, fiddling with hardware, or stressing over connection issues.
Hello “Insiders!” I know I haven’t posted much lately. Went on a short vacation, and we’re now in the middle of 5 (yes, five!) website builds running at the same time
I’m also working on a couple big posts. The Time Lords willing, I’ll have them up before the end of the year.
In the meantime, let’s talk retirement.
Skype for Business (Online) Retiring in 2 Years
If you haven’t heard, MS will retire Skype for Business (Online) July 31, 2021. After that, it’s Teams all the way in Office 365.
No big surprise. We all knew it was coming. But what’s important for me to point out is that this retirement date only applies to the ONLINE version. The one on which Teams has chewed almost since its launch day.
That’s not the case for Skype for Business Server. Our good old on-prem version will stick around a while longer.
Skype4B Server Version Remains Supported Until 2025
Skype for Business Server 2015 mainstream support ends October 13, 2020. Extended support remains available until October 14, 2025.
Skype for Business Server 2019 will receive mainstream support until January 9, 2024. This is interesting though—its Extended support will also run until October 14, 2025.
Both versions of Skype for Business Server running out of support on the same date, a little more than 5 years hence. That’s still a good chunk of time to use the software.
Where does this leave you? A retirement date that far out, and only on one version, means nobody needs to run around in headless-chicken mode. Here’s some suggestions depending on your current Skype4B situation:
If you’re on Skype for Business Server 2019 or plan to migrate there soon – Keep doing what you’re doing. Let us know if you need help with setup.
Running Skype for Business Server 2015? Consider a move to Server 2019 next year. You’ll still have plenty of time with full support to get your money’s worth.
If you’re on Skype for Business Online & considering a move to Teams – Weigh the schedule in light of your workforce. If you have a large employee base, start planning now. If you’re in a smaller company, no need to panic. Run the move when you expect a slower time (does anyone have those anymore?).
You Don’t Have to Move off Skype for Business (Server) if You Don’t Want To
If it sounds like I’m still swinging in Skype for Business Server’s defense…well, I am. I like the platform for its power and its usability. It has a reliable history to boot. In fact, we still have one customer running Lync Server on-prem! (I think we’ve tried to move them off for what, 2 years now?)
What do you think of the Skype for Business Online retirement?
If your organization has decided to move off its Skype for Business Server deployment to Teams, you’ll hit an in-between period. A time when some users are on Skype4B, and some have moved to Teams.
Can they still communicate with one another during this period?
It’s possible…but it’ll take some extra configuration. Let’s talk about what you’ll need to do.
How to Make Skype for Business and Teams Talk to One Another
Before any Skype4B user can talk to a Teams user, the disparate systems have to talk to one another. Therefore, you’ll need to setup communications between your Skype for Business Server and your Teams tenant.
Essentially, any on-prem deployment must move to a Hybrid deployment. If you already run Skype4B in Hybrid mode, half the work’s already done. You can skip the Part 1 section below & move to Part 2.
But before you do that, let me call out a major communication limitation.
Limitations on Native Interop
Before we dive into the config work required, let me make this point. Users talking between Skype for Business and Teams will have ONLY TWO TOOLS to communicate:
That’s it. No video conference, no group chats, no emojis or file transfers. Not available.
If you have a long transition period, doing the config for this limited communication toolset may make sense. However, if you’re doing a fast cut-over (e.g., less than 4 months), then it doesn’t seem worth the time investment. I would recommend skipping it in that case.
Still here? Great! Let’s talk about making Teams and Skype4B talk.
Part 1: Setting Hybrid Mode with Azure AD Connect
If you’re not already familiar with Azure AD Connect, it’s basically a connection between your Skype for Business Server’s Active Directory and an Office 365 tenant. AD Connect synchronizes your users’ accounts in Active Directory with Azure Active Directory on O365, and vice versa.
This sets up the question of homing. If you created all of your users in your own on-prem Active Directory, then the users are ‘homed’ locally. If you have Teams users you created within your Office 365 tenant, those users are ‘homed’ in Azure Active Directory.
This is important for one reason: Interop between Teams and Skype for Business users only works if you home the user online.
Effectively, you’ll have to transfer all of your Skype for Business users up into the Teams O365 tenant. They’ll still use the on-prem server (in fact they won’t even notice the difference), but they have to live up there to talk to Teams users.
This post would run on forever if I detailed the whole AD Connect setup process. If you do need to set this up, please refer to these MS documentation pages:
Select the users, and click the Action dropdown menu. Choose Move selected users to Skype for Business Online.
In the wizard, click Next.
You may see an Office 365 prompt. Sign in using an administrative account. (Must end in “.onmicrosoft.com”!)
Click Next two more times to complete the move.
Now it’s time for Part 2.
Part 2: Change Users’ TeamsUpgrade Modes
Every Teams user has a mode assigned to it. Same with Skype4B users. The default mode is “Islands” – meant to signify the user as either on the Skype for Business ‘island’ or the Teams ‘island.’
Now, that won’t work if we want people talking between islands. Each & every user, on both sides, needs to have this mode changed for interop.
Other possible modes are:
TeamsOnly – For Teams users only
SfBOnly – For Skype4B users only
SfBWithTeamsCollabAndMeetings – This is called “Meetings First,” meant for using Teams’ meetings as an introduction to the platform.
SfBWithTeamsCollab** – This is the mode we want. It facilitates native interop.
In SfBWithTeamsCollab mode, users still use Skype for Business for IM, calls, and meetings. (If you used SfBWithTeamsCollabAndMeetings mode, your users would use Teams for meetings instead. Everything else is the same.)
As I understand, that’s pretty much it. Changing this mode allows Skype for Business users to chat with Teams users, after all the prerequisites are in place.
(By the way, this process also sets up the users to move completely to Teams. It doesn’t mean you have to move them, but you save yourself time this way.)
Teams, Can You Hear Us Now? Good!
I remember our team having some serious issues with Azure AD Connect, the first time we hybridized a Skype for Business Server. (In fairness, that was over 3 years ago. The tech and documentation have improved since then.)
Still, I urge caution if you need to deploy it in your existing on-prem environment. If possible, use a staging environment to test AD Connect setup first, so you’re comfortable. I believe that’s what we did.
What’s your status with Teams and/or Skype for Business? Using one or both? Comment below on your communication situation.
Sounds like an easy way to kick off a meeting, doesn’t it? If you’re using a RealPresence Trio, you have this functionality available.
Poly (formerly Polycom) has made several updates to their Trio conference systems since introduction. Not only have they helped with stability and audio/video clarity, they’d added third-party integrations. Lots of them.
In this post we’re talking about three of the latest—three that enhance a Skype Meeting’s usability. Alexa, AirPlay, and Zoom.
Alexa for Business Integration: “Alexa, please schedule a meeting for 10:30…”
The latest RealPresence Trio 8800 firmware includes an integration for Amazon’s Alexa for Business. You know what that does—adds voice commands into the Trio. To use it for business though, you’ll have to connect Alexa for Business to a “conferencing provider” of your choice: Cisco WebEx, BlueJeans…or Skype for Business.
Business Case for Alexa Integration: I see this as a primary convenience improvement. Too often we’ve seen customers start their Skype Meetings like this:
Team members enter conference room.
Someone taps a button on the Trio.
Loud dial tone as it connects, because someone forgot to turn down the volume after the last meeting.
Then a conversation somewhat like this happens:
“Did it connect?”
“I don’t know, I don’t hear anything.”
“Are they muted?”
“I think it failed. I’ll try again.”
[After 2-3 other attempts taking up to 10 minutes…]
“Oh! You can hear us now?”
“Yes, can you hear us okay?”
“Yes. All right, we can get started.”
Let’s avoid all that wasted time, shall we? Just ask Alexa to start your next meeting.
AirPlay Integration: Extra Screen Sharing Power
If you’re an Apple fan, you already know AirPlay. Good news for you—the Trio 8800 now lets you use it for AirPlay too!
This integration does one thing and one thing only: Screen mirroring. Once the Trio’s configured to activate its AirPlay integration, anyone in the meeting can share content on-the-fly.
We tested this one on-site too, using a MacBook Pro (it also works with iPhones and iPads). Worked flawlessly. Interestingly, I found that AirPlay content supersedes any Skype for Business shared content (a PowerPoint file, for instance). When the person sharing via AirPlay stops, the Skype for Business shared content reappears.
You configure AirPlay on the Trio the same way you do Alexa for Business: Adding a features.cfg file to the device’s Trio Web Interface. Parameters listed in the documentation below.
Business Case for AirPlay Integration: Participation boost! This integration makes it easy for attendees to share content off their phones or tablets. People don’t have to lug their computers into the meeting. Just a couple taps and you’re the one presenting.
Zoom Integration: Control a “Zoom Room” with Your Trio
Last year, we had a customer request a Trio 8800. We asked if they planned to use it with Skype for Business, as they were on Office 365 already. They said no. They’d just started using Zoom…and they wanted to use the Trio with it.
This took a little configuration finesse on our end. Thankfully, you don’t have to go through the same process. Zoom and Poly partnered to integrate the Zoom Rooms software into the Trio.
A “Zoom Room” is their version of a fully media-enabled conference room. It does require a computer, but otherwise gives the same functionality as a Skype for Business-enabled conference room: audio/video conferencing, screen sharing, and a simple control system.
The integration allows you to use a Trio as a controller in a Zoom Room. In other words, you’d use the Trio much as you would in a Skype for Business setup. Start/end meetings, use its speakers, & control the screen sharing.
NOTE: If you bought a Trio 8800 separately from the Zoom Rooms hardware, you will need to provision it. See the setup notes posted below for the steps.
We did these new integration tests on the very same Trio. It’s still in our conference room, subjected to all sorts of firmware mangling. (It’s all in the name of testing, honest.) Which means if these integrations work on our battle-worn Trio 8800, they will work on your latest-model Trio 8800 too.
How do you use your RealPresence Trio? Leave a comment, or message me to share.
Entry #6 into the “How it Fits” series is…the Video Interop Server, or VIS!
Of all the Server Roles, I have the least experience with this one. We’ve only done one install of it, for a customer with an older Cisco conferencing setup. It did the job, and made the customer happy.
Newly-introduced in Skype for Business Server 2015, VIS made a bit of a splash on debut. Because it leveraged existing video conferencing hardware, you didn’t need to spend extra on new hardware when deploying Skype for Business. You could reuse what’s already in place. We all love cost-saving!
This post, like the other “How it Fits” series, will give an overarching take on the Video Interop Server’s function and use case. It has not markedly changed since introduction, and ships with both Skype for Business Server 2015 and 2019. You may never need to use one…but if you do, you’ll be glad it’s there!
The Video Interop Server’s Primary Role
The VIS acts as an intermediary for Skype for Business and legacy Video Teleconferencing Systems (VTCs). These are older conferencing room systems businesses have used for years. Cisco, Polycom, and several other brands make VTCs. It appears Microsoft meant the VIS to work primarily with Cisco TelePresence VTCs.
By creating the server, Microsoft helped many companies with older conferencing hardware extend its useful life. Remember all the money you sank into that conferencing room’s video setup? Big screen, high-quality (for the time) cameras, expensive phone/speaker equipment, wiring? With a VIS, you don’t have to scrap all of that for new hardware. The VIS allows those video systems to connect to & join Skype Meetings.
You can also use VIS for peer-to-peer calls on the same hardware, with some limitations.
VIS is primarily designed to interoperate with the Cisco Unified Communications Manager (CUCM) and its connecting endpoints. I’ve seen mentions of people connecting it to non-Cisco conferencing systems, but I don’t have a concrete example. (Do you? Please comment with the details!)
Main Components of the VIS
1. Video Converter. A VIS is almost single-purpose: it converts video streams between the formats used by Skype for Business and legacy VTCs.
Let me explain a little more about how this works. Skype for Business uses the H.264 video codec. However, it also maintains support for the RTVideo codec for interoperability. This allows legacy conferencing systems to transmit their video data into the system. But the Skype4B servers may not fully understand the legacy video transmissions.
Which is why we have Video Interop. It performs the conversion & translation functions necessary to make everyone see & talk to one another.
As you can imagine, this takes a little more bandwidth. When implementing Video Interop, it’s wise to make sure you have a comfortable amount of bandwidth available. Otherwise the VIS will bump streams down to a lower resolution, causing poor video quality & even attendee drops.
2.SIP Trunk. Not necessarily a Server Role, but the VIS needs a video SIP trunk to communicate between itself and a legacy VTC.
Other Servers a VIS Communicates With
Front End Server. VIS talks directly to the Front End Server. Please note, you cannot collocate VIS with a Front End Server; it must have its own server/pool.
Edge Server. Since VIS must venture outside of the internal network for some third-party VTCs, it needs to associate with an Edge Server/Edge Pool. This is set up within Topology Builder.
How a Video Interop Server Works in a Hybrid Environment
You implement the VIS as a standalone server, in on-prem topologies. As such, this is the only way it will work in a hybrid deployment. Microsoft may have reasoned that since larger companies are more likely to use (and want to keep) Cisco legacy VTCs, they’re opting for on-prem deployments anyway.
The VIS in Skype for Business Server 2019 & Teams
Skype for Business Server 2019 does include Video Interop Server. I expect that future Cumulative Updates (CUs) for Server 2019 will expand its interoperability to more legacy video platforms.
Teams however is a different story. Since it’s all cloud-based, and Microsoft built VIS as an on-prem Server Role only, we don’t have such an option for Teams users. Nor will we. Those companies with legacy VTCs still on-site are out of luck.
Or are they? You do have one option…a third-party Cloud Video Interop service. An add-on service that performs the same function as VIS, made by a Microsoft Partner like Polycom or BlueJeans. If you invested thousands into a now-older Cisco conferencing setup, and are looking at Teams, go with this option.
VIS Extends the Life of Your Video Conferencing Hardware
Personally, creating an entire Server Role to handle one use case seemed like overkill to me. At first.
However, since then I’ve come to understand the reasoning behind VIS. Given how bandwidth-intensive video is—not to mention how demanding older teleconferencing systems can be!—it does make sense to include a gateway devoted to it. In so doing you also make said hardware last longer, saving on costs. Which makes Management happy!
Hey Skype for Business/Teams/ChatOps fans! Just wanted to do a quick post about a new Workplace Messaging Report. Mio released it after surveying over 200 companies on their messaging apps/ChatOps trends & plans. I saw it posted on Twitter, read through, retweeted a few times, and then raced over here to share it.
Do you enjoy customizing everything about your desk? Your phone screen, posters, funny desktop gadgets…
Why not the same with your software? Judging by our search traffic, many of you would like to see more about customization for Skype for Business. I collected a whole group of search queries about customizing the Skype for Business client. So that’s what this post is about.
Again, these questions came from this blog’s Google Search Console data. Which means you – yes, you right there – may have submitted the question. Thanks!
Now, you’re no doubt curious. Let’s get to the answering part.
Group Post 2: Customization Questions & Answers
“How to Change Skype for Business Ringtone”
Some of us are OK with a phone’s default ringtone. Others will change it the second they can. For those of you in the latter crowd, it’s very easy to change your Skype for Business call ringtone.
In the Skype for Business client (I’m using the desktop version here), open up the Options window by clicking the gear at top right. Click “Ringtones and Sounds” in the window’s left-side menu.
You have four options for ringtone changes in the list: Your work number (the main line), your team/group calls, delegate calls, and Response Group calls. Chances are you’re just looking to change your work number’s ringtone. Click that line, and you’ll receive several choices. Click each one to hear it. If one of those sounds good to you, click OK at the bottom.
What if you don’t like any of them? Can you use a custom ringtone? You sure can. To set a custom ringtone (must be a .WAV file), click the “Sound Settings” button in this window. The Windows Sounds window will open.
Scroll down in the Sound’s “Program Events” box until you see the Skype for Business section. Click “Incoming Call” (see screenshot, in blue). With that selected, open the dropdown menu below it (in red).
These are available sounds within Windows. If you have your own sound file, click the “Browse” button to select it. Make sure it’s in a location where it won’t go anywhere, and that’s it in .WAV format. Click OK, and you have a custom ringtone!
(Note: This will only change the ringtone for you, on this one device.)
Mobile Skype for Business users – You can change your phone’s overall ringtone in your Settings app. The Skype for Business app should take its ringtone from there.
“How to Change Skype for Business Theme”
Do the normal white-on-gray app layouts hurt your eyes? Some of us have visual impairments that make normal layout colors uncomfortable. Or perhaps you just like the ‘dark theme’ option (right there with you). Either way, a darker theme would appease your eyes & make work easier.
Unfortunately, Skype for Business doesn’t have a theme selector available in its clients. We’re stuck on this one. But what you can do is voice your opinion. Here’s a suggestion thread on SkypeFeedback.com, requesting a ‘dark mode’ theme for Skype for Business clients.
“How to test Skype for Business connectivity”
If you’ve ever been in a webinar, then you know about the “Test Your Connection” process. Just before you join the webinar, you can click on a link to run a quick test of your speakers, microphone, video…and Internet connection.
Most of the time your connection’s fine. On the rare occasions it’s not though, you’re glad for the tester!
What if you want to do that for an on-prem Skype for Business Server? There are two easy ways to do that:
The most relevant one is the Skype for Business Server Remote Connectivity Test. Enter your Skype4B account login, domain/username, and password. Verify your request and click “Perform Test.” That’s it.
Start up a Skype Meeting – with yourself!
Since the Skype Meeting’s communicating with the server to & from your client, it gives you a basic idea of connectivity. You can also rope a co-worker or two in. Bonus if said co-workers are in different offices.
This way you’re illustrating the ‘actual’ Meeting experience, without bothering customers. If you have a connectivity issue, it appears as you converse. Before any customers see it and think, “Well, this Skype thing’s not too stable…”
“Where do Skype for Business recordings go?”
It’s possible to record your video calls and Skype Meetings directly within Skype for Business! Useful for webinar recordings, documentation, and preservation of communications (e.g. for regulatory compliance).
To activate a recording in a Skype Meeting:
Launch the Skype Meeting.
In the lower right corner, click the More Options button (the one with three dots).
Click “Start Recording.”
When you’re done with the meeting, return to More Options and click “Stop Recording.”
Wait a moment. Depending on how long the meeting went, it may take Skype for Business a minute or two to save the recording file.
To activate a recording in a video call: Follow the same steps as above. Both recording types will save in MP4 format.
You can always refer to past recordings via the Recording Manager. This is under “Tools” in the main Skype for Business client.
The default location for storing these recordings is the user’s Videos > Lync Recordings folder. You can change this location, as well as the recording quality. See the next answer for steps.
“Can you change where Skype for Business recordings go?”
Of course! It’s an option you can set in your client. Go to Tools > Options, and click the Recordings options in the left-side menu. Click the “Browse” button next to the current folder, and navigate to the folder you want to use. I set mine to my Downloads folder.
The Skype4B administrator may change the default for all users, and/or disable users’ ability to change the default recordings location.
Skype for Business is OK on Customization
Customization isn’t as high of a priority for Skype for Business as privacy. Which does make sense; the content of your messages needs protection. If that means less attention paid to style, so be it.
That doesn’t mean you can’t do anything with it. Hopefully these answers provide a little more “fun” to your daily chats & meetings.
(I didn’t talk about emojis for one reason – you already know where those are!)
Do you have a question on Skype for Business to which you’ve never found an answer? Send it in! Let’s see what we can find out for you.
I’ve always meant this blog to serve as a resource for Skype for Business use. Both for users and for administrators…leaning a bit more toward administrators. Not today though. Today I’m leaning over to the user side, to answer common questions about privacy in Skype for Business.
Where did I find these questions? You asked them. Yes, you, right there.
Like I do (at least) monthly, I went through Google Search Console to examine this blog’s data. In the Queries data, I found a large group of fully-formed questions. People asking simple, direct questions about Skype for Business.
Questions everyone from basic users to admins might have. Questions that I can answer in just a few lines. Thus they don’t need their own posts…but they do need answering.
Solution: Group them together! Write up a resource post where you can find several answers in one spot. Which brings us here. This is the first group of questions I found. They all have one thing in common: Privacy.
Group Post 1: Privacy Questions & Answers
These are the 5 most-asked privacy questions on Skype for Business. My answers come from our own experiences deploying & supporting hybrid and on-prem Skype for Business Servers.
“Are Skype for Business calls recorded?”
Only if you record them. The Monitoring Server does collect data on call connections & quality, but not their contents.
“Are Skype for Business conversations private?”
Yes. Skype for Business encrypts the pipe between users’ conversations, as well as from each client to the Skype for Business Server.
However, you can potentially have eavesdroppers (though it’s very unlikely). It depends on your deployment type.
On-Prem: Your Server Administrator can view conversations.
Hybrid/Cloud: Microsoft CAN technically view conversations, though they’ve stated that they don’t.
One important caveat: Conversations between Skype for Business users and Skype-C users have one extra privacy risk. Even if you control privacy on the Skype for Business side, you don’t control the Skype-C side’s privacy. I documented this back in 2016: The Privacy Risks in Skype for Business-to-Skype Conversations.
“Are Skype for Business conversations recorded?”
Since this one mentioned ‘conversations’ and not ‘calls’ I’ll split up the answer.
VOICE: Only if you leave a voicemail. Otherwise, see above question on recording calls.
TEXT/INSTANT MESSAGING: These conversations are saved in your Conversation History, as well as the Conversation History of all parties involved.
“Recorded” in the sense of the NSA collecting data on you? They apparently like to do that to everyone. Good news is, with proper security for an on-prem deployment, the chances of your conversations showing up in an NSA vault go down to pretty much zero.
“Does Skype for Business track you?”
If you are logged into the Skype4B client on your devices, yes…to a certain degree. Skype4B does track your activity within its infrastructure.
The client tracks your Presence status from the last active client.
The client tracks your location, also by last active client.
There is also the Monitoring Server. This tracks users’ activity, call details, and system health.
A Monitoring Server is not required; admins can choose not to install it. But most would go ahead & do so, as it provides extremely useful data on communications stability & troubleshooting. We recommend Monitoring for all deployments.
If you’re worried about an Orwellian-esque sensor constantly following your movements…you’re thinking of Apple. Skype for Business doesn’t do that. Like any good communications software, it responds when someone triggers a conversation.
“How does Skype for Business know when you are away?”
Device activity! Skype4B clients monitor the last activity performed on the last device you used while logged in.
They look for mouse movements or keyboard presses on desktops, and taps/swipes on phones. After a certain interval (set by your Server Administrator) without any such activity, Skype for Business assumes you are ‘away from desk’ and changes your status to Away.
Server Administrators can set this ‘Away Interval’ anywhere from 5 minutes to 360 minutes, site-wide. We generally keep it to 5 minutes or 10 minutes for customer deployments.
“Does Teams record your calls/conversations?”
This question came up as well. Since people have just as much right to question Teams’ privacy controls as they do Skype for Business, I included it.
Teams does log your chat conversations. Since Teams is primarily text-based, and since most conversations take place in channels, it makes sense to keep records of those chats. You as the participant may access the logs. Teams Administrators within your O365 tenant can as well. Microsoft doesn’t scan or collect them either.
All in all, Skype for Business maintains a solid reputation for protecting your privacy. We’ve deployed it for thousands of users now, and received zero tickets on data leaks or breaches. I asked two of our customers if they thought their Skype for Business deployments risked their privacy. Both said no, not at all.
I take that as a vote of confidence. Hopefully you can too.
Thanks for reading! The next “Group Post” will discuss how to change several common Skype for Business elements. Join us back here next time for those.
3 Ways to Keep Voicemail & Auto Attendant when Upgrading to Skype for Business 2019
Those of us who use voicemail in Skype for Business face a quandary.
We did get a new Skype for Business Server, as well as a new Exchange Server. But we’re missing one component: the Unified Messaging service in Exchange Server 2013/2016. Exchange Server 2019 will NOT have Unified Messaging.
The sysadmins reading this already know what that means. They can feel it as a sudden clench in the chest. Skype for Business’ voicemail needs Unified Messaging. Without it you’ll end up upgrading a part of the office’s phone system away!
Two, actually…the Auto Attendant’s gone too. No more, “Press 1 for Customer Service. Press 2 for Sales…”
What do we do? If your offices use Skype for Business on-prem and employ Unified Messaging for voicemail and/or Auto Attendant, it’s time for some alternative thinking.
Fortunately, we’re all IT pros. We’re good at creative solutions. That’s what we’ll have to do here, to preserve Unified Messaging.
Right now we have 3 ‘preservation’ options, each with different levels of expense & usable time. Time to run some comparisons!
Voicemail/AA Preservation 1: Keep Your Exchange 2013/2016 Server On-Prem
This is a way to preserve UM within the Microsoft infrastructure. It involves juggling between different versions of Skype4B and Exchange. Essentially, you upgrade your Skype for Business Server to 2019…but not your Exchange Server. It stays at its current version. Accounts and configuration intact.
You’ll need to undertake several processes. Changing the UM dial plan, voice policies, etc. It all depends on your existing Exchange Server’s configuration. Here are resources to help you:
Important! If you take this route, make sure to configure the new Skype for Business Server as a partner application to your Exchange Server, and vice versa. Even if Exchange had partner app configuration before, I’d advise re-running it.
VERDICT: The most direct solution. With a critical flaw – it has a lifespan. Exchange 2016 will run out of mainstream support in October 2020. Extended Support runs until October 2025, which lets you stretch things more. You’re still faced with the potential of higher support costs the longer you go.
This is the option I prefer, frankly. Even with the lifespan boundary. You retain the most control, and it requires almost no new hardware.
If you don’t run Exchange 2016 already, or the lifespan boundary doesn’t work, then we have Option 2.
Voicemail/AA Preservation 2: Switch to Cloud Voicemail/Cloud Auto Attendant (Hybrid Deployment)
Cloud Voicemail is Microsoft’s response to yanking Unified Messaging out of Exchange. It’s (predictably) a part of Office 365, and requires a tenant to operate. Same with Auto Attendant—now it’s a cloud service too.
Setting up Cloud Voicemail isn’t that complicated. You must have hybrid connectivity enabled first, of course. I’d even recommend doing this a week in advance, so you can test & verify successful connectivity.
To configure Cloud Voicemail, you’ll need:
Your Office 365 tenant account login/password
The domain assigned to your tenant
Administrative access to your Skype for Business Front End and Edge Servers
Cloud Voicemail is not a 100% drop-in replacement for Unified Messaging though. According to ExPTA.com, Cloud Voicemail doesn’t include Play on Phone, call answering rules, text notification, or Outlook Voice Access. Doesn’t mean those won’t show up down the line, but for now, Cloud Voicemail’s sticking to the basics.
VERDICT: If you want to move to Exchange Server 2019, you’ll have to switch either to Cloud Voicemail or Option 3. Exchange 2019 doesn’t have the Unified Messaging service. This might help to gradually introduce Office 365 tools to the company. You also get Teams this way, which could provide a transition path for all staff…if you’re going that way.
Voicemail/AA Preservation 3: Integrate a Third-Party Voicemail/Auto Attendant Service with Skype for Business
This option essentially abandons using Exchange Online, Cloud Voicemail, and Office 365. Instead, you add in a third-party service to provide your users voicemail and/or an Auto Attendant feature.
We have a curious reversal on this track. It’s relatively easy to add in Auto Attendant…several third-party providers exist to do just that.
As far as I know, we haven’t worked with either of these solutions directly in a Skype for Business topology. If you have, please share your thoughts in the comments.
VERDICT: If you do want to upgrade to Exchange Server 2019, but don’t want anything to do with Office 365, this is your only option to preserve voicemail and/or Auto Attendant.
Preserving Unified Messaging: Unfortunate, but Necessary.
I can understand why Microsoft chose to remove Unified Messaging. It falls within their “cloud first” mission, consolidating things like voicemail & Auto Attendant into the Azure/O365 ecosystem. (Must have taken a LOT of coding…)
That said, those of us who appreciate on-prem control now have another instance of “technical gymnastics.” Trying to find a new solution for a resurgent problem.
Unless of course you want to drop Unified Messaging? I can’t think of a scenario when a business would voluntarily drop its voicemail/Auto Attendant…but that doesn’t mean it doesn’t exist. Perhaps you’re considering the idea?
In terms of how these processes shake out…we do have a full Skype for Business Server 2019 installation planned this year. We’ll most likely use Preservation 1, maintaining our current Exchange 2016 server. (Exchange 2019 will have a separate test.) I will document EVERYthing as we go, and produce plenty of blog posts from that.
If you’re planning a Skype4B 2019 upgrade, which Unified Messaging preservation method will you use?
It’s time to add chat to your communications tools. Which chat platform should you adopt? Teams? Slack? Something else?
First off, take a breath. Your search has brought you to the right place. In this post we’ll go over the available chat platforms, discuss the pros & cons of each, and identify the criteria for you selecting your best option.
Chances are you’re looking at chat platforms for one of these reasons:
Users are clamoring for a chat option
Need to get users off Skype (Consumer)
Time to replace less-advanced communications platforms
Worried about a data breach through user behavior (this one’s not limited to chat, of course)
Unless there’s another reason – if so, please share it in the comments!
Let’s address all of these reasons in one handy guide. I’ve put anchor links below for quick reference, but I recommend you read the entire guide. Only takes about 8 minutes.
First, before anything else, you’ll want to identify what you need from the chat platform. What it must do for you from an IT standpoint, and what it must do for the business’ communications.
Consider factors like these when identifying. These have all come from our own customers’ initial discussions about chat and/or voice offerings. Some contradict others, so make sure to decide which is most important.
Easy transition from another communications system
Easy adoption of a brand-new platform
Omni-device (apps for every major OS)
Focused on Windows devices
Security is paramount for all devices & data
Security should not get in the way of ease of use
Works within an existing cloud subscription we have (e.g. Office 365)
Stands alone, needs no additional subscriptions or hardware
Works in the cloud
Has a monthly fee, flat or per-user
Pay up front, no monthly fees
Has voice and video options built-in
Video is equally important to chat
Voice is equally important to chat
I’ll refer back to this list several times, so keep it in mind. Next up, we must narrow our focus. This is for business use; therefore, we need to look at only business chat offerings.
Focusing on Business Chat Offerings
This guide will focus on chat platforms where chat is the centerpiece product.
That’s why I won’t look at platforms like Fuze and Zoom here. I’m also leaving off consumer-targeted chat platforms, like Discord and Telegram.
No knock against any of these, of course. I like Telegram, but I don’t use it for business. For purposes of this guide, I’m focusing on chat platforms targeted for business use.
In order to qualify, they must meet these criteria:
Meant for business users
Good support options available
Work within existing office environments
That leaves us with a handful of platforms. Each very similar to one another. All crazy usable. All with at least decent security, mobile apps, and lots of integrations. So how do you choose?
Let’s start by identifying the elements you should consider.
ChatOps Adoption – Elements to Consider
Will your users accept a chat platform? Will your current IT infrastructure play nice with one? What about security? These are all important elements to consider…long before you trial anything.
Will your users adopt?
A chat platform’s useless if nobody wants to use it. You may have fielded requests for chat already…if so, you’re good! If not, you’ll want to check their thoughts.
The solution? Survey your users. A simple email, or SurveyMonkey form. I’ve written out a few questions you can use in it.
If the company adopted a new chat platform, would you use it to communicate with co-workers?
How do you think chat would help you in your daily routine?
Do our customers use a chat platform in their work? If so, which?
If users vote the idea down, well, less work for you! But if you get a positive response, and these days I expect you will, then you can move to the next element. Compatibility.
Which chat platforms work with your current infrastructure?
Most office networks will work with a cloud-based platform like Slack or Teams as-is. Check your max bandwidth though—you might overtax a smaller pipe.
An on-prem chat offfering will obviously require hardware & network changes. That’s a trade-off you’ll have to make, depending on budget & company policy.
Which features are necessary?
While most chat platforms have the same feature sets, they’re not all equal. For instance, Teams still doesn’t support private channels. If that’s something your users want, then Teams is (for now) off the list.
Identify the features your users would like the most, either through the survey or through conversations. These features come up frequently among our customers:
Talking with customers on an existing platform
Use chat app on phones (or blocking chat apps on phones)
Web-based only, app-based only, or both?
Voice call function built into chat
Integration with specific third-party services already in use
Pay Attention to Security
If I’d written this guide in 2016, this would be the biggest section. Think about it%—every chat user types out company IP in text format, every day, in a cloud-based medium that’s saved someplace you don’t control.
Fortunately for all of us, security around ChatOps has improved immensely since then. Every platform we’ll examine here has documented their security protections. Here are a few reference URLs to help your case-building:
That said, ChatOps adoption still requires some security updates on your network’s end. Pay attention to these adoption aspects as potential security risks:
MOBILE APPS—Handy, but they can leave chat conversations susceptible to data theft. Chats are not audio clips; they’re whole conversations in text form. Someone steals your phone, they could have a ton of your IP in their hands. As such, use 2FA on mobile apps, or limit who can use the mobile app at all.
GUEST ACCESS—Important to keep guest access regulated. Teams’ Office 365 account requirement helps with this, but also throws up a roadblock for ease of use. Slack is a little better with guest access, limiting adds with admin controls.
THIRD-PARTY INTEGRATIONS—If your users connect a third-party service with poor security, it can create a data leak. Make it clear that IT needs to know about integrations, and vet them first.
PRIVACY—Who owns the data? Most platforms will unequivocally say, “You do.” Still helps to check their TOS. Especially if you have GDPR to consider.
If you choose a cloud-based chat platform, make sure to incorporate its logs into your backups. You may not think you’d need to back up chat conversations when they’re already in the cloud. However, if you’re using chat for work, remember…those conversations contain important information!
With a backup running, you’ve made sure you know where chat logs are stored (and you can retrieve them). I did a post on this for the SpinSucks Blog recently.
Open the link and then come back. We have a lot more to cover!
Now that we have a clearer sense of what to watch for, let’s break out the best business chat platforms, one by one, and weigh them.
The Major Chat Platform Options
There are four ‘major’ chat platforms in use today. The most popular, the one you hear about all the time, is Slack.
With good reason. Slack is a titan of chat—near-infinitely flexible, stable as you can get, friendly with just about every device out there, and designed to support business users. Some businesses run their whole operation through Slack. The company supporting it is stable and plans to go public soon.
Choose Slack if:
Ease of use is paramount
Your company do not already have an Office 365 tenant subscription
Teams’ recent growth indicates that people who are new to business chat go for it the most. Not surprising either; it has a short learning curve, Microsoft’s weight behind it, and free options. It isn’t perfect; Teams loses to Slack on a few points (Linux clients, adaptability). However, its incorporation of Skype for Business voice & video tools enhance its appeal.
Choose Teams if:
Your company has an Office 365 tenant subscription, with accounts for the majority of users
You primarily use Windows devices
You want an easy transition from an existing communications system
The only on-prem offering in the majors. For security-conscious mid-markets and enterprises, this is THE chat platform of choice. It requires more up-front investment, but a search of this blog alone will tell you how much communications power Skype for Business provides.
(You might wonder why this is on here, when I made chat the centerpiece. Many would consider Skype for Business Server a voice product, with chat & conferencing added. Be that as it may, we use the IM tool more than any other in our office. So do most of our customers. Besides, this IS the Skype for Business Insider Blog. So it’s included.)
Choose Skype for Business Server if:
Data/IP security concerns are high
You must meet regulatory compliance such as GDPR or SOX 404
You have 150+ users
You previously used HipChat Data Center and need to switch
Rounding out the major platforms is Google Hangouts Chat. I find this offering a little TOO simplistic, and Google’s privacy shenanigans may dent Hangouts’ appeal. But it’s still popular, cheap, and sports a similar integration level to other G-Suite offerings as Teams.
Choose Hangouts if:
You already use G-Suite for your company’s email
You do not have an Office 365 tenant subscription
You have users who like using Skype Consumer in the office (Hangouts is similar, making a transition easier to accept)
The Challengers/Alternative Chat Platforms
Maybe the major platforms don’t appeal to you for whatever reason. You’re not a Microsoft/Google fan, or you want to test out several options before making a decision. I love testing myself, so if you’re in the latter camp, welcome! Here are a few ‘challenger’ chat platforms to whet your appetite.
These are chat platforms not as popular as the above options, but still chat-focused and business-oriented. I haven’t done official reviews of these yet; as such, please take the following information as general advice.
First up is Twist. Made by a team already known for a popular to-do app, Twist takes a one-topic-per-thread approach to chat. It focuses on simplicity, sticking to chat as its core and leaving the rest to third-party integrations. Not many of those yet, but they already put in a Zapier integration…clever.
Choose Twist if:
You haven’t used chat in the office yet & want to try it out
You’ve already tried one of the major platforms, and users complain of confusion or overwhelm
You need to keep price low (their Unlimited tier only costs $5/month per user)
Our sole on-prem Challenger. This one’s not trying to compete with Skype for Business though…they’re competing with Slack. Right up to compatibility with Slack’s third-party integrations. It’s probably one of the most extensive open-source projects I’ve come across.
This platform has teeth. A hefty feature set, good documentation, and an unapologetic targeting toward the DevOps community. That may make it a little more technical than some businesses want. Even so, it’s worth a look.
Choose Mattermost if:
You’d like an on-prem offering, but can’t/don’t want to pay for Skype for Business Server
You like to tinker with the tech
You support open-source projects
You’re a tech company and want a chat platform that can keep up
You previously used HipChat Data Center and don’t want to move to Skype for Business
Thirdly we have Wire.I’ve seen this one on the fringes of chat discussion, but know very little about it. Wire places a heavy emphasis on security. End-to-end encryption, secure guest rooms, and so on. I think this is an excellent position for a challenger chat platform to take. If they can back the claim up (and I’ll look for that in a review), then I expect this one to grow.
Choose Wire if:
Your company places a high value on security for all communications
You need a backup communications option for emergencies (Wire offers a “Wire Red” service for this)
You’re in the EU and would like a chat platform based there
Finally, we have Glip. I only came across Glip a few days ago! It’s a chat offering from RingCentral, the cloud-based phone service. We work with them for some customers, though none mentioned Glip to me.
From reviews I read, Glip is apparently popular with marketing agencies. I think the ‘unlimited guest users’ feature has something to do with that. The in-client document collaboration too. I’ll look into that myself.
Glip doesn’t appear to have any “stand-out” features. It’s pretty much what you’d expect from Slack or Twist, right up to third-party integrations. Pricing’s similarly cheap too. It’s an alternative, if you want to explore.
Choose Glip if:
You already use RingCentral
You’re comparing several chat offerings at once
“What do these platforms cost?” That’s what Management will want to know first, right?
I did the legwork on pricing too. This wouldn’t be a complete guide without it. I divided the platforms into Cloud-Based and On-Prem. You’re either paying a small monthly fee per user, or paying up front for server hardware & bandwidth.
Monthly Cost (Cloud-Based)
SLACK – Standard tier is $6.67/month per user, Plus tier is $12.50/month per user. Plus does come with better support and more administrative options.
TEAMS – Free, though I recommend getting an Office 365 subscription if you don’t already have one. Three options I’d recommend considering when Teams is your main focus: Business Premium ($12.50/month per user), E1 ($8.00/month per user), and E3 ($20.00/month per user).
GOOGLE HANGOUTS CHAT – Part of G-Suite for business users. Business tier is $10/month per user, though the Enterprise tier ($25/month per user) comes with more security.
TWIST – $5/month per user. For business, don’t even consider the Free version; it comes with a 30-day limit on viewing past messages. With Unlimited, you can always access the full message history.
WIRE – Sliding-scale, starting at €6/month per user. Enterprises go down to €4/month per user. To use their Wire Red emergency collaboration service, you must contact their Sales department.
GLIP – Like Twist, there’s a Free tier and a Standard tier at $5/month per user. In this case, the difference is the total time allocated for shared video; Free accounts get 500 minutes total, while Standard accounts get 1,000 minutes/month per user.
Up-Front Cost (On-Prem)
SKYPE FOR BUSINESS (SERVER) – Cost comes in initial deployment. No monthly recurring fees for the software, but you may pay for a SIP trunk mostly depending on configuration. Check my Pricing for Skype for Business and Teams post for details.
MATTERMOST – Free to download & use (it’s open source). You’ll need a server to host it of course, like Skype for Business Server. The Mattermost team does charge for Enterprise accounts though, starting at $39/year per user.
Try Out Some ChatOps Platforms Before Deciding
Okay, you’ve read all the material in this guide. Your users do want to use chat. You have go-ahead from C-level. Time to start the last part of the search—testing.
Make sure to try out at least two chat platforms. Not just yourself either; invite a handful of tech-savvy users to trial the chat with you. (That way you’re not talking to yourself the whole time. It gets lonely…trust me.)
While many of the same visual elements are the same for all these options, how they work with their own features, and how they interoperate with other tools, can make a big difference in your overall experience. We’ve had customers hate Slack but love Teams (and vice versa). One customer absolutely loved Skype for Business Server’s IM tool. It all depends on the office environment and user tastes.
Using a chat platform in your business can save a ton of time, and make everyone more productive to boot. I hope this guide helps you select the right one!
What chat platform did you end up going with? Please share!