Forum Discussion
Solved
Force Teams desktop client update
Hi all, I've recieved several questions about this and I'm also seeing too many topics about it here in the community. We all know about the update process for Teams as described here https://d...
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.
ChristianBergstrom Yes the updates would continue, and Teams will offer you an update available to your ring with a higher version number, so effectively you will fall back in line with support from that point.
Teams updates are deployed on a percentage basis, first 10% and so on. This is both to avoid load at the Microsoft end and to allow rollouts to be paused if a significant support issues is created. I don't know but assume that is what happened in December, a versions was rolling out then deployments stopped. The point being the mechanism is there to protect people and the service.
PDSDavid I'm sure that Premiere will come up with a supported answer, that warning means you are reaching the limit, 90 days I think. If you just download the Teams client again doesn't that take you back to more recent version? You can deploy that however you like. Also if you look in the log you will see the URL that Teams is checking for a version (it looks a lot like those Bec is creating but with your current version number), if you log into Teams in a browser then open a tab to that page you might be able to see what in your infra is causing the block, the service will return some JSON if there is an upgrade, and the location the client should fetch it from.
Great! As I suspected. Really appreciate you getting back confirming. Thanks!