Forum Discussion
Teams that came with Office 365 package does not auto-update
Hi, I deployed Office 365 with Teams via SCCM Application Client deployment using Semi-Annual Channel Target installer. I noticed that Teams do not auto-update. What do I do to make Teams aut...
If we're deploy Teams with O365 (via Intune) Teams Desktop client comes in an old version and seems not to update itself. We're not GCC...
Only if I click on "check for updates" self update seems to be initiated.
What's the sitiution right here?
Only if I click on "check for updates" self update seems to be initiated.
What's the sitiution right here?
Here's what I found. For Autoupdate to work, first, the user needs to be logged in to Teams. 15 minutes after the user logs in, Teams will check for updates in the background. After that, the update will only apply if the user is logged in and idle for 30 minutes. In other words, If the user keeps signing out after use or not idle in Teams and computer for 30 minutes after the 15-minute check (total of 45 minutes), the update will not apply. Even if you are not using Teams for 30 minutes, but if you are actively using your computer, it won't auto-update. Knowing this timing helped me understand the problem we had.
- I have the same experience (and it is already 2023). I think, it is because the O365 App package came with Team with the core version (not updated), and it relies on the auto-update to get to the latest version. For example, if I image a computer now in our environment, it will get Teams from the Office 365 App package but I will get a message that Teams need to be updated. If I leave it as is, and after some time, Teams will eventually be up to date and will let you in.
But why Teams (installed within M365 Apps) initially comes in an old versions?
