I think a lot of Microsoft hate is clouding judgement here. People want Teams to suck.
Why does Teams occasionally load up with the usual icons showing the broken image icon? Why did my organization create a special “Fix Teams” utility?
As a result, Teams is on my computer, adds itself to the startup items, then opens up to a login window every time I turn on my computer. The X button does not work to close the window. I have to open Task Manager and kill it every time. I can disable it in startup items, but it puts itself back there, next time I join a Teams meeting.
Also, if I am using my computer in the closed position, it still chooses the integrated webcam and microphone every time, even sometimes switching to them randomly during a meeting.
Of course, I am running on an unusual setup that I'm sure Microsoft didn't think to test: I am running Microsoft Teams on Microsoft Windows 10 on a Microsoft Surface Pro computer.
Seems like that is something you should have stated in the first comment.
>>Linux/Chromebooks depending on the person in the team and this alone seems to be a major barrier
Something like les than 1% of the world uses Linux on the desktop. Dont get me wrong I love Linux, I used it as my primary desktop from 2005 until around 2012 when I went back to Windows (windows 10)
But calling problems on linux a "major issue" seems to over state the usage of Linux Desktop
further depending on when you tried it, and what client you were using that is likely the root cause
The Linux Desktop client always sucked, so much is no longer a thing, 100% a web app now. The web App teams should work just fine.
I'm sure that if you use the whole Windows enchilada that it may work, but given that Microsoft has shipped a Linux desktop client[1] I would expect that thing to simply work.
It doesn't. Besides wanting to run all the time even when you're not in a teams meeting. Video conferencing is all about seamless integration, it should get out of the way as much as possible and as soon as the tool becomes the focal point of the meeting in my book you've failed to deliver.
[1] https://petri.com/microsoft-replace-teams-linux-client-progr...
And they retired it, apparently because they agreed with my assessment or it isn't worth their trouble.
this is the entire Microsoft business model:
1. identify a competitor's product
2. clone it, but only spend enough engineering effort to make it sound plausible enough to tick the required boxes for evaluation by someone won't have to use it
3. bundle it with your other products (so no need to compete on quality)I'm sure Microsoft will get right on improving that
"DOS aint done 'til Lotus won't run"
Agreed. It's as bandwagon as I've seen anything else. FFS, I half expect to see M$ written about.
It works fine, have your meeting and get back to work. What is it that people are trying to do in Teams?
I happily use windows 10 for most personal computing (I haven't upgraded, so no comment on 11), VScode, github, word, excel, whatever...
Teams, though, is one MS product that genuinely never worked for me. Last company I was at used it, and they had to upgrade my work machine since teams needed more CPU (old machine was an i5 macbook with 8gb). Google/zoom was fine, but running teams would regularly overheat my computer.
But we have to have shared definitions for words or communications just breaks down
It can not be "your definition of broke is different from mine" if that is the case then language is just noise and we need to stop communicating
When I say it is broken I'm pretty serious about it: we spent a full day because there was one customer that positively insisted that we had to use their Teams setup rather than what we normally use and in the end we just gave up, it isn't worth the stress to me if there is a viable alternative (or even several). But of course if you think that I'm redefining the meaning of the word 'broken' just for the heck of it then you're free to continue to do so.
So you tried it once, as a guest and then banned the entire things with out understand the permissions systems or any other possible causes?
Understand that as a Admin I have the power to block Guests from Joining, Block some features from Guest, and so alot of things that is not commonly possible under other platforms. Often these security settings are aggressive by default, for example we had an issue with one client needing to connect to one of our teams room, teams and the room worked fine but because the security settings the Guest could not connect, everyone else could but the guest could not
This is not something that can be fixed by the guest, nor it is problem with teams as a technology, it is the security controls built into the platform
>Do you realize I'm the idiot that came up with live video in the browser to begin with?
and I am a guy that wrote PHP code in the 90's and love it... so....
That's not what I wrote. I wrote that because someone insisted we said, ok, fine let's invest a bunch of time and solve this and we could not.
Before then we had tried multiple times and even now every now and then we get a teams invitation but I just point blank refuse them. Enough time wasted.
Check TFA: this is a Microsoft subsidiary that needs to be forced to use the solution provided by the mothership. That push really wouldn't be necessary if the people at GitHub believed that Teams served their needs well.
Ok - that really surprised me and from anyone else I would’ve dismissed it as hyperbole… after some digging I ended up reading this incredible story —
https://jacquesmattheij.com/story-behind-wwcom-camaradescom/
Amazing adventure!
After they explained to you it was broken in their official client for their officially supported operating system, you moved the goal post to it's only broken in the client, try the web app instead:
> The Linux Desktop client always sucked, so much is no longer a thing, 100% a web app now. The web App teams should work just fine.
Just stop.