Forum Discussion
Staff receiving updates to Teams at different time periods?
- Hi Toby McDaid,
The following article outlines the updates to Microsoft Teams clients
https://docs.microsoft.com/en-us/microsoftteams/teams-client-update
It is pretty obscure outside of the fact it updates automatically or that users can trigger the update process through the client (via the menu). In most cases, I find the experience to be similar to yours - it can be sporadic so it's worth ensuring that users manually update their Teams client periodically. The web version (teams.microsoft.com) updates automatically and the mobile through the regular store updates which depend on the phone settings.
Good to know that Microsoft are working on the ability to let admins manage updates to the Teams client for their users - hopefully this will ultimately fix this kind of issue
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18738943-let-admins-manage-updates
I have voted on it, and would recommend you do too as when it is completed it will notify you.
Hope that answers your question
Best, Chris
The following article outlines the updates to Microsoft Teams clients
https://docs.microsoft.com/en-us/microsoftteams/teams-client-update
It is pretty obscure outside of the fact it updates automatically or that users can trigger the update process through the client (via the menu). In most cases, I find the experience to be similar to yours - it can be sporadic so it's worth ensuring that users manually update their Teams client periodically. The web version (teams.microsoft.com) updates automatically and the mobile through the regular store updates which depend on the phone settings.
Good to know that Microsoft are working on the ability to let admins manage updates to the Teams client for their users - hopefully this will ultimately fix this kind of issue
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18738943-let-admins-manage-updates
I have voted on it, and would recommend you do too as when it is completed it will notify you.
Hope that answers your question
Best, Chris
Glad to know I'm not the only one experiencing this issue. It's definitely a minor problem for the time being, it's just made life difficult because I can no longer inform staff about new Teams updates as there's no guarantee they've actually installed the update.
At least they are working on it, I have added my vote also.
Toby McDaid there is a degree of randomness deliberately to avoid you have all your client download an update at the same time, and making your network upset. I imagine it's like Office updates, Microsoft define a %age of client they want to upgrade and each machine picks a random number, if it's less than the percentage they take the update, if it's more they don't. After a few days Microsoft move the %age higher and the next client pick it up.
Yes it makes it hard to say when something it there, I always just give a likely window e.g. over the next 2-3 weeks you'll see. Secondary ringer is new, only jsut started rolling out.
- It would be great if the documentation would reflect your knowledge to better inform administrators - maybe you could login to docs.com and amend the article?
It will be great when admins can manage the updates and servicing of the clients - would hope to see deployment rings and something like targeted/standard release. It would also be interesting to see if this would be via the TAC or also possible in Intune/Config Manager too. If you know more about that would be good to know too 😄
Best, ChrisChrisHoardMVP There is nothing you can or should change about the process, it's controlled by Microsoft. If they did allow some admin control then people would opt out, defer etc. Microsoft would have to develop knowing the client could be any one of hundreds of different versions, making testing expensive and slow. All in everything would grind to a snails pace. Instead they use a similar process to Chrome, Spotify and dozens of other consumer apps.
The updates are performed using Squirrel, which is open source and documented here -> https://github.com/Squirrel/Squirrel.Windows/blob/develop/docs/readme.md
