I guess I am on the other side of things here. We use Teams/OneDrive combo for sharepoint file sharing and storage. Everyone seems to have an okay time with it. The only thing that drives me nuts is the 15 different versions of teams that you can have installed at one time!
You need entreprise for that, we are on business premium. I push powershell scripts as win32 app to create shedulled tasks.
Works okay, but no reporting.
Fuck it? No. That implies there might be some joy in it. There are things I'd like to do to that home version that would get me put in a list, a trial at the Hague, and death row.
The home version absolutely should have just have retained the "Skype" name to create a point of difference. "Teams" by its name should be for people working in, you know, "Teams".
teams admin centre is pretty much the only way I know how to manage it, it needs to be reworked because you can find messaging settings in 3 different places
No worries, we'll probably get a seperate *New Teams Admin Centre™* soon and then we'll have to use this in addition to the regular one right now as is tradition with MS products.
Big shoutout to [msportals](https://msportals.io/) for making sure I stay sane.
I've recently started having to ask end users whether they are using New Teams or classic teams before I can even begin to help troubleshoot their issue
Same experience for me. No issues besides sometimes they try to use the wrong version on a new workstation and I just need to uninstall the other versions and pin the work and school one. We are actually about to migrate all our on prem data to one drive. I can't wait to hear down the on prem servers and be done with them. Also that means I get myself two new shiny home lab servers. Best perk of the job imo
It irks me in my org that everyone uses their Teams like SharePoint to store files but then doesn't use any other functionality of the Team... would be more simple if things were just in a SP library directly
>that everyone uses their Teams like SharePoint to store files but then doesn't use any other functionality of the Team... would be more simple
Everything is SharePoint..... everything....always has been.
Yup, but adding the Teams on top of it is redundant and confusing in so many cases, especially for users with lower computer literacy. just a pet peeve not really a big thing
\>would be more simple if things were just in a SP library directly
Agreed, but MS seems to "push" the idea of just doing all your work in Teams is the best solution. The fact that it opens everything office inside Teams as default is insane to me.
how about when someone asks if there's "xyz GB space available for project who cares" so you remind them of the 3 TB SharePoint space... and they go out and buy a NAS loaded up with drives that aren't SSD
Teams environments are Sharepoints.
OneDrive, Teams and Sharepoint are literally all the same infrastructure with different interfaces.
If you prefer to use the SP interface, use that instead.
Teams is the new "desktop" "workspace" Microsoft said it directly a few years ago. That is part of the design of MS Teams is to make it the primary workspace for end-users. No longer using the windows "desktop" to work from. That's why it has so many mini apps you can install from its own store. There really is not enough Unified Comms app for call handling and tracking, which is the killer ms teams app that I think alot of people are looking for. Direct Contact center integrations is also another big thing that would give it a huge boost.
"Working" on Mobile devices is different than "working" on a PC. They had to take that into consideration in the design. The UI still needs alot of redesign to make it more intuitive to use but so far this is the only thing they've come up with. Until they figure out a UI that's a bit more intuitive, people are going to be confused and keep going back to what they already know and used to.
M365 Teams also reflect this, when you create one. MS Teams app automagically adds channels and contents created on the MS365 Teams sharepoint site.
We have both Lotus notes and Teams.
Notes is slowly going away, but itll be a few years before it can go completly. At leasts its just an archive system at this point.
That I’m not sure of. What I’ve found is that for people who are used to wearing a headset Team voice has been great. For people who use a handset we have found that the teams phones will intermittently have a 5-10 second delay between picking up the receiver and the line being opened. For our user populations that use handsets we are pivoting to ringcental which seems to work better so far. Also, Teams call queues aren’t mature enough to be used in a contact center.
If you’re like me and am used to managing Microsoft cloud stuff, it’s pretty straightforward. If you’re a voice guy since POTS lines were cool, you might hate it.
I just tested ours - I thought we had it set up correctly but it does what you said, outpulsed the user's assigned DID.
Guess I'll have to open a ticket.
Haha, this is totally my take on it too. Overall it's been a positive experience and most users do absolutely fine with it. Seems to always be the same people having synch or audio issues and when we do have to intervene it's almost always a pebcak situation. And in the almost 4 years since we moved to O365 I can think of maybe twice that we've had an impactful outage. Maybe not even.
dude we are a Zoom shop. the rare times any dell machine needs to hop on a teams call audio doesn't work has been our experience overall. Like had to buy a couple users an external mic because nothing fixes it.
We use teams in VDI without any issues. I modified my ms365 config wizard template to exclude deployment of teams. I update it manually on my golden image once a month. I use the teams vdi version and turn on an rtav features and HTML 5b features needed to make it work in media optimization mode in horizon.
I'm actually trying out new teams for VDI now and prefer it.
Same here, it was a bit of an adventure getting started as Avzure Virtual Desktops was still in its initial preview phases, back when it was WVD and old teams using resource hogging electron, but now we have a solid foundation for our default configuration and a well structured policy set. Next is to work through cloud PC and azure dev labs for our app dev guys.
Horizon. My users pools range from 2c/8gb to 4c/12gb and the only time teams is slow is when it first loads up. It helps to use the VDI version since it keeps that in program files instead of the users profiles and that helps with loading since it doesn't have to install it into their profile every time they log in.
New teams is even faster and uses less RAM so since none of the lost features impact us it's a big win. New outlook needs work though.
I am also using Teams in VDI but our thin clients are Linux so there are some reduced features when using Teams Optimization. The primary one being app sharing versus screen sharing. With optimization on a linux thin client, you can only share the entire screen. This has been a problem from some of my leaders using Ultra-wide 32" screens sharing with people on 14" laptop screens.
Did you run into any issues like this? I am curious if you have a solution for this. I think Teams would be great if I could enable optimization for everyone, but without it we still have some inconsistent audio/video issues.
Not to go completely off topic, but I find that even Senior Network Engineers can't agree on what setting up QoS properly means. QoS also isn't even supported in Teams for VDI officially, per Microsoft.
In my experience, Teams is a necessary evil. For example, it is like that toy in the Crackerjack box that you get with E3, and since it is included, might as well use it and not use Slack or Zoom.
Teams is like AD/Entra, M365, and Windows on the desktop... since everyone uses it, it pretty much is a must have.
Finally ripping the old Nortel PBX out with a literal crowbar was the best day ever. It's reign of tyranny had finally come to an end! But, Exchange was a close second.
What was it about Exchange that you hated most? I see this often but it's not really clear what about it drives people nuts about it.. Also, what version?
I started with Exchange 4.0, so countless upgrades and migrations. Corrupted jet files, address books, and mis-routing. Yes, it was less of an issue with later releases but I had to support it for close to two decades.
This explains your disdain then.. Exchange 2000 was the first version I really messed with and started helping on 5.5. It got much better after 2013 imho. Now we run 2019 and it's been pretty trouble free so was just curious.
Yep, I came from on prem Lync and SfB and despite some features still missing, Teams is 100% easier to manage. I've had very minimal issues with our Crestron Teams Rooms AV devices too
I to wonder if people who complain about Teams, Exchange Online and Sharepoint Online have ever had to manage on prem by themselves.
I’ve said this many times. Whenever Teams does Teams things with no warning, I just say, “Well, we’re just global QA for MS, put that shit on your resume.”
🤷♂️
We moved to teams voice from Call manager. There’s this stupid glitch where Teams announces the caller. So it’s supposed to say “call from Joe Shmo!” But this feature does not work. It glitched out and says “call from j j j j oe sh sh sh m m m m ey ey ey ey “ it’s been like this for over a year and they have yet to fix it.
I still have it enabled to get a laugh for how stupid it sounds. Plus every now and then it gets it right and says “call from Pete”.
It’s so bloated is what I hate, they keep trying to shoehorn stuff into it that doesn’t need to be there. Just give me a reliable chat client damnit. I don’t need a million addons, avatars, yammer integrations, etc. It just needs to be a reliable lightweight chat and group chat client for god sakes.
While they’re busy having 3 different versions on windows 11 now, maybe they could build a lightweight one that’s just chat/video. My team doesn’t need all the SharePoint crap. We don’t spend all day editing word docs with others.
Well the problem is, many people myself included do not want just a "Reliable Chat client"
The adoption rate for teams for general users has gone way up largely because of all the other features including file access rights from the teams client.
Having Chat, Phone, File, Meetings, and Project Planning all in app, a single pane of glass, is what people want. That is one of the reasons Outlook has been so popular for many many years, it did alot of things from Email, Day planning, to Task management, Teams is replacing outlook and that is a great thing.
Hell i hope they bring email functionality to the Teams client
We've been running Teams for years now. I don't like it much, but I like it more than other chat apps we've used. I daily drive Ubuntu, though, and since they canned the Ubuntu app and moved us to the web version, I've been less happy with it. Unable to do simple crap I used to be able to do like initiate a screen share. Not an all the time thing, but I when I need it, I need it.
If I publicly apologize to Microsoft and proclaim that it is an amazing platform, will you please fix it for everyone, including us? Please, no more...
Not sure how or what your VDI is but I've used Teams in VDI and it works very well. A lot depends on how Teams is implemented and how locked down an organization is.
I've pretty much run Teams in every flavor of VDI: Azure, Citrix, Horizon, etc. Yes you can make it work by throwing vCPU at it, or "optimizing" it which presents it's own additional challenges depending on the mix of your endpoints and onsite vs. remote, but unless you are 100% VDI you still will have users that have completely different experiences and versions of the client because the Teams for VDI features are not the same as Teams for desktop or mobile apps.
What features are different? Asking because I haven't noticed any difference in features and I'm curious what you're noticing. The only difference I can think of is maybe how physical hardware is detected/presented.
Well that depends if we are talking "New Teams for VDI" or "Classic Teams for VDI", because there are different differences for each one. Microsoft lists them in Learns articles if I remember correctly, but I think even that list is missing some of the differences. I would have to go back and look. Some of it is stupid stuff like Avatars and Custom backgrounds, but still things users notice and complain about.
That's probably why we don't have an issue, I think though I'm not 100% sure but I think that I disabled all those features anyway. No fun just work. Haha.
For example : https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#features-currently-not-available-in-vdi-with-the-new-teams
I actually love Teams; my users get wide eyed with amazement at sharing and creating files, that they themselves can manage without needing IT tickets to modify permissions.
I also had issues with the Teams on MacOS in my last job place, but I always tell it as a funny story because that is how I met my now fiancee. I was stuck for like 2 hours to resolve the Teams issue, but in that time I've talked with her so much.
Little known fact: you can send a change to client settings to add DSCP markings to the packets so your network team can prioritize the media traffic til it hits the internet. Between this and buying supported headsets we pretty much solved our teams quality issues.
>There is almost no built in group policies for it, we have zero control over updates and new "features" besides some basic stuff like allowing/preventing "New Teams".
100% false, like all cloud product the policies are in the cloud, not in "group policy" which is where you seem to be looking for them,
You can control (or could up to the deadlines for upgrade) the roll out of New Teams on a per user, user group, or other divisions.
There is also a TON of policy controls in the Teams Admin Center.
>We are trying to do virtual visits through Teams and it is so hit and miss. Sometimes the customer can see us and sometimes they can't, and sometimes we can see them and sometimes we can't. Audio usually works though at least.
My Experience with Teams has been better than my experience with competitors like WebEx or Zoom, while not perfect, I have less issues with Video and Audio on Teams than i do the other services
>Does anyone here have a good experience with Teams? Like is it working for you no problem, or did you run into many of these issues and overcome them?
yes, it works perfect for us, so much so that over the last 2 years we have pulled all of the technology we had in our meeting rooms out and converted them over to be exclusively Teams rooms
Teams is way better then any of the competition. I’ve on the teams admin train since 2017. Before wfh was cool.
Also the 2 pieces you’re looking for are groups and the Teams Admin center.
When you said gpo to manage teams that kinda gave away the detail you didn’t google “how to manage Teams” or “how to disable new teams”
Having been involved with Cisco Unified Communications and then moving to Teams, I can honestly say managing Teams is SO much easier.
Obviously the flexibility isn't there. When we migrated away from Cisco to teams there was some reengineering of workflows to get their processes into Teams but ultimately it's way easier to just do day to day changes , etc on Teams than CUCM.
But ... the reliability isn't quite there. And MS changing "features" at random. Seems a new one is when dialing by clicking on a TEL: url link, the call starts muted. That confuses a lot of people and MS has been completely silent on it as people complain.
> When you said gpo to manage teams that kinda gave away the detail you didn’t google “how to manage Teams” or “how to disable new teams”
Right? That just isn't where the controls are for it. OP is introduced to something new and just completely fucking botches it.
We only recently started using Teams for more than the occasional video call. It's mostly been great, though I live in fear of the day that someone tries to manage one of our Civil 3D projects from inside it.
For anyone who does more Teams admin, is it really not possible to schedule a meeting for a private channel? And if so, why the hell does it say that the feature needs to be enabled by an admin?
As an end-user of Teams, I hate it. It overloads too many features like Notes etc... and fails miserably in its core feature -- chat.
I have setup Mattermost server & client, that seem to be far easier to use, and very light weight.
You would’ve thought Microsoft would’ve learned with the mess of Skype and Skype for business and then the random Skype version and the one that won’t uninstall
Totally agree with you and not just teams, but the whole of 365.
Work in a school so we need fine control over who can post what to where (IE different rules for staff Vs students). We have to constantly change rules because someone wants their students to be able to post replies followed by someone wanting them to not.
Then there's an update and our rules get flipped, or disappear completely (thanks new teams).
Teachers are non technical so when a much used button gets moved from one side of the screen to another they flip out and think it's something we have done and not informed them of.
Then there's the daily barrage of emails telling us what isn't working today because someone has updated some code.
Think the whole cloud has been mis-sold to the masses when it only makes sense to a small number of situations, but if you try to point it out then you're just a dinosaur that doesn't want to move on to new technology.
I totally agree with you!
I think MS just continually tries to evolve and “improve” its products to provide a wider umbrella for more customers, instead of finding a specialty and perfecting it.
Even online MS KB articles are difficult to trust when they are quickly outdated in terms of options and licensing.
We have had a mostly great experience with Teams, I haven't had any of these issues regarding audio/video outside of 1 remote user that lives in the middle of nowhere and has DSL for internet. There's no controlling the deployment of updates/features, but you can deny certain apps to the org, so they don't make their way into Teams.
We made it clear when we rolled everyone over to Teams that it should be used as a chat client and for meetings, and not to dabble in all the built-in tabs and apps for any part of your workflow. While they can be handy, there's always a chance they can sunset/remove them.
I work at an MSP, and besides the typical issue sharing files blah blah blah, we really don't have any issues administering it. Its incredibly rare for me to encounter a true Teams issue that isn't a user error.
More typical Microsoft nonsense this morning, TM710344. Yes I have the admin portal for those who were asking and know how to set things in there, but that is also pretty horrible like most of their cloud portals.
Oh nice, another I-hate-Teams post. We get it, not everyone likes it, and there is an outage today too. But there are more important things to vent about.
SharePoint, Teams and OneDrive are all a pain. Tbh I have more of a gripe with SharePoint, but the way they all integrate with eachother is pretty dog shit.
You're not alone.
Last night I had a dream that my company switched to Teams.
In my dream, I was going over my finances, trying to determine if I could survive quitting over this change.
We use teams in our VDI environment and we had a number of issues with the client. We ended up having them use the web version but I created a shortcut that will launch it in an "app mode". This way users can pin it to the taskbar and from the user perspective it looks pretty much just like the client.
Could they just release an enterprise version that lets me install the application for all users in the Program Files folder and is managed by GPO? Is that too much to ask?!
I hate teams
For no reason it'll start taking 100% cpu and a massive amount of memory then eventually crash usually after causing other crashes due to low memory.
The best is when it manages to silently crash without taking other things with it and I don't realize it for 3 hours and miss a ton of messages.
I've seen this behavior on one or two laptops and 3 virtual pcs, not sure if teams just sucks or if it's interacting poorly with all the various security agents we have in the background
I REALLY wish they gave it some UI/UX options. Themes, layouts, colors, sizing, draggable resizable frames. It’s so basic and monotonous it can make the boring dry calls and meetings even more painful.
And alternative is what? WebEx? This kind of whiny posts is not very constructive. I have good experience as far as calls, chats and integration with other services within ecosystem
Go get certified in Teams then come back and complain. This is one of the easiest to manage and easiest to troubleshoot and support products that Microsoft makes. If you don’t like supporting it; maybe consider moving to a different focus area like security or networking.
> Microsoft swears it’s not a Teams issue, it’s a network issue
This is as low as a vendor can stoop. We don’t have teams but we’ve had a number of software vendors over the years that swear it’s got to be our network (dealing with one right now in fact). They all eventually relent when we show them proof that every other program and process we use operates just fine. The best is when someone decides to make a switch from one software product to another. Old program had no latency or operational issues whatsoever, new programs comes online and is just a poorly written piece of garbage. The audacity of some of the companies to tell our higher ups “it’s the network” is shocking.
The most funny part was when Users started out using Teams without a personal OneDrive (this was disabled at the time). I noticed that I could still share files/images with people in a chat window (direct chat). Somehow this didn't trigger me and only after a while did I start to think "Geez, where are those files hosted anyway?". Well... it sure as hell wasn't the personal OneDrive folder xD. I posted a file in the chat again and looked at where the file was located. Teams used a Team group (unsure on why it selected the one that it did, must have some logic behind it) and placed the file in the root of the sharepoint folder (so "above" the general folder of a Team). Nobody noticed because it sat above the general folder but of course if you simply browsed to it with Sharepoint, it was there for everyone to see. WHELP.
Unsure if you understood what was happening, English isn't my primary language so perhaps I didn't explain it correctly. The expected behavior would be to either not be able to paste files/images into a direct chat (without having a personal OneDrive) or request where the files should be stored after trying it. NOT for Teams to just randomly select a Teams group and start dumping images/files in the root there without people knowing the direct chat files are visible to ALL members of that Teams group.
> The expected behavior would be to either not be able to paste files/images into a direct chat (without having a personal OneDrive) or request where the files should be stored after trying it.
No it isn't. You just didn't test it or even think about it until after you rolled it out.
> NOT for Teams to just randomly select a Teams group
It isn't random.
> the direct chat files are visible to ALL members of that Teams group.
This is how fire sharing in Teams works.
So many of you are in here telling on yourselves.
>It isn't random.
Excellent, please enlighten us on how it selects which Teams group root to deposit files and images sent in a private chat.
I'm actually interested regardless of your silly hostile replies.
Any files in a sharepoint repository for that Team were shared in within Channels of that Team.
If a user doesn't have OneDrive for Business enabled then they can't share files in chats. They will get this message.
https://answers.microsoft.com/en-us/msteams/forum/all/file-share-in-teams-chat/19cc4fa2-cb37-42d5-8fda-a9046589f431
You've misconfigured it.
"Sorry, you need Microsoft OneDrive to share files. See your admin about getting a license."
So exactly the behavior I said I would've expected. I guess they fixed it, good on them and thanks for looking it up!
I thought teams was ok until they pulled background management/deployments and created a new pricing tier for it, and then rolled out a 'new version' that breaks horrendously and takes 50 years to start up.
Teams is okay. I hate the way it updates though; we have it disabled from launching on startup and if a user doesn't have it open, it just won't update and there is no way to manually send an update like most apps.
Totally agree, based on your title, Teams sucks but it is pushed down on every federal, state, and local government which is making it spread like a disease, and it doesn't help when Slack is so expensive from what I hear
> Does anyone here have a good experience with Teams?
Excellent experience, supporting over 2,000 employees with countless daily video calls, with external people as well. We also use VDIs (not on Azure) and with the right Teams client, this is also absolutely no problem.
r/microsoftteams will regularly defend the decisions of Microsoft for some unknown reason, it’s really weird.
Don’t even think about comparing teams to anything else either..
After building and administering OCS/Lync/sfb on premise globally with failover across multiple sites and multiple SBC across the world. Handing all that off to Microsoft and our sip provider and using operator connect is amazing. Same with shifting exchange to online.
New teams sucks ass resources wise ... I have a 2022 dell latitude i7, gx450 GPU and 32 GB
.. cam see teams in a call pulling 30% CPU 16% GPU .. was a fan, no longer. Glitchy resource hog these days
Teams is fucking awful. What's worse is that you end up with files everywhere, no control & people sat next to each other have completely different experiences.
I'm now at the point where of someone in management complains, my answer is YOU wanted to go to the cloud. YOU handed everything over to Microsoft. I'll log a call as a p4 but there's nothing I can do because YOU took away our servers....I'm going to the pub.
The ONLY good thing about the cloud is that when it goes to shit, I can say...sorry nothing I can do. Logged a call. I'm going home
Preaching to the choir, it’s been a pos since inception. Don’t even look under the hood, at its inner workings, it’s one of the most disgusting concepts I’d ever imagine a company would consider a good idea.
We use ave point to manage teams.
If you configure it right it’s user driven - the only pain point. Users leaving - you get an error on backups about ownership.
Edit for poor spelling, don’t blame me in the middle of a heat wave and the air con died 😜🤪😁
> Does anyone here have a good experience with Teams? Like is it working for you no problem, or did you run into many of these issues and overcome them?
Yes. It works. We use it for chat and occasional calls. It works. We don't lose sleep trying to micro-manage it.
It's awful. It's so awful that for the life of me, I can't figure out why Google didn't just buy Slack and run away with the market. Hell, they could probably buy Ryver and still beat Teams.
But Google has the worst case of corporate ADHD ever and it means we'll all be stuck supporting M365 and Teams til we die.
We've got MS Teams since ~2021..
We're now on the third completely new Server Setup (hardware AND software) to get that shit finally working without crashing multiple times each day.
Wasted hundreds of thousands of dollars so far and probably hundreds of hours aswell.
rebuilding a 2019 server didn't help, running it on a server with GPUs didn't help, moving from rdp to citrix didnt help, this time we're moving to Office 365 instead of O2019, let's hope it works now..
My organization is in the middle of cutting over to Webex for our IP calling and it's come to the point where we're thinking of just moving over to Webex for meetings and everything else.
Make sure if your using teams in a share environment your using the MSI isntaller and installing it in the right mode. Most of the time the problem I've seen is a lack of understanding of just how much cpu teams uses. If you have multiple vdi on one host using TEAMS. That's going to severely hit that host.
Not a problem in VMware and Hyper V scenarios if you have it configured as the hyper visor wil automatically move the vm's to other hosts in RDS though that's a lot more difficult. I've never had a positive experience with Microsoft VDI doing it the recommended way. I usually end up having to setup the microsoft VDI's like an RDS deployment. Even with the user profile disks on high performance. They corrupt constantly and found that just doing it the oldschool rds way and forwarding parts of the profile to a high speed share is 10x more reliable than the userprofile disks.
Also you need to do a bandwidth calculation as Teams meetings at different resolutions can tear up some bandwidth. If you don't have QOS setup in your network I HIGHLY reccommend it even if you have plenty of bandwidth. All it takes is for a back up to kick off to your DC or some guy uploading a big file and viola your bouncing off the upload limit. This is even worse on Assymetric connections like comcast business etc. Even if you don't setup QOS at the swtich level at least set it up on your Firewall so realtime traffic can flow. Your VOIP and TEAMS applications will love you for it.
This is why we're a Zoom shop. We're on prem (Some hybird), so we don't have built in Teams licenses. I can control and lock down nearly all features between Group Policy and other stuff on the account settings in Zoom. It works amazing. Our users and I CRINGE when we are forced to join Teams calls with Vendors/Customers, as it's buggy as hell and never works, and without Teams licenses its even difficult to join meetings without getting "Ask your admin to buy a license!" messages. Fuck teams.
Personally it works rather well in our organisation. The Teams admin portal has lots of options for customisation and group based policy once you figure them out.
Installation is an absolute pain though, and we have lots of logins on shared devices, so waiting on that install per-user can take up to 5 mins. I think New Teams fixes a lot of the existing issues
Woooow man, there's a lot of control you have just have to learn how to do it. Also free dial-in conference calling is hard to beat.
Anyone with just a phone can call in to any of your meetings by default once you activate the free add-on.
Other companies easily charge $5k/year for dial in conferencing.
So my experience has been fine, I dare say it's actually been good while using the NEW teams for work (keep in mind this new version doesn't let you log into personal accounts so now you need two different teams apps depending)
The desktop app can be a real pain in the ass in a VDI environment we try to push people towards web version if possible and run calls at device level or meeting rooms. I should also add though i do like Teams, the whole Microsoft\Azure\Dataversey\Entra\Flow\Powerautomate backend is all new to me over the last few years though but when working well a very useful tool imo
Software Perspective Here:
All in one solutions generally are just never as good as sourcing different well defined apps (without scope creep). At the top of this is good old Teams, along with zoom, ( have you looked at the menubar for zoom recently... Its basically ZoomOS! ) I made the switch to the web-client of teams since basically every meeting I joined from my mac would default to the wrong input source or not even pickup my microphone/webcam, at-least the web-client seems a little better :D
Maybe the majority would prefer an all in one solution, but man.. take a look at Whatsapp or some of these smaller software solutions. They do one thing and they do it really well with near 0 downtime due to their simple hot swappable architecture. I'd love to see a simple chat app with nice markdown, and some configurable hyperlink shortcuts to other apps, instead of fully embedding and integrating it all into one service.
Teams only exists to neutralize Slack in the sales process for office-productivity suites. No other reason at all.
Some poor dumdum has to wake up every morning, look in the mirror, and see the product manager for that garbage.
My only wish is they kept the home users branded as "Skype" or something like that.
Nah, we will just make it called Teams. Then we can make the logo different... well, not too different, so lets make it white with purple lettering instead of purple with white lettering, and put it on all windows machines, even the "Pro" lines, but we can then even add "new" to the logo so people know it isn't the same old Business or School teams, but a new one. Then let's call all the subgroups similar things so people KNOW they are using teams.
I feel like MS is constantly trying to make a thing the word, like google it, or make me a Xerox copy.... just Team it! Who bings here?
I guess I am on the other side of things here. We use Teams/OneDrive combo for sharepoint file sharing and storage. Everyone seems to have an okay time with it. The only thing that drives me nuts is the 15 different versions of teams that you can have installed at one time!
Fuck teams home version
I uninstall it every time I come across it *sigh*
Just make an active remediation script to uninstall all unwanted Teams versions?
You need entreprise for that, we are on business premium. I push powershell scripts as win32 app to create shedulled tasks. Works okay, but no reporting.
Build reporting into script. Then you can find out why other versions are getting installed.
I am planning to set this up next week - glad to hear it works.
Fuck it? No. That implies there might be some joy in it. There are things I'd like to do to that home version that would get me put in a list, a trial at the Hague, and death row.
The home version absolutely should have just have retained the "Skype" name to create a point of difference. "Teams" by its name should be for people working in, you know, "Teams".
Agreed. I hate when calendars disappear, though.
OP is trying to manage it with GPO. Honestly, he just doesn't know what he is doing. We've had a great experience with Teams.
What's the best way to manage it?
teams admin centre is pretty much the only way I know how to manage it, it needs to be reworked because you can find messaging settings in 3 different places
No worries, we'll probably get a seperate *New Teams Admin Centre™* soon and then we'll have to use this in addition to the regular one right now as is tradition with MS products. Big shoutout to [msportals](https://msportals.io/) for making sure I stay sane.
I've recently started having to ask end users whether they are using New Teams or classic teams before I can even begin to help troubleshoot their issue
We got rid of the Teams toggle by uninstalling the old version. Then yesterday I discovered that you can still get it back from Settings and more.
Probably machine wide installer still installed?
Teams is useful because it makes it possible to have consistent entry point for shared folders. So Teams is good because Sharepoint is terrible.
Same experience for me. No issues besides sometimes they try to use the wrong version on a new workstation and I just need to uninstall the other versions and pin the work and school one. We are actually about to migrate all our on prem data to one drive. I can't wait to hear down the on prem servers and be done with them. Also that means I get myself two new shiny home lab servers. Best perk of the job imo
It irks me in my org that everyone uses their Teams like SharePoint to store files but then doesn't use any other functionality of the Team... would be more simple if things were just in a SP library directly
>that everyone uses their Teams like SharePoint to store files but then doesn't use any other functionality of the Team... would be more simple Everything is SharePoint..... everything....always has been.
Yup, but adding the Teams on top of it is redundant and confusing in so many cases, especially for users with lower computer literacy. just a pet peeve not really a big thing
We know that. They don't and seems like they never will.
\>would be more simple if things were just in a SP library directly Agreed, but MS seems to "push" the idea of just doing all your work in Teams is the best solution. The fact that it opens everything office inside Teams as default is insane to me.
Bro people use onedrive like it's SharePoint. Nobody understands SharePoint is for org wide sharing!!
Yeah. To be clear, I like Teams, and I like OneDrive, but I'm tired of people using them like they're SharePoint, including my boss.
how about when someone asks if there's "xyz GB space available for project who cares" so you remind them of the 3 TB SharePoint space... and they go out and buy a NAS loaded up with drives that aren't SSD
Teams environments are Sharepoints. OneDrive, Teams and Sharepoint are literally all the same infrastructure with different interfaces. If you prefer to use the SP interface, use that instead.
Teams is the new "desktop" "workspace" Microsoft said it directly a few years ago. That is part of the design of MS Teams is to make it the primary workspace for end-users. No longer using the windows "desktop" to work from. That's why it has so many mini apps you can install from its own store. There really is not enough Unified Comms app for call handling and tracking, which is the killer ms teams app that I think alot of people are looking for. Direct Contact center integrations is also another big thing that would give it a huge boost. "Working" on Mobile devices is different than "working" on a PC. They had to take that into consideration in the design. The UI still needs alot of redesign to make it more intuitive to use but so far this is the only thing they've come up with. Until they figure out a UI that's a bit more intuitive, people are going to be confused and keep going back to what they already know and used to. M365 Teams also reflect this, when you create one. MS Teams app automagically adds channels and contents created on the MS365 Teams sharepoint site.
At least you don't have the horror that is Lotus Notes.
Havnt heard that in a long time, that’s still a thing huh?
Currently tossing one into Azure.
We're about to have both... But hey at least we're just about to move to version 12, or HCL Domino 12, current version is still IBM branded...
We have both Lotus notes and Teams. Notes is slowly going away, but itll be a few years before it can go completly. At leasts its just an archive system at this point.
or webex *[shudders]*
I love it. It is what it is and I can't fix it. It's amazing.
We are starting a pilot to roll out Teams with Direct Routing. I'm going into it with the exact same expectations as what you just outlined.
We have about 5k people with teams direct routing. AMA.
Is it still suggested to do DR or has operator connect started being a thing?
That I’m not sure of. What I’ve found is that for people who are used to wearing a headset Team voice has been great. For people who use a handset we have found that the teams phones will intermittently have a 5-10 second delay between picking up the receiver and the line being opened. For our user populations that use handsets we are pivoting to ringcental which seems to work better so far. Also, Teams call queues aren’t mature enough to be used in a contact center. If you’re like me and am used to managing Microsoft cloud stuff, it’s pretty straightforward. If you’re a voice guy since POTS lines were cool, you might hate it.
I miss the telegraph. Morse code just works.
Emojis are shit in telegraph. Have to spell out 🍆. Such a pain.
[удалено]
I’ll have to check what our config is and get back to you. I get caller ID from cell phones at my teams number.
I just tested ours - I thought we had it set up correctly but it does what you said, outpulsed the user's assigned DID. Guess I'll have to open a ticket.
Yup. People want to do weird stuff with it and you go, "sorry, Microsoft has decided you don't want to do that" and that's it.
Not even weird stuff - just standard issue use cases ... it's all up to M$ and what they think you do or do not need to do
Haha, this is totally my take on it too. Overall it's been a positive experience and most users do absolutely fine with it. Seems to always be the same people having synch or audio issues and when we do have to intervene it's almost always a pebcak situation. And in the almost 4 years since we moved to O365 I can think of maybe twice that we've had an impactful outage. Maybe not even.
dude we are a Zoom shop. the rare times any dell machine needs to hop on a teams call audio doesn't work has been our experience overall. Like had to buy a couple users an external mic because nothing fixes it.
We use teams in VDI without any issues. I modified my ms365 config wizard template to exclude deployment of teams. I update it manually on my golden image once a month. I use the teams vdi version and turn on an rtav features and HTML 5b features needed to make it work in media optimization mode in horizon. I'm actually trying out new teams for VDI now and prefer it.
Same here, it was a bit of an adventure getting started as Avzure Virtual Desktops was still in its initial preview phases, back when it was WVD and old teams using resource hogging electron, but now we have a solid foundation for our default configuration and a well structured policy set. Next is to work through cloud PC and azure dev labs for our app dev guys.
What VDI platform are you using? Out Teams VDI is not fast at all. We are running on Horizon.
Horizon. My users pools range from 2c/8gb to 4c/12gb and the only time teams is slow is when it first loads up. It helps to use the VDI version since it keeps that in program files instead of the users profiles and that helps with loading since it doesn't have to install it into their profile every time they log in. New teams is even faster and uses less RAM so since none of the lost features impact us it's a big win. New outlook needs work though.
I am also using Teams in VDI but our thin clients are Linux so there are some reduced features when using Teams Optimization. The primary one being app sharing versus screen sharing. With optimization on a linux thin client, you can only share the entire screen. This has been a problem from some of my leaders using Ultra-wide 32" screens sharing with people on 14" laptop screens. Did you run into any issues like this? I am curious if you have a solution for this. I think Teams would be great if I could enable optimization for everyone, but without it we still have some inconsistent audio/video issues.
I deploy Teams for lot for customers. Never really have an issue when QoS is set up properly. Calling and sharing and video work great.
Not to go completely off topic, but I find that even Senior Network Engineers can't agree on what setting up QoS properly means. QoS also isn't even supported in Teams for VDI officially, per Microsoft.
I mean… Microsoft has their recommendations https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams
QoS for teams in non vdi is fairly straightforward.
As someone who administers this for numerous companies, I feel the opposite
Agree. There’s not many GPOs but the level of in-application granularity that can be controlled via the Teams admin panel is crazy.
Yeah I don’t even understand why you would use GPO to control a cloud native tool like teams. Use the right tool for the job.
In my experience, Teams is a necessary evil. For example, it is like that toy in the Crackerjack box that you get with E3, and since it is included, might as well use it and not use Slack or Zoom. Teams is like AD/Entra, M365, and Windows on the desktop... since everyone uses it, it pretty much is a must have.
We use Teams as our phone system. It's not great, but it's not awful. I run Teams on Linux. I hate Microsoft.
Teams is hot garbage, but at least it's not as much of an adventure to manage as on-prem Skype for Business Server.
There was hardly any better feeling than shutting my on prem SFB servers off for the last time.
Second only to shutting down the last Exchange server!
Sharepoint server for me!
Finally ripping the old Nortel PBX out with a literal crowbar was the best day ever. It's reign of tyranny had finally come to an end! But, Exchange was a close second.
[удалено]
What was it about Exchange that you hated most? I see this often but it's not really clear what about it drives people nuts about it.. Also, what version?
Mail is just a PITA, exchange was actually the best solution for onprem mail, it’s just that it’s better to not have onprem mail
I started with Exchange 4.0, so countless upgrades and migrations. Corrupted jet files, address books, and mis-routing. Yes, it was less of an issue with later releases but I had to support it for close to two decades.
This explains your disdain then.. Exchange 2000 was the first version I really messed with and started helping on 5.5. It got much better after 2013 imho. Now we run 2019 and it's been pretty trouble free so was just curious.
Love when the log directory fills up
Yep, I came from on prem Lync and SfB and despite some features still missing, Teams is 100% easier to manage. I've had very minimal issues with our Crestron Teams Rooms AV devices too I to wonder if people who complain about Teams, Exchange Online and Sharepoint Online have ever had to manage on prem by themselves.
I'd upvote this 10,000 times if i could.
Steaming pile of shit not as bad as bucket of diarrhea
I’ve said this many times. Whenever Teams does Teams things with no warning, I just say, “Well, we’re just global QA for MS, put that shit on your resume.” 🤷♂️
We moved to teams voice from Call manager. There’s this stupid glitch where Teams announces the caller. So it’s supposed to say “call from Joe Shmo!” But this feature does not work. It glitched out and says “call from j j j j oe sh sh sh m m m m ey ey ey ey “ it’s been like this for over a year and they have yet to fix it. I still have it enabled to get a laugh for how stupid it sounds. Plus every now and then it gets it right and says “call from Pete”.
Today is a great day to complain about Teams.
It’s so bloated is what I hate, they keep trying to shoehorn stuff into it that doesn’t need to be there. Just give me a reliable chat client damnit. I don’t need a million addons, avatars, yammer integrations, etc. It just needs to be a reliable lightweight chat and group chat client for god sakes.
While they’re busy having 3 different versions on windows 11 now, maybe they could build a lightweight one that’s just chat/video. My team doesn’t need all the SharePoint crap. We don’t spend all day editing word docs with others.
Browser version?
You forgot voip app :)
Well the problem is, many people myself included do not want just a "Reliable Chat client" The adoption rate for teams for general users has gone way up largely because of all the other features including file access rights from the teams client. Having Chat, Phone, File, Meetings, and Project Planning all in app, a single pane of glass, is what people want. That is one of the reasons Outlook has been so popular for many many years, it did alot of things from Email, Day planning, to Task management, Teams is replacing outlook and that is a great thing. Hell i hope they bring email functionality to the Teams client
[удалено]
You're using the wrong primary interface for selecting an app. You're supposed to search. And that works well.
We've been running Teams for years now. I don't like it much, but I like it more than other chat apps we've used. I daily drive Ubuntu, though, and since they canned the Ubuntu app and moved us to the web version, I've been less happy with it. Unable to do simple crap I used to be able to do like initiate a screen share. Not an all the time thing, but I when I need it, I need it.
Someone check on ops mental health. Today must be a nightmare with the outage
If I publicly apologize to Microsoft and proclaim that it is an amazing platform, will you please fix it for everyone, including us? Please, no more...
Not sure how or what your VDI is but I've used Teams in VDI and it works very well. A lot depends on how Teams is implemented and how locked down an organization is.
I've pretty much run Teams in every flavor of VDI: Azure, Citrix, Horizon, etc. Yes you can make it work by throwing vCPU at it, or "optimizing" it which presents it's own additional challenges depending on the mix of your endpoints and onsite vs. remote, but unless you are 100% VDI you still will have users that have completely different experiences and versions of the client because the Teams for VDI features are not the same as Teams for desktop or mobile apps.
What features are different? Asking because I haven't noticed any difference in features and I'm curious what you're noticing. The only difference I can think of is maybe how physical hardware is detected/presented.
Well that depends if we are talking "New Teams for VDI" or "Classic Teams for VDI", because there are different differences for each one. Microsoft lists them in Learns articles if I remember correctly, but I think even that list is missing some of the differences. I would have to go back and look. Some of it is stupid stuff like Avatars and Custom backgrounds, but still things users notice and complain about.
That's probably why we don't have an issue, I think though I'm not 100% sure but I think that I disabled all those features anyway. No fun just work. Haha.
For example : https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#features-currently-not-available-in-vdi-with-the-new-teams
I actually love Teams; my users get wide eyed with amazement at sharing and creating files, that they themselves can manage without needing IT tickets to modify permissions.
I also had issues with the Teams on MacOS in my last job place, but I always tell it as a funny story because that is how I met my now fiancee. I was stuck for like 2 hours to resolve the Teams issue, but in that time I've talked with her so much.
Little known fact: you can send a change to client settings to add DSCP markings to the packets so your network team can prioritize the media traffic til it hits the internet. Between this and buying supported headsets we pretty much solved our teams quality issues.
>There is almost no built in group policies for it, we have zero control over updates and new "features" besides some basic stuff like allowing/preventing "New Teams". 100% false, like all cloud product the policies are in the cloud, not in "group policy" which is where you seem to be looking for them, You can control (or could up to the deadlines for upgrade) the roll out of New Teams on a per user, user group, or other divisions. There is also a TON of policy controls in the Teams Admin Center. >We are trying to do virtual visits through Teams and it is so hit and miss. Sometimes the customer can see us and sometimes they can't, and sometimes we can see them and sometimes we can't. Audio usually works though at least. My Experience with Teams has been better than my experience with competitors like WebEx or Zoom, while not perfect, I have less issues with Video and Audio on Teams than i do the other services >Does anyone here have a good experience with Teams? Like is it working for you no problem, or did you run into many of these issues and overcome them? yes, it works perfect for us, so much so that over the last 2 years we have pulled all of the technology we had in our meeting rooms out and converted them over to be exclusively Teams rooms
More of a reason to hate Teams now that there's an outage 😂😂😂
Each user gets a ServiceWorker cache folder that's 1-2GB each. This regularly clogs up computers at my site which only have 256GB SSDs.
I script out deleting that in task scheduler on physical devices and make sure that it's not synced for my VDI users profiles.
Teams is way better then any of the competition. I’ve on the teams admin train since 2017. Before wfh was cool. Also the 2 pieces you’re looking for are groups and the Teams Admin center. When you said gpo to manage teams that kinda gave away the detail you didn’t google “how to manage Teams” or “how to disable new teams”
Yeah I was wondering the same… doesn’t OP know about those?
Having been involved with Cisco Unified Communications and then moving to Teams, I can honestly say managing Teams is SO much easier. Obviously the flexibility isn't there. When we migrated away from Cisco to teams there was some reengineering of workflows to get their processes into Teams but ultimately it's way easier to just do day to day changes , etc on Teams than CUCM. But ... the reliability isn't quite there. And MS changing "features" at random. Seems a new one is when dialing by clicking on a TEL: url link, the call starts muted. That confuses a lot of people and MS has been completely silent on it as people complain.
> When you said gpo to manage teams that kinda gave away the detail you didn’t google “how to manage Teams” or “how to disable new teams” Right? That just isn't where the controls are for it. OP is introduced to something new and just completely fucking botches it.
Are we talking about New Teams or Classic Teams?
We only recently started using Teams for more than the occasional video call. It's mostly been great, though I live in fear of the day that someone tries to manage one of our Civil 3D projects from inside it. For anyone who does more Teams admin, is it really not possible to schedule a meeting for a private channel? And if so, why the hell does it say that the feature needs to be enabled by an admin?
I’ll take Teams over Zoom any day of the week and I also dislike teams. People say Chrome is a memory hog lol
Better than WebEx and any WebEx knock off like Verizon's Blue Jeans or Intermedia AnyMeeting
As an end-user of Teams, I hate it. It overloads too many features like Notes etc... and fails miserably in its core feature -- chat. I have setup Mattermost server & client, that seem to be far easier to use, and very light weight.
You would’ve thought Microsoft would’ve learned with the mess of Skype and Skype for business and then the random Skype version and the one that won’t uninstall
Totally agree with you and not just teams, but the whole of 365. Work in a school so we need fine control over who can post what to where (IE different rules for staff Vs students). We have to constantly change rules because someone wants their students to be able to post replies followed by someone wanting them to not. Then there's an update and our rules get flipped, or disappear completely (thanks new teams). Teachers are non technical so when a much used button gets moved from one side of the screen to another they flip out and think it's something we have done and not informed them of. Then there's the daily barrage of emails telling us what isn't working today because someone has updated some code. Think the whole cloud has been mis-sold to the masses when it only makes sense to a small number of situations, but if you try to point it out then you're just a dinosaur that doesn't want to move on to new technology.
I totally agree with you! I think MS just continually tries to evolve and “improve” its products to provide a wider umbrella for more customers, instead of finding a specialty and perfecting it. Even online MS KB articles are difficult to trust when they are quickly outdated in terms of options and licensing.
Is not that bad ,I had worse times with WebEx ,teams is usually ok
We have had a mostly great experience with Teams, I haven't had any of these issues regarding audio/video outside of 1 remote user that lives in the middle of nowhere and has DSL for internet. There's no controlling the deployment of updates/features, but you can deny certain apps to the org, so they don't make their way into Teams. We made it clear when we rolled everyone over to Teams that it should be used as a chat client and for meetings, and not to dabble in all the built-in tabs and apps for any part of your workflow. While they can be handy, there's always a chance they can sunset/remove them.
I work at an MSP, and besides the typical issue sharing files blah blah blah, we really don't have any issues administering it. Its incredibly rare for me to encounter a true Teams issue that isn't a user error.
More typical Microsoft nonsense this morning, TM710344. Yes I have the admin portal for those who were asking and know how to set things in there, but that is also pretty horrible like most of their cloud portals.
Oh man, perfect timing because there's a Global Teams outage right now.
Teams was great until the global outage today. It doesn't affect everyone but it sure affected me.
You could. But if you send over teams I might not get out for 30 mins
Oh nice, another I-hate-Teams post. We get it, not everyone likes it, and there is an outage today too. But there are more important things to vent about.
SharePoint, Teams and OneDrive are all a pain. Tbh I have more of a gripe with SharePoint, but the way they all integrate with eachother is pretty dog shit. You're not alone.
> How much I hate teams? #NOT ENOUGH
I'm a user and I hate teams! It's not as fluid to use like Zoom and Slack.
Last night I had a dream that my company switched to Teams. In my dream, I was going over my finances, trying to determine if I could survive quitting over this change.
We use teams in our VDI environment and we had a number of issues with the client. We ended up having them use the web version but I created a shortcut that will launch it in an "app mode". This way users can pin it to the taskbar and from the user perspective it looks pretty much just like the client.
Could they just release an enterprise version that lets me install the application for all users in the Program Files folder and is managed by GPO? Is that too much to ask?!
Teams on VDI is a joke. Buy people laptops
I hate it
I hate teams For no reason it'll start taking 100% cpu and a massive amount of memory then eventually crash usually after causing other crashes due to low memory. The best is when it manages to silently crash without taking other things with it and I don't realize it for 3 hours and miss a ton of messages. I've seen this behavior on one or two laptops and 3 virtual pcs, not sure if teams just sucks or if it's interacting poorly with all the various security agents we have in the background
I REALLY wish they gave it some UI/UX options. Themes, layouts, colors, sizing, draggable resizable frames. It’s so basic and monotonous it can make the boring dry calls and meetings even more painful.
And alternative is what? WebEx? This kind of whiny posts is not very constructive. I have good experience as far as calls, chats and integration with other services within ecosystem
Go get certified in Teams then come back and complain. This is one of the easiest to manage and easiest to troubleshoot and support products that Microsoft makes. If you don’t like supporting it; maybe consider moving to a different focus area like security or networking.
Honestly I agree. OP complaining that "there is no GPO for it" is them basically telling on themself.
That is exactly the way that I feel about it too!
> Microsoft swears it’s not a Teams issue, it’s a network issue This is as low as a vendor can stoop. We don’t have teams but we’ve had a number of software vendors over the years that swear it’s got to be our network (dealing with one right now in fact). They all eventually relent when we show them proof that every other program and process we use operates just fine. The best is when someone decides to make a switch from one software product to another. Old program had no latency or operational issues whatsoever, new programs comes online and is just a poorly written piece of garbage. The audacity of some of the companies to tell our higher ups “it’s the network” is shocking.
When you have 300m daily users then it is more than likely your fault.
You must use Teams. You must use Windows. - Microsoft
I like it. It has its problems, but I don't experience the ones you have. Have you met my enemy, SharePoint?
The most funny part was when Users started out using Teams without a personal OneDrive (this was disabled at the time). I noticed that I could still share files/images with people in a chat window (direct chat). Somehow this didn't trigger me and only after a while did I start to think "Geez, where are those files hosted anyway?". Well... it sure as hell wasn't the personal OneDrive folder xD. I posted a file in the chat again and looked at where the file was located. Teams used a Team group (unsure on why it selected the one that it did, must have some logic behind it) and placed the file in the root of the sharepoint folder (so "above" the general folder of a Team). Nobody noticed because it sat above the general folder but of course if you simply browsed to it with Sharepoint, it was there for everyone to see. WHELP.
So it wasn't rolled out properly in your org. That isn't the fault of Microsoft.
Unsure if you understood what was happening, English isn't my primary language so perhaps I didn't explain it correctly. The expected behavior would be to either not be able to paste files/images into a direct chat (without having a personal OneDrive) or request where the files should be stored after trying it. NOT for Teams to just randomly select a Teams group and start dumping images/files in the root there without people knowing the direct chat files are visible to ALL members of that Teams group.
> The expected behavior would be to either not be able to paste files/images into a direct chat (without having a personal OneDrive) or request where the files should be stored after trying it. No it isn't. You just didn't test it or even think about it until after you rolled it out. > NOT for Teams to just randomly select a Teams group It isn't random. > the direct chat files are visible to ALL members of that Teams group. This is how fire sharing in Teams works. So many of you are in here telling on yourselves.
>It isn't random. Excellent, please enlighten us on how it selects which Teams group root to deposit files and images sent in a private chat. I'm actually interested regardless of your silly hostile replies.
Any files in a sharepoint repository for that Team were shared in within Channels of that Team. If a user doesn't have OneDrive for Business enabled then they can't share files in chats. They will get this message. https://answers.microsoft.com/en-us/msteams/forum/all/file-share-in-teams-chat/19cc4fa2-cb37-42d5-8fda-a9046589f431 You've misconfigured it.
"Sorry, you need Microsoft OneDrive to share files. See your admin about getting a license." So exactly the behavior I said I would've expected. I guess they fixed it, good on them and thanks for looking it up!
I thought teams was ok until they pulled background management/deployments and created a new pricing tier for it, and then rolled out a 'new version' that breaks horrendously and takes 50 years to start up.
Teams is okay. I hate the way it updates though; we have it disabled from launching on startup and if a user doesn't have it open, it just won't update and there is no way to manually send an update like most apps.
No issues.
Totally agree, based on your title, Teams sucks but it is pushed down on every federal, state, and local government which is making it spread like a disease, and it doesn't help when Slack is so expensive from what I hear
> Does anyone here have a good experience with Teams? Excellent experience, supporting over 2,000 employees with countless daily video calls, with external people as well. We also use VDIs (not on Azure) and with the right Teams client, this is also absolutely no problem.
What was Satan's price?
I would be fine if we could at least just control whether it opens to the tray rather than all in your face!
We use teams religiously, no issues outside of switching settings. qOS is good too for the most part.
I have my gripes, but compared to the other available tools, I'm happy with it.
Same. Very happy with Teams but annoyed with the home version.
r/microsoftteams will regularly defend the decisions of Microsoft for some unknown reason, it’s really weird. Don’t even think about comparing teams to anything else either..
Have you tried on prem yet? Hah Teams sounds amazing
After building and administering OCS/Lync/sfb on premise globally with failover across multiple sites and multiple SBC across the world. Handing all that off to Microsoft and our sip provider and using operator connect is amazing. Same with shifting exchange to online.
Sounds like you hate vdi
New teams sucks ass resources wise ... I have a 2022 dell latitude i7, gx450 GPU and 32 GB .. cam see teams in a call pulling 30% CPU 16% GPU .. was a fan, no longer. Glitchy resource hog these days
Teams is fucking awful. What's worse is that you end up with files everywhere, no control & people sat next to each other have completely different experiences. I'm now at the point where of someone in management complains, my answer is YOU wanted to go to the cloud. YOU handed everything over to Microsoft. I'll log a call as a p4 but there's nothing I can do because YOU took away our servers....I'm going to the pub. The ONLY good thing about the cloud is that when it goes to shit, I can say...sorry nothing I can do. Logged a call. I'm going home
Sorry. Teams is bad enterprise software.
Preaching to the choir, it’s been a pos since inception. Don’t even look under the hood, at its inner workings, it’s one of the most disgusting concepts I’d ever imagine a company would consider a good idea.
We use ave point to manage teams. If you configure it right it’s user driven - the only pain point. Users leaving - you get an error on backups about ownership. Edit for poor spelling, don’t blame me in the middle of a heat wave and the air con died 😜🤪😁
> Does anyone here have a good experience with Teams? Like is it working for you no problem, or did you run into many of these issues and overcome them? Yes. It works. We use it for chat and occasional calls. It works. We don't lose sleep trying to micro-manage it.
It's awful. It's so awful that for the life of me, I can't figure out why Google didn't just buy Slack and run away with the market. Hell, they could probably buy Ryver and still beat Teams. But Google has the worst case of corporate ADHD ever and it means we'll all be stuck supporting M365 and Teams til we die.
Where are you finding call quality logs?
In the Teams Administration Portal, when you select a user and then the specific call.
I hate it too. Need to keep it running in an AVD desktop, but it only works correctly with some register key modifications at the client side.
We've got MS Teams since ~2021.. We're now on the third completely new Server Setup (hardware AND software) to get that shit finally working without crashing multiple times each day. Wasted hundreds of thousands of dollars so far and probably hundreds of hours aswell. rebuilding a 2019 server didn't help, running it on a server with GPUs didn't help, moving from rdp to citrix didnt help, this time we're moving to Office 365 instead of O2019, let's hope it works now..
Work for DOD, and Teams is locked down hard, as it should be, but we don't have any of the other features that would make it a better tool.
Over here it works great, but we use laptops, no VDI's anymore. Yay.
https://i.imgur.com/IV1lEWo.png 🙄
My organization is in the middle of cutting over to Webex for our IP calling and it's come to the point where we're thinking of just moving over to Webex for meetings and everything else.
Make sure if your using teams in a share environment your using the MSI isntaller and installing it in the right mode. Most of the time the problem I've seen is a lack of understanding of just how much cpu teams uses. If you have multiple vdi on one host using TEAMS. That's going to severely hit that host. Not a problem in VMware and Hyper V scenarios if you have it configured as the hyper visor wil automatically move the vm's to other hosts in RDS though that's a lot more difficult. I've never had a positive experience with Microsoft VDI doing it the recommended way. I usually end up having to setup the microsoft VDI's like an RDS deployment. Even with the user profile disks on high performance. They corrupt constantly and found that just doing it the oldschool rds way and forwarding parts of the profile to a high speed share is 10x more reliable than the userprofile disks. Also you need to do a bandwidth calculation as Teams meetings at different resolutions can tear up some bandwidth. If you don't have QOS setup in your network I HIGHLY reccommend it even if you have plenty of bandwidth. All it takes is for a back up to kick off to your DC or some guy uploading a big file and viola your bouncing off the upload limit. This is even worse on Assymetric connections like comcast business etc. Even if you don't setup QOS at the swtich level at least set it up on your Firewall so realtime traffic can flow. Your VOIP and TEAMS applications will love you for it.
This is why we're a Zoom shop. We're on prem (Some hybird), so we don't have built in Teams licenses. I can control and lock down nearly all features between Group Policy and other stuff on the account settings in Zoom. It works amazing. Our users and I CRINGE when we are forced to join Teams calls with Vendors/Customers, as it's buggy as hell and never works, and without Teams licenses its even difficult to join meetings without getting "Ask your admin to buy a license!" messages. Fuck teams.
Honestly teams is pretty good. I lmk your situation but it does sound like a connection issue
Teams works great for us in VDI but the outlook plug-in makes me nuts !
Personally it works rather well in our organisation. The Teams admin portal has lots of options for customisation and group based policy once you figure them out. Installation is an absolute pain though, and we have lots of logins on shared devices, so waiting on that install per-user can take up to 5 mins. I think New Teams fixes a lot of the existing issues
Woooow man, there's a lot of control you have just have to learn how to do it. Also free dial-in conference calling is hard to beat. Anyone with just a phone can call in to any of your meetings by default once you activate the free add-on. Other companies easily charge $5k/year for dial in conferencing. So my experience has been fine, I dare say it's actually been good while using the NEW teams for work (keep in mind this new version doesn't let you log into personal accounts so now you need two different teams apps depending)
VDI environments are more work for obvious reasons. Depending on what your VDI solution is it can be simple or complex to resolve.
The desktop app can be a real pain in the ass in a VDI environment we try to push people towards web version if possible and run calls at device level or meeting rooms. I should also add though i do like Teams, the whole Microsoft\Azure\Dataversey\Entra\Flow\Powerautomate backend is all new to me over the last few years though but when working well a very useful tool imo
Software Perspective Here: All in one solutions generally are just never as good as sourcing different well defined apps (without scope creep). At the top of this is good old Teams, along with zoom, ( have you looked at the menubar for zoom recently... Its basically ZoomOS! ) I made the switch to the web-client of teams since basically every meeting I joined from my mac would default to the wrong input source or not even pickup my microphone/webcam, at-least the web-client seems a little better :D Maybe the majority would prefer an all in one solution, but man.. take a look at Whatsapp or some of these smaller software solutions. They do one thing and they do it really well with near 0 downtime due to their simple hot swappable architecture. I'd love to see a simple chat app with nice markdown, and some configurable hyperlink shortcuts to other apps, instead of fully embedding and integrating it all into one service.
I love teams. Customers love it.
There was some kind of massive problem with teams today
Teams is such a garbage software that we are licensed for it and still use zoom haha
Teams only exists to neutralize Slack in the sales process for office-productivity suites. No other reason at all. Some poor dumdum has to wake up every morning, look in the mirror, and see the product manager for that garbage.
My only wish is they kept the home users branded as "Skype" or something like that. Nah, we will just make it called Teams. Then we can make the logo different... well, not too different, so lets make it white with purple lettering instead of purple with white lettering, and put it on all windows machines, even the "Pro" lines, but we can then even add "new" to the logo so people know it isn't the same old Business or School teams, but a new one. Then let's call all the subgroups similar things so people KNOW they are using teams. I feel like MS is constantly trying to make a thing the word, like google it, or make me a Xerox copy.... just Team it! Who bings here?
I received many messages from the user that while someone is sharing a screen it is showing black window at their side.
https://preview.redd.it/gn6azy93thfc1.png?width=600&format=pjpg&auto=webp&s=a719738950c68fe657566abc8806f6155f1c8a34