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.
I'd completely uninstalled the old version before installing the new one, but I've just re-checked anyway. Under Driver Interface i see
Profile Version: 6
Installed system RAM: 8191 MB (load: 42 %)
FSLogix Service Version 2.9.8884.27471 Status: RUNNING
FSLogix Kernel Driver Version 2.9.8884.27471 Status: RUNNING
FSLogix Kernel Virtualization Driver Version 2.9.8884.27471 Status: RUNNING
so it's all at the correct version.
Regards
Ken Z
- Ken_ZMay 17, 2024Brass ContributorOK, 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.- hjmmmJul 23, 2024Copper Contributor
Same issue here on server 2019 + fslogix + new teams on RDS Server.
C:\users\Local_user1,2,3 keeps adding up numbers, user folders not deleted when signing off.
fslogix log show:
Error removing reparse point: C:\User\local_User\AppData\Local\Pacakges\MSTeams+8wekyb3d8bbwe\LocalCache
(process cannot access the file, because another process already uses it)
any ideas?
I have tried you suggestion and changed the redirections.xml not working.
- Ken_ZJul 23, 2024Brass Contributorhjmmm
have you rebooted the server after changing the redirections.xml file?
also, to confirm that it's the same issue, try completely removing the xml file from a test server so that it doesn't exclude any files, delete any vhdx files from your test account, and retry.
if the issue goes away, most likely you've missed an entry to remove.
Ken Z
- DanielL535Sep 06, 2024Copper Contributor
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
- aunabyNov 06, 2024Copper Contributor
Operasi