Forum Discussion
2210 HF4 still broken on Server 2019 and new Teams
- May 17, 2024OK, if anyone is interested, I got to the bottom of this issue. I had to remove the following entries from my redirections.xml file as New Teams was causing the system to keep the files in these folders locked after logoff. (This only occurs on Server 2019, not Server 2022)
<Exclude Copy="0">AppData\LocalLow</Exclude>
<Exclude Copy="0">AppData\Local\D3DSCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\IdentityCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\OneAuth</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\TokenBroker</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Caches</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Explorer</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\IECompatCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\iecompatuaCache</Exclude>
Once these were removed, the local_<user> folder was successfully being deleted.
NOTE this is my standard xml file that i've been using for years and hasworked without incident, and still works on Server 2022. Definitely an issue with New Teams on Server 2019.
Note the LocalLow was removed but it was only a couple of files in the Microsoft subfolder that was causing the issue.
<Exclude Copy="0">AppData\LocalLow</Exclude>
<Exclude Copy="0">AppData\Local\D3DSCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\IdentityCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\OneAuth</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\TokenBroker</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Caches</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Explorer</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\IECompatCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\iecompatuaCache</Exclude>
Once these were removed, the local_<user> folder was successfully being deleted.
NOTE this is my standard xml file that i've been using for years and hasworked without incident, and still works on Server 2022. Definitely an issue with New Teams on Server 2019.
Note the LocalLow was removed but it was only a couple of files in the Microsoft subfolder that was causing the issue.
so this issue seems to be well known to Microsoft already?
Sad that they did not update their knowledge base having this noted as a known issue
as someone already mentioned. Disabling the redirections.xml fixes this issue but profiles will be bloated then, so thats no option, or does anyone get it work with other redirections.xml settings?
- Ken_ZSep 06, 2024Brass Contributor
the primary Microsoft article for deploying new Teams in VDI/Session hosts had been updated near the end of July to include additional requirements for roaming. Please see
- DanielL535Sep 06, 2024Copper Contributor
I have it working at another customer with same exclude/include set but have no clue why it does not work at a specific customer
<Exclude Copy="0">AppData\Local\Packages\</Exclude>
<!--Microsoft New Teams-->
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs</Exclude>
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLog</Exclude>
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage</Exclude>
<Exclude>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\GPUCache</Exclude><Includes>
<Include>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\</Include>
</Includes>So redirections.xml should be correctly configured