Forum Discussion
Solved
2210 HF4 still broken on Server 2019 and new Teams
Hi Everyone, so, I assume everyone's been testing the new 2210 HF4 this morning/last night? I've got two Citrix Session Hosts, Server 2022 and Server 2019 Both of them have the latest FSLogi...
- OK, 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 also struggled over this but then i checked my FSLogix Installation with frxtray.exe
The Version that should be running is:
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
but why is it running the old Version 2.9.8784.63912 after the Update?
So i uninstall FSLogix and make sure that is no FSLogix in C:\Program Files and in ProgramData.
Reboot the Server and install the new Version of FSLogix and reboot again.
Now the new Version 2.9.8884.27471 is running checked with frxtray.exe
Hope this will help.
Hi Hans
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
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
- I've logged this with Microsoft today. The engineer who I spoke to says he's seen already seen this! and it's only ben 24 hours since HF4 came out.
- OK, 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.Operasi
