Let admins manage updates
For corporate use please let stop automatic updates and user side updates.
Admins can deploy updates in a managable way
We are exploring the best way to ensure users receive the latest improvements to Teams while providing admins with more manageability.
Ewald Bracko commented
The best way to achieve this would be to install Teams into the %ProgramFiles% folder in general. Create an enterprise-specific install for that if necessary.
Use the user profile folders only to store user specific configuration settings and user specific temporary data like cache files.
Create and install a system service that handles the Teams Update. The Teams update mechanism should be limited to updating the central installation folder only and it should be avoided to do registry manipulations, especially not within the HKLM hive of the registry.
The Teams Updater service should first download the update package locally. Then it should check if any instance of Teams is running and delay the update process in that case for some minutes until doing a recheck. Updates should be deployed only if Teams is not being used on the system.
That way Teams will be well suited for any kind of business environment, even RDS and Citrix.
This update issue kicked me from Teams during a meeting where we were looking at a planner. There was no evidence of what was happening, no notification, just disappeared and then restarted. Not really acceptable behaviour.
Teams can't just "decide" to auto update at will
Anthony G commented
this is normal with SAAS and the fact its really still in build
Keeps interrupting me by updating.
Tom Olin commented
It's been 4-5 times in less than 3 hours today. Please make it stop.
and for windows too.
todd jones commented
client runs in an RDS environment with 40 users. VDI maybe the next step. BUT since adding Teams a month ago, the update creates a storm of user activity since runs on each user session individually and slows the server to 100% usage. Be nice to find a solution that updates is managed and maybe after hours or weekend and not immediately at run time.
There is also a downside on the desktop app that when it automatically updates our antivirus blocks it and then we cant use it for a while until it gets approved, such a hassle.
Scott Yates commented
Please allow us to disable this while we have the app loaded. It is fine to update when we first load or we we choose to re-load the app, but not while we are in flow, and coding. It distracts developers and we lose time getting back into flow.
4-5 times a day, Teams updates which takes you out of what you are working on. It is tedious and unnecessary. These "updates" don't change anything noticeable and should be saved for the end of the work day, or at the user's discretion.
I has got a strong demand from our customers.Customer need client update manegement of Teams．
Craig Watson commented
having something like below would be helpful
1. set a random back off timer for when the update is downloaded
2. add a dns record to redirect updates to a server that has the new bits within the organization.
Noriko Yamashita commented
In the almost case of Japanese customer, they doesn’t separate their network for their core systems and communication infra etc. If some Office 365 teams update is hugged their network systems, IT admin is nervous to keep to use Office 365 due to no control and no estimated network capacity.
Kunio Sato commented
Customer need client update manegement of Teams．It is absolutely necessary for consumption．
Any time update kicks in it distracts my workflow by redirecting to the Teams window a few times during auto-update.
I wish to disable it but there is no option right now.
Please add an option to disable auto-upadates.
Takuya Sugiyama commented
If there are no function of client update management, company admins cannot control their network load or estimate network capacity.
So it would be great to manage updates like Office 365 ProPlus.
Ember Quill commented
Or at the very least allow us to schedule the automatic updates so Teams stops updating itself in the middle of the day while I'm actively using it.