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 FSLogix installed, and they share the same GPO for the FSLogix configuration.
They’ve also got a common redirections.xml file for both Servers. Logging into a Session host creates both a normal profile folder and a local_<user> folder for redirected folders/files
For testing, I’ve been deleting the vhdx files between tests on each server, so there’s no potential issues using a profile container between the two different OSes.
Also, I’ve only got a single profile container configured – I’m not using an Office container
I’ve also got the latest new Teams installed on both servers. Server 2022 was installed via the bootstrapper and Server 2019 was installed via DISM as per the recommended method.
Server 2022 – when i log in to this OS using a test account configured for FSLogix, and start new Teams, everything is fine. When i log off, both the user profile and local_<user> folders get deleted.
Server 2019 – Doing exactly the same operation on this server, after starting new Teams, then logging off, the local_<user> folder fails to get deleted. The error message in the FSLogix operational logs are “Error removing directory: C:userslocal_<xxxx>AppDataLocalMicrosoftIdentityCache1UD…. The process cannot access the file because it is being used by another process)”
Note that the location under AppDataLocal… can change between different tests as there are a lot of different files locked and this is the first file FSLogix came across during the logoff process.
Running sysinternals Handle64.exe shows that the files are open by “System” (pid = 4)
Also, I can’t delete the folders manually as administrator after the user has logged off either, unless i reboot the server.
This issue only occurs after I’ve run new Teams for the first time. If i start clean without a profile container, log in, start Word, Excel, Outlook, etc, but don’t start new Teams, the issue doesn’t occur. Once I’ve started Teams, even if i shut it down, the local_<user> folder can’t be removed/deleted.
Anyone else experiencing this?
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 2019Both of them have the latest FSLogix installed, and they share the same GPO for the FSLogix configuration. They’ve also got a common redirections.xml file for both Servers. Logging into a Session host creates both a normal profile folder and a local_<user> folder for redirected folders/filesFor testing, I’ve been deleting the vhdx files between tests on each server, so there’s no potential issues using a profile container between the two different OSes.Also, I’ve only got a single profile container configured – I’m not using an Office containerI’ve also got the latest new Teams installed on both servers. Server 2022 was installed via the bootstrapper and Server 2019 was installed via DISM as per the recommended method. Server 2022 – when i log in to this OS using a test account configured for FSLogix, and start new Teams, everything is fine. When i log off, both the user profile and local_<user> folders get deleted. Server 2019 – Doing exactly the same operation on this server, after starting new Teams, then logging off, the local_<user> folder fails to get deleted. The error message in the FSLogix operational logs are “Error removing directory: C:userslocal_<xxxx>AppDataLocalMicrosoftIdentityCache1UD…. The process cannot access the file because it is being used by another process)” Note that the location under AppDataLocal… can change between different tests as there are a lot of different files locked and this is the first file FSLogix came across during the logoff process. Running sysinternals Handle64.exe shows that the files are open by “System” (pid = 4)Also, I can’t delete the folders manually as administrator after the user has logged off either, unless i reboot the server. This issue only occurs after I’ve run new Teams for the first time. If i start clean without a profile container, log in, start Word, Excel, Outlook, etc, but don’t start new Teams, the issue doesn’t occur. Once I’ve started Teams, even if i shut it down, the local_<user> folder can’t be removed/deleted. Anyone else experiencing this? Read More