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.
adding onto annon below, untested but should delete any cache older than 7 days.
forfiles -p "$env:appdata\Microsoft\Teams\Logs" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
forfiles -p "$env:appdata\Microsoft\Teams\media-stack" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
forfiles -p "$env:appdata\Microsoft\Teams\Service Worker\CacheStorage" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
forfiles -p "$env:appdata\Microsoft\Teams\Application Cache" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
forfiles -p "$env:appdata\Microsoft\Teams\Cache" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
forfiles -p "$env:appdata\Microsoft\Teams\GPUCache" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
forfiles -p "$env:appdata\Microsoft\Teams\meeting-addin\Cache" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
forfiles -p "$env:appdata\Microsoft\Teams\*.txt" -d -7 -c "cmd /c IF @isdir == TRUE rd /S /Q @path"
We ended up just creating a simple PowerShell logoff script in our environment:
Remove-Item "$env:appdata\Microsoft\Teams\Logs" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item "$env:appdata\Microsoft\Teams\media-stack" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item "$env:appdata\Microsoft\Teams\Service Worker\CacheStorage" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item "$env:appdata\Microsoft\Teams\Application Cache" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item "$env:appdata\Microsoft\Teams\Cache" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item "$env:appdata\Microsoft\Teams\GPUCache" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item "$env:appdata\Microsoft\Teams\meeting-addin\Cache" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item "$env:appdata\Microsoft\Teams\*.txt" -Force -Recurse -ErrorAction SilentlyContinue
It's been over 3 years and MS has not managed to change a cache folder path from %appdata% to %localappdata%.
Get your act together before promoting Teams as communication tool for enterprise.
Austen Lowe commented
1 hour login times over the Wi-Fi because teams cache folders are massive (15GB in one case! mostly 7) is not an acceptable use case Microsoft!!! Operational issues should not be on backlog, they should be at the forefront instead of faffing around with colours and other useless features fluid components, pining chat to name a few, Lazy company.
Samson Wu commented
Teams developers, and the project leaders, Do you job to fix it!!!!!!!
Teams is the number one reason my roaming profile is so huge and it upsets me.
So if I'm correct two years and four months later it has been put on the backlog, which is already an absurd amount of time for a problem this big.
And this still isn't fixed after beeing on the backlog for seven months.
Please fix this issue.
Nalin U commented
This is to the MS teams developers. I give a below an extract of an email from my Head teacher in our school about MS teams experience.
"There is a real problem with MS Teams at the moments which has ruined my last two assemblies. (I want to do a live assembly with one form whilst on Teams to the others). MS Teams is a problem – it hangs, so I try again and it hangs again, so I sign out and reload … and it does not reload. Then the sound does not work with the videos even when we change the settings etc. etc. Other staff are having similar problems.
Please can someone do some maintenance work on Teams."
Her MS teams was frozen and no amount of restarts worked. The school has a 1Gbps connection to the internet which is not maxed out.
What does the MS teams team propose to fix this? I understand these files will build up and the need to have these files somewhere. But if they are not needed after a session can they not be cleared up? Just like when we clear a mess when create one in real life?
+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.**