This message was deleted.

Did you read the section where it defines the changes to the profile regarding what needs to be persisted and excluded? https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#profile-and-cache-location-for-new-teams-client I removed the \AppData\Roaming\ Teams entries from the redirections.xml and am going to test adding in these new entries Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Cache/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Service Worker/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage/Exclude

Thank you for the information. I did see that. I was wondering more along the lines of whether the change in location will result in the Teams 1.0 data remaining in the profile resulting in wasted storage. I assume it will, and will need to be cleaned up with a script.

It will remain there from what I have witnessed and had to script a clean up.

The data for Teams 1 isn't cleaned up as a user could switch back to Teams 1. We have been tirelessly working on getting a new release for Teams 2, but there are some significant issues with Server 2019 we are still working to understand. All the FSLogix changes seems to be working as intended, but there are some nuances to UWP on 2019 that the other teams are investigating.