Frequent mistakes by multiple users occur in Citrix LTSR 1912cu5 when using Microsoft Teams.
Frequent mistakes by multiple users occur in Citrix LTSR 1912cu5 when using Microsoft Teams.
Microsoft Teams presents challenges, and it’s frustrating we’re relying on the web version now. Our main aim is to ensure the app runs smoothly. Because of incomplete persistence, proxy configurations, blacklists, security rules, and Azure restrictions, pinpointing the exact cause remains difficult.
Current steps: We’ve created a script that removes files outside a designated folder—specifically targeting issues seen in logs like "desktop-config.json", "preauth.json", "settings.json", and "storage.json". This folder is being synchronized via FSLogix, aiming to store user data and files on our servers. However, this process occurs before shutdowns, causing Teams to start fresh each day. It’s resolved about 80% of cases before they arise. We’re also manually purging files one by one, user by user, to maintain progress. The files currently removed are shown in the attached image.
Looking ahead: I’m unlikely to share full logs, but initial theories suggest WAM fails to log in, triggering a fallback to ADAL and occasionally launching the app. The recurring error code "80070003" is puzzling, and I’m unsure if it ties to our firewall. This isn’t something I’m comfortable discussing publicly, as it relates to our internal operations.
Thank you all for your support over the years, active or not.
Teams on VDIs presents significant challenges. Here are my questions: Are you utilizing the machine-wide installer? Have you disabled the "Allow my organization to manage my device" setting in the registry? Based on our testing, it seems you can't have Teams data stored solely in each user profile rather than on the machine itself, even with the machine-wide installer. We're leveraging FSlogix for user profiles to ensure data consistency across all VMs, though it remains somewhat unstable. The "Allow my organization to manage my device" fix has largely resolved our issues, but we still encounter occasional problems requiring full profile wipes. If you manage profiles, consider incorporating Teams folders into the profile container.
We are employing the machine-wide installer for both /ALLUSER and /ALLUSERS settings. I haven’t encountered the registry yet, but I’m looking for the correct path. Since I have a faulty setup, testing is important. Appreciate your help!
Registry entry located at HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin. Value set to 1 prevents the "Allow my organization to manage my device" option from being enabled. This setting is configured in the MS Office GPO for users accessing our VDI farm, which uses AVD instead of Citrix.