Announcing general availability for FSLogix 2210 hotfix 4!

Is there any news on when there might be a HF5 that will hopefully address issues with the locking of Appdata\Local\Microsoft\Teams when using ODFC containers which prevents the users profile from being fully removed at logout?

ChristianJoham 

It has been awhile since I worked on this but I had a similar issue with teams settings not saving. If the user makes the setting changes they want and then exits teams (shut the app down completely) the settings saved. 

I had to do this to get dark mode to save etc. 

Let me know if that works for you as well.

According to others who have had the above issue the workaround is to delete Appdata\Local\Microsoft\Teams at logon before Teams is loaded.

I have carried out a quick test and have confirmed this appears to work.

My understanding is Appdata\Local\Microsoft\Teams is a symbolic link to the Teams folder in the FSLogix container?

Mine is empty as all the Teams data is going into the Teams_UWP folder in FSLogix so i assume deleting Appdata\Local\Microsoft\Teams won't cause any issues?

We seemingly have a different issue with non persistent Windows Server 2019 (Citrix VDA 2402 CU1 LTSR) desktops using UPM and FSLogix ODFC.

As soon as we enable "IncludeTeams" when users log out of their desktop session then their user profile on c:\ cannot be removed due to a number of locked files and folders.

These files and folder seemingly become locked as soon as Teams is loaded and then remain locked preventing the users profile from being removed.

If we do not include Teams in FSLogix and leave it just doing Outlook then there is no issue.

Can you please digitally sign ADMX files ?

We installed HF4 in our non-persistent Horizon 8 VDI environment.

Our users are now no longer getting their Group Policies when they log into their desktop.

No other changes to our environment other than applying this hotfix!!!!

Since we are rolling out FSLogix 2210 HF4 to our users we are getting complaints about the Files tab in teams being empty (blank screen). Repairing Teams fixes the issue, but it keeps getting back. The users that are still on HF3 do not have this issue.

Does anyone recognize the issue?

We've found that with the newer FSLogix 2.9.884.27471 (FSL 2210 Hotfix 4) that if our users attempt to add a network printer, they get an error message if they have an AppVolume attached.  As a workaround we can remove their access to all their Appvolumes and have them log out and back in and then they can add the printer.  The error is "Windows cannot connect to the printer. Operation failed with error 0x000005b3."  We can add printers without issue (even with AppVolumes) if we downgrade FSL to our previous installed version 2.9.8228.50276. 

Is anyone aware of a compatibility issue with FSL 2210 HF4 and AppVolumes 2111?  Is there a documented fix or workaround (maybe a registry edit like in some print issues for past versions).  We currently see this in any pool we upgrade to FSL 2210 HF4, so we've downgraded to our previous version for now, but we need to use the HF4 version to get New Teams to natively load and work correctly. 

Hello,

Every Citrix VDI restart, Teams show an error message ... do you have a solution ?

"We weren't able to connect. Sign in and we'll try again."

When clicking on "Sign In", no issue to sign but at the end a new error message appeared.

"Something went wrong. Error CAA90049. Session key is empty."

Regards,

I was able to solve my problem from yesterday, now Teams starts without any problems

(C:\Users\%USERNAME%\AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\* and C:\Users\%USERNAME%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\* deleted).

Unfortunately, I now have a new problem with Hotfix 4 (I don't have the problem with Hotfix 3). Teams does not save any settings.

Reason: The folder C:\Users\%USERNAME%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\ is missing. As a result, the file C:\Users\%USERNAME%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\app_settings.json is also missing.

If I delete my FSLogix profile and a new, empty one is created, same behaviour, app_settings.json is missing.

If I stop the FSLogix services and create a new, local profile, the app_settings.json file is created and Teams saves changes.

Does anyone else have this problem, does anyone know a solution?