mdrabble Posted December 14, 2020 Posted December 14, 2020 We have rolled out Office 365 Apps to our staff desktops including the MS Teams App. I use a redirected AppData folder to the users home drive. Noticed a sudden increase in the amount of storage being used on staff home drives and discovered that Teams is using an insane amount of storage in the AppData folder. AppData\Microsoft\Teams\Service Worker\CacheStorage Anyone come across this??
bezzoh Posted December 14, 2020 Posted December 14, 2020 Does Storage Sense not handle clearing this data out?
mdrabble Posted December 15, 2020 Author Posted December 15, 2020 Nope! Users cache storage folders were getting near the 1gb mark - that * 80+ staff and it zooms adds up - not to mention increased traffic erc
bezzoh Posted December 15, 2020 Posted December 15, 2020 Weird. I have it running daily on all my machines and it seems to be doing a decent job of handling Teams and OneDrive caches. OneNote used to be my biggest pain, but I've had a logout script just deleting all of that for a while now... I might not even need it anymore, but don't fix what aint broke...
dgsmith Posted January 19, 2021 Posted January 19, 2021 Did you get anywhere with this? Although I have tolerated it for some time, it's getting very frustrating now as the cache indefinitely sits in their network drive and doesn't budge or decrease! It wouldn't be too bad even if it cached to their local user profile as they're all using the same laptop (not roaming around).
mdrabble Posted January 19, 2021 Author Posted January 19, 2021 I ended up redirecting the AppData folder back to the local drive as it was getting silly with logon times and also the amount of storage it was taking up.
buzzard Posted January 19, 2021 Posted January 19, 2021 We stopped redirecting it to and then excluded the directories from roaming profiles to stop the bloat. We also had a startup script to clear the cache folders on c:\Users\*\Appdata\Teams etc of all the cache folders as they where filling with bloat from Teams. Not had any adverse effects yet! 1
mdrabble Posted January 19, 2021 Author Posted January 19, 2021 Must admit didn’t even cross my mind to use a start up script to clear the teams cache. May have a look at that when I come to roll out 20H2
sonofsanta Posted October 13, 2021 Posted October 13, 2021 We stopped redirecting it to and then excluded the directories from roaming profiles to stop the bloat. We also had a startup script to clear the cache folders on c:\Users\*\Appdata\Teams etc of all the cache folders as they where filling with bloat from Teams. Not had any adverse effects yet! Necro! @buzzard, did you have any negative effects from clearing the various cache folders? If not, can you share the script? Our 128GB SSDs are taking a hammering now from all staff profiles being 1GB+ thanks to these chuffing things. I wouldn't mind so much if the one supposed benefit of Teams installing into profiles--that it's easier to update the client--actually bore out, but we have just as many problems with some users' profiles getting stuck on months-old versions that no longer connect to meetings properly...
kennysarmy Posted January 19, 2024 Posted January 19, 2024 Necro! @buzzard, did you have any negative effects from clearing the various cache folders? If not, can you share the script? Our 128GB SSDs are taking a hammering now from all staff profiles being 1GB+ thanks to these chuffing things. I wouldn't mind so much if the one supposed benefit of Teams installing into profiles--that it's easier to update the client--actually bore out, but we have just as many problems with some users' profiles getting stuck on months-old versions that no longer connect to meetings properly... Thread bump but we're getting insanely huge AppData\Roaming\Microsoft\Teams\Service Worker\CacheStorage\ folders - some almost 3Gb. Did the script it was talked about sharing do the trick?
DaveTheTech Posted January 19, 2024 Posted January 19, 2024 Hi, I have used this on shared PCs. Have it run at boot: Get-ChildItem "C:\Users\*\AppData\Roaming\Microsoft\Teams\*" -directory | Where name -in ('application cache','blob_storage','databases','GPUcache','IndexedDB','Local Storage','tmp', 'previous', 'Service Worker') | ForEach{write-host Removing $_.Name; Remove-Item $_.FullName -Recurse -Force} Get-ChildItem "C:\Users\*\AppData\Local\Microsoft\Teams\*" -directory | Where name -in ('previous') | ForEach{write-host Removing $_.Name; Remove-Item $_.FullName -Recurse -Force}
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now