Forum Discussion
Force Teams desktop client update
I would suggest you check out the recently shared blog that explains a little about the update process at Why do I not see a feature but my colleague does? - Release Processes Microsoft Teams.
As explained it's entirely normal to have different versions while deployments are happening slowly, things are a little complex at the moment due to some delays, an apparent rollback and new versions through TAP and Public Preview. So if your users are guests in other tenants that may be in TAP you could be getting versions from there, I'm a guest in the microsoft tenant so my versions vary wildly.
As PDSDavid correctly explained the Machine Wide installer is more like a stub to create the installation for each user. Also the regular msi will be a little behind the newest version you may see, it trails rollout and doesn't lead.
It is quite unlikely that any specific build would cause the issues you describe, and that would seem to be largely verified by it remaining after a reinstall. I would be looking into driver versions perhaps.
Teams update process is unorthodox in enterprise, more like a consumer app, but this is deliberate from Microsoft to manage the far faster pace of change in what is really a web application in a wrapper. In my experience across Teams at many organisation it is very robust, the only issues I've seen are in locations where network restrictions are preventing access to the download service. Microsoft were planning to provide some more admin control, allowing you to control the day of the week and so on, but I think this has been pushed down the list due to priority works to support Teams being used by schools during the pandemic.
>It is quite unlikely that any specific build would cause the issues you describe,
>and that would seem to be largely verified by it remaining after a reinstall.
>I would be looking into driver versions perhaps.
It is *extremely* likely that a specific build would cause the issues I describe. Its called a bug. Thats why we update software. Its the principal reason for updating software.
Drivers being out of date is just being ridiculous. You can always say that about anything. Why would only Teams, not much more than an advanced chat app, be affected by this magic driver issue when all the other stuff, using more advanced system features, is stable. Also, in my own case I know my driver set is up to date as I do update whenever something is available. On a client machine it would be less often, but in my case its all up to date and Teams still crashes constantly with no log.
I'm basing this on supporting hundreds of desktops. If applications like Solidworks, office or the myriad of programming tools people use crashed, the users would be on the phone. They're not, but a lot of people do report that they missed teams chat messages because it was closed. Just Teams, which makes it pretty unlikely that all those desktops (with different models, different makes and different drivers) have issues which just happen to affect Teams and only Teams.
IanMurphy48 wrote:
It is *extremely* likely that a specific build would cause the issues I describe. Its called a bug.
However this forum isn't full of people reporting the exact same issue, and from your description no one is going to live with Teams crashing constantly. Microsoft also wouldn't leave people on a version with such an issue when they have newer versions either would they?
StevenC365 Given the long history of MS doing precisely that, my answer is a resounding yes. MS fixes bugs which affect a lot of people or which create a lot of noise. I changed nothing, but the Teams issue disappeared a few weeks later, without so much as a reboot (I rarely reboot)... so, yes, it was a teams bug fixed by a Teams update.... why couldn't I just have installed the latest version? Ah, yes, because the latest version is never available for download.
I currently have an issue at a client who is running office 2010 (still). All of a sudden some users have the Teams Icon in outlook, despite that not being supported in 2010. Some users, but not all, and I can't download the same version for everyone, so some people have the icon, some don't. Those that don't have it of course want to know why their neighbour is able to organise meetings from Outlook and they can't. All online help still says that this functionality does't exist.
Isn't this release policy just great...