Teams Windows client greatly increases roaming profile size (Appdata\Roaming\Microsoft\Teams)
On Windows, Teams is available as an end user self-install app. The app installs to AppData\Local, so not part of the roaming profile. However, it stores LOTS of content in AppData\Roaming\Microsoft\Teams.
Our organisation uses roaming profiles and profile size policy; users are beginning to exceed a [very generous!] limit, and Teams is a big cause of this.
Thank you for your feedback! This is our on backlog, we will share an update as soon as one is available.
+1 for fixing, soon 2,5 years passed since this issue has been reported. This will be "wonderful" issue after people will come back to office after covid restrictions. I have already seen problems with this, GigaBytes of space and thousands of files syncing to server. At the moment I go the GPO tweaking and excluding the folders.
+1, please fix. While we have implemented specific Group Policy restrictions to not sync the Teams Cache location this is not ideal. Teams should not be storing up to 17GB of data in any scenario.
Any update of this bug ?
+1 please fix, this is very poor.
+1, any news?
I agree. Using roaming profiles this is not useful.
It¨s a simple issue to fix - Use Linux clients. Better still - LINUX based Thin Clients and the LINUX version of teams, that run from RAM. We did this last year. Saved 1000´s - zero help desk calls either. Using solution en WAN (home office) and LAN environments.
I do not recommend booting the Thin Client from USB - you'll burn them out.
NEVER install teams in the server. And BLOCK the install.
Don´t use teams in Windows based domain clients either.
This is becoming quite the issue in a Terminal Server environment (persistent). Put 15 users on a TS and Teams will fill the disk with cache files. No need for this.
We also have this issue with all of our customers who use MS Teams.
Christine Ayre commented
We have multiuser pcs with small hard drives which due to this issue are now being filled up and become unusable. Please get this sorted asap, or at least provide an update/timescale as to when it may be fixed, and a work around would be helpful too.
great issue in our organizazion, you need to fix this ASAP.
Ms teams and roaming profile workaround
This is what I found works well for us on windows 10 roaming profiles.
Using GPO to exclude the following from the profile.
User configuration>Administrative template>system>user profiles>exclude directories in roaming profile.
After applying the exclusion place the latest version of ms teams install files in a central place that has permission for users to run the file.
Uninstall all versions of teams installed on every computer and then create a shortcut to the central file on the users desktop and tell every user to use that icon to run teams
**We also use a common desktop for every user in our roaming profile so we just have to place the shortcut on the common desktop and all users get it.**
This is getting even worse and worse instead of finding a solution to this issue. This is causing major issues in our environment with 200+ users. We can not expand the disk under the profile stores anymore. We are at the point when Teams data is more than actual user profile including redirected folders! After a Teams update 10s of GBs are disappearing within 30-60 minutes, it's just simply not acceptable.
Robert Holt commented
This is a real issue in our school. We don't have a good solution to it.
This issue is killing our user area storage, we cannot give ever staff and student member an extra 500GB of storage space. You are pushing the school to have to seriously look at moving away from Microsoft and Office 365 to your competitors, why can't the software use the local hard drive and Users folder on the desktop PC to run Teams rather than their network storage?
3 year old problem and Teams still spams roaming profiles.
Why does a program insisting on being installed in localappdata write to roaming in the first place?
Can not believe this has not been fixed yet.
Same dumb issue!!! Unbelievable...
Same issue - it should be completely optional where the application stores data - most of the data going into the /AppData/Roaming/Microsoft/Teams under the users roaming profile just isn't required (in this location). It’s crazy that after two years MS haven't resolved this obvious fault
David Broadley commented
I can't believe MS haven't fixed this yet. This is taking up lots of expensive enterprise storage. Why is the data not stored in local APP data where caches should exist.
There is no reason an app should have a cache that is roaming!