Conquer Microsoft Teams Screen Sharing Frustrations

Conquer Microsoft Teams Screen Sharing Frustrations

The Battle of the Blinding Splash Screen

As a seasoned system admin, I’ve had my fair share of frustrations with Microsoft Teams. It’s a tool that’s supposed to make our lives easier, but sometimes, it feels like it’s out to get us. Let me tell you, the battle against the blinding white splash screen is one I’ve been fighting for ages.

I mean, come on, Microsoft. You’ve implemented a dark mode, but somehow, that white screen still manages to sear my retinas every time I open the app. It’s like staring directly into the sun, except the sun is made of pure, unadulterated light. And it’s not just me – our entire organization has had to deal with this issue. [1]

But hey, at least we can take solace in the fact that we’re not alone. The good people over at Reddit have been just as perplexed by this, shall we say, “feature.” As one user so eloquently put it, “The white (blinding) splash screen, even after enabling dark mode (android) – Microsoft has implemented a dark mode on the app, but, there is still a blinding white screen every time the app reloads. Small problem, but should be a simple fix.” [1]

The Maddening Maze of Message Notifications

Now, if the splash screen wasn’t enough to drive us all to the brink, let’s talk about those pesky message notifications. You know the ones – you get a notification that a message has arrived, but when you go to check it, the message is nowhere to be found. It’s like a game of hide-and-seek, except the message is the hider and you’re the seeker, and the hider has an invisibility cloak.

As the system admin, I’ve had to deal with this issue more times than I can count. One user would come to me, frantically explaining that they received a notification but couldn’t find the message in the chat. And you know what I had to tell them? “Have you tried exiting the chat and going back in?” [1] It’s a solution that works, but it’s also a frustrating one. I mean, why should we have to jump through hoops just to see a message that was already sent?

The Sordid Saga of the Unresponsive Reply Button

But wait, there’s more! Let’s not forget about the complete lack of a “reply” or “quote” function in the desktop app. Seriously, Microsoft? It’s been over two years, and this basic feature is still missing. [1] I can’t tell you how many times I’ve found myself opening up my phone just to reply to a specific message in a group chat. It’s absolutely maddening, and it’s not just me who feels this way. As one Redditor so eloquently put it, “Seriously? It has been over 2 years and they STILL can’t implement this on the desktop apps? It just makes the mobile-desktop experience very inconsistent.” [1]

And the worst part? This is the most upvoted feature request in the Teams community, with over 40,000 votes. Yet, Microsoft continues to ignore it, choosing instead to focus on, I don’t know, adding new emojis or something. [1] It’s enough to make you want to throw your computer out the window and start a carrier pigeon-based communication system.

The Woes of the Woeful Wiki

But wait, there’s more! Let’s talk about the Teams wiki, shall we? Now, I know what you’re thinking, “The wiki? Who even uses that?” Well, let me tell you, our organization did, and let me tell you, it was a complete and utter disaster.

As the Redditor so eloquently put it, “It is ABSURD how bad and crippled the default wiki is in the teams. No way to export the articles, no way to print the articles, no search (!!!) , images pasted into the wiki sometimes simply disappear after a while, you can’t copy the content with images and paste it word (for example), no revision history.” [1] I mean, come on, Microsoft. This is the 21st century, and we’re still dealing with a wiki that’s about as useful as a chocolate teapot.

And let’s not forget the promise of SIP calls and SIP integration. They’ve been promising it for over a year, and yet, nothing. [1] It’s like they’re playing a cruel game of “hurry up and wait” with us, and we’re the ones who end up feeling like the fools.

The Tyranny of the “Urgent” Message

But wait, there’s more! Let’s talk about the “urgent” message feature. Now, I know what you’re thinking, “Urgent messages? That’s a good thing, right?” Well, let me tell you, it’s not. In fact, it’s a complete and utter nightmare.

As the Redditor so eloquently put it, “Urgent messages bypass even Android’s “DO NOT DISTURB” setting. Our company has people in different parts of the world and people were getting woken up by messages marked as “urgent” by other team members. It is crazy that MS states that this is the intended behaviour. I had to disable urgent messages in my entire org to avoid this.” [1] I mean, come on, Microsoft. Do you have any idea how disruptive that can be? It’s like having a fire alarm that goes off every time someone wants to ask you what time it is.

The Maddening Malaise of Mobile Search

But wait, there’s more! Let’s talk about the search function on the mobile app. Now, I know what you’re thinking, “Search? That’s a basic feature, right?” Well, let me tell you, it’s not. In fact, it’s a complete and utter disaster.

As the Redditor so eloquently put it, “If you try to search for a message in the chat, sometimes it doesn’t work at all, and when it does, it simply takes you to the chat. So, if I search for a message that was sent months ago, it only takes me to the latest message in that same chat. Then I have to scroll all the way, to find the message in the chat. So, the search is useless.” [1] I mean, come on, Microsoft. This is the 21st century, and we’re still dealing with a search function that’s about as useful as a chocolate teapot.

Conclusion

So, there you have it, folks. The myriad of frustrations that come with using Microsoft Teams. From the blinding splash screen to the maddening message notifications, the unresponsive reply button, the woeful wiki, the tyranny of the “urgent” message, and the malaise of mobile search, it’s enough to make any system admin want to throw in the towel and go back to carrier pigeons.

But fear not, my friends. With a little bit of perseverance, a healthy dose of humor, and a lot of creative problem-solving, we can conquer these frustrations and make Microsoft Teams work for us, rather than against us. After all, as the great philosopher Yoda once said, “Do or do not, there is no try.” [2] So, let’s do this, shall we?

References:

[1] Knowledge from https://www.reddit.com/r/MicrosoftTeams/comments/lccipl/my_frustrations_with_ms_teams/
[2] Knowledge from https://trainingsupport.microsoft.com/en-us/mcp/forum/all/my-awful-experience-with-pearson-vue/8b5d546b-6a4b-4a8a-81a7-a434df8bf3cc

Facebook
Pinterest
Twitter
LinkedIn