Elastic layers. Contemplating using them for the first time, but now that teams needs to be in the OS layer it makes Elastic Fit tests for app layers throw errors. What's the guidance here now?

Teams does not need to be in the OS layer, we still have it in an app layer. But in order to get it to work we also have a scheduled task that runs when the server has started that registers Teams.

"WS2022 and W11 multisession OSes: There are three options to install Teams • Use UPM/CPM and let it manage UWP apps (a GPO setting) ◦ https://docs.citrix.com/en-us/profile-management/2402-ltsr/how-to/enable-new-teams-roaming.html • Use the latest FSLogix release, and expect to not see MSTeams in the start menu on the very first logon of a new user. It should work after the initial logoff completes. • Install MSTeams in the OS layer ◦ This will not pollute other layers noticeably because MSTeams operates on a per-user basis"

Our strategy when it comes to troublesome applications is to recreate the app layer every time we install a new version, that way we know for sure that all old stuff is 100% gone. Teams absolutely belongs in this category. The only thing that is certain is that you will run into problems with Teams regards of how you choose to install it 🙂

That is a given, teams has never been easy. But i'm trying to avoid having different build methods for each OS just to support MS's shitty messaging app. So we have it in the OS layer for the Server OS and the Workstation OS.

Hi all -- I recommend taking a look at this KB re best practices for Teams + AL as well: https://support.citrix.com/s/article/CTX692020-new-teams-deployment-guidance-for-app-layering-or-user-personalization-layerupl .. also, in the latest release, if elastic/user layer/UPL are enabled for the image, we will proactively register Teams for the user when they log in. This should mean you don't need to do that step via script @Lennart Hermansson if you are on the latest release.

That is the same article i have been working with for some time. But it does not answer my question.

ok, glad you are aware of it. Yes, we also observe there are chronic differences in how Teams/AppX apps work across the Windows variants. App Layering doesn't/cannot do anything to change how any app interacts, or does or does not support running in the OS. While I wish that were better/easier (as it causes us significant pain as it does you), it is not something we have any control over whatsoever.