This message was deleted.

Unfortunately you can't exclude files with FSLogix

aah

exclude it from what?

well, redirections.xml is kind of excluding it from the container

This is all I ever used with Teams in Redirections.xml:

<Exclude Copy="0">AppData\Roaming\Microsoft Teams\Logs</Exclude>
	<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Application Cache</Exclude>
	<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Cache</Exclude>
	<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\media-stack</Exclude>
	<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\meeting-addin\Cache</Exclude>
	<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Service Worker\CacheStorage</Exclude>

I think the *.txt exclusion is a bunch of crap anyway

anyone has a solution for removing Teams cache paths from O365 FSLogix profiles? Looks like it doesn’t have GPO controls for that so only 2 options I could think of: 1 - clean them with logoff script. 2 - clean them with vhd compact script (we currently open, defrag and shrink vhds we probably could add some cleanup too). Another thing is - when you overclean Teams cache - it hits you on next launch, re-downloading everything and showing empty chats for a minute or so.

@Vadim Gonzalez Use Aaron’s Prune framework - and don’t stick teams in the office container 😬

Am I missing the point, but the point of the Office365 container is to hold the Teams cache (among other caches)? If you don't want it, then just don't include it via the policy?

If you put teams cache into Office Container, then you cannot redirect it out of that container. If you want to use redirections, you have to have the cache in the profile container

But if you put it in the container I'm assuming you wanted it in there?

its a common mistake that people put something like teams into the Office Container because its logical (which it is), but then they want to clear the useless shite out with redirections, and wonder why it doesn't work....Fine to keep it in either container, but if you want to use redirections, it has to be in the profile container

But it's all cache anyway, so just delete it if you don't want it

Yep, Aarons pruning method is the best path for that stuff, easy as pie

Or use UPM containers instead, I'm sure their exclusions are a bit more capable (although I haven't actively checked)

@James Kindon Thanks. Aaron’s script may be helpful. We actually use a modified version of the script to clean up our UPM files share once a week, but I’m not sure how running it in the user session would impact logoff time. There’s a story behind our current profiles/caches situation. We were using UPM profiles and were generally happy with them, but some “loud” people were not happy with the performance of Outlook in Citrix, comparing to laptops. Microsoft recommended using cached mode, so we decided to go for FSLogix 0365 profiles. There were several ideas floating around: 1 FSLogix profiles 2 FSLogix Profiles + FSLogix 0365 profiles 3 FSLogix 0365 Profiles + UPM profiles. we went with Option 2: However, we ran into some storage issues when testing FSLogix profiles. We have a lot of “low activity” users with very small UPM profiles (well below 100 MB). When we started using FSLogix profiles, each profile VHD was at least 256 MB. Additionally, FSLogix profiles tend to have a lot of white space and could grow to 5-7 GB, with more than half of it being white space. Considering we have 2k+ users, that would require way more storage than FSLogix O365 Profile + UPM Profile. So here we are. We have had a number of issues that were fixed by cleaning Teams caches (such as screen sharing and Citrix optimisation not working), but cleaning them all massively slows down the next Teams launch. Perhaps some maintenance (prune) clean up for O365 container could keep the balance between Teams launch times and IOPS hit and cache-related issues.

I took @Aaron Parker script and made a blog from it. If you are interested. https://blogs.mycugc.org/2022/02/04/how-to-prune-a-fslogix-profile/

@Vadim Gonzalez the hidden price of container tech... 🙂 Re Aarons script, you might get a slight hit the first time you run it (I am talking specifically about what Ray has above) as it will fix up the profile contents but its not likely to be huge. WEM, GPP, There is a few different ways to execute it with test users to get a feel for it. The pruning logic is nice because you have so much control on what you keep, and what you don't - pretty much do whatever you want

Added the script via logoff batch file. Modified targets file to check only Teams and Office files. Changed the log file name. (Added username) Takes between 300 ms local profile to 6 sec 0365 FSlogic profile to process if there is nothing to delete. I’ll test it further to see if there are any unexpected issues with UPM /FSlogix when you have this in the mix. So far looks like working solution. @echo off set ScriptDirectory=%~dp0 powershell.exe -ExecutionPolicy Bypass -Command “& ‘%ScriptDirectory%Remove-ProfileData.ps1’ -Targets ‘%ScriptDirectory%targets.xml’ -LogPath ‘\\afsprofiles\office$\_Remove-Profiledata’ -Confirm:$False -Verbose”

@Aaron Parker FYI