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.
Anthony Lawlor commented
As stated nothing more to ask for as all comments say it all and agreed this will not work well with a large terminal server environments.
Please fix this folks. Our roaming profiles are instantly 1GB on a fresh(ish) user account when Teams has been used. The lack of an actual machine-wide installer is criminal given Microsoft's clear desire to oust Slack's stranglehold on collaboration in the developer and/or enterprise sectors.
To re-iterate, stuff we need if we're to promote its use:
1. Machine-wide installer in C:\Program File\Teams (or x86, whatever).
2. User settings stored in HKCU or AppData\Roaming
3. Cached content stored in AppData\Local (Or LocalLow)
4. AS AN ASIDE, more efficient processing. It hammers machines, which is terrible in a shared compute environment, such as VDI or RDS.
Nothing more to ask as previous comments say it all
How things should be, to support a real-world enterprise environment:
- Teams supports centralized installation and managed updates
- Teams cache is in %localappdata%
- Teams settings are in the Registry, in HKCU, or if they have to be file-based, in %appdata%
We're seeimg 300MB Teams data in %localappdata%, which includes the Teams install and can include a Previous folder with previous versions of Teams, making this folder grow to 600MB or more.
We're also seeing a Teams folder in %appdata%, containing Teams caching as well as user settings. This directory can grow from tens of MB to multiple GB, and roams by default.
THIS NEEDS TO CHANGE!
In a roaming profile environment (for instance, free seating or Citrix shared desktop with multiple servers), Teams settings need to roam. Also, to avoid asking users to reinstall Teams after every logon, the installation should either be centralized, or the installation folder should roam.
Conversely, the ginormous Teams cache should NEVER roam.
This means that the installation directory is in the wrong place (%localappdata%) and the cache is also in the wrong place (%appdata%). Not to mention the settings, which are in %appdata%, where the cache is also stored.
None of that makes any sense. Microsoft, your vision for the future of computing may be individualistic, with personal devices, but a HUGE part of the world works with managed devices and roaming profiles. Get with the program!
Sören Calvert commented
Me too, starting to Work with Teams and a Roaming üprofile with size limit. All Cache Files are under Roaming. Please Microsoft fixit asap, can't be a big issue?
Joar Guttormsen commented
How can this not be of the highest priority? It makes it imposible to use in an Enterprise enviroment.
Most of our users can't even install Teams much less run it due to the amount of space it requires in the roaming profile. Why isn't this a per machine install instead of a per user? This IS meant for an enterprise environment, no?
We have the same problem in our environment. Teams instantly bloats to upwards of 1GB in the roaming profile, which puts it will over the limit and the profile no longer syncs to the server. We've found no solution to this other than writing a short .bat script that deletes the cache folders that our employees have to manually run before signing out.
This cache should really be in \local\ not \roaming\.
Cache files should really be under AppData\Local, not AppData\Roaming. But failing that, give a setting or GPO to specify a different location for these folders.
Ditto....and doesn't seem to be much of GPO settings either.