This message was deleted.

yes, although the defaults are very limited

I tend not to use many exclusions in my redirections.xml file when I configure fslogix as it kind of defies the point of using a profile container solution (Not file based like Citrix UPM or roaming profiles). The previous admin for this customer has put loads of exclusions in the current redirections.xml and I am seeing some weird app behaviour so thought as a test I would try a test server without it ( put a fake path in so it can't find it) so just wanted to know what happens if it can't find a redirections.xml I took a look here https://learn.microsoft.com/en-us/fslogix/concepts-redirections-xml#:~:text=User's%20Profile%20Location-,The%20redirections.,inside%20the%20user's%20profile%20container) and it suggests it copies the redirections.xml specified in the policy to the profile container in appdata/local/fslogix/redirections.XML so wasn't sure what the default behaviour is would it still be applying this or the out of box redirections.xml

Now you make me doubt...

yeah looking at the Fslogix log file and frx list-redirects its using a cached copy of the redirections.xml rather than a default one

This might depend on whether it’s previously found redirections.xml, as it’s copied into the profile container. I would assume it will work from its cached copy

@c4rm0 what do you mean by default one? FSLogix will always exclude specific folders as its part of the internal code. Redirections.xml never overrides that behavior. As you've found, the XML file is always copied from a remote location into the users profile. If the XML path changes and we can get it, we'll still use the XML inside the profile until it is removed (by an admin) or replaced. Still, all 'in code' exclusions will be in place.