Jul 18 2024 07:28 AM - edited Jul 18 2024 07:34 AM
Hi all,
We've been testing the latest Teams 2.1 Bootstrapper on our non-persistent Horizon VDI machines but having issues once we bring FSLogix into the mix.
We are able to deploy new Teams onto our base image and when using a local profile it launches and runs as expected from the shortcut in the Start Menu. Similarly on our physical PCs Classic Teams > New Teams upgrades without issue (we're not running FSLogix on physical machines... yet)
When logging in with FSLogix enabled (frxtray shows version 2.9.8228.50276) the Teams shortcut is present, however clicking it produces a white progress bar and no further action. We have updated our Redirections.xml to one we found here
Teams 2.1 with FSLogix setup guide – Jeff Riechers Technical Site
If we look at the properties of the Windows Store App for Teams it returns 16KB, which seems wrong? Looking in Event Viewer AppxPackaging log we see this error, can't find much online relating to it.
App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/manifest/uap/windows10/7 is inapplicable, it will be ignored during manifest processing.
I note from another thread that there's a GPO for ODFC called IncludeTeams that needs to be turned on to roam the new Teams cache etc.
https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\FSLogix\ODFC\IncludeTeams
However we don't use ODFC as FSLogix is in single-profile mode as recommended here...
Configure ODFC containers tutorial - FSLogix | Microsoft Learn
So my question is:
Any input much appreciated as it feels like we've hit a wall here at present. The MS documentation suggests Hotfix 4 is meant to be the supported configuration for Teams 2.x but struggling to find evidence of a working setup.
As an aside the reason we're running FSLogix in the first place is in order for OneDrive client to be deployed onto our non-persistent VDI machines as Microsoft don't support Roaming Profiles for this (which is what we used for roaming user data previously)
Jul 22 2024 06:35 AM
@gshawNCC
Hi, we encountered similar issues with Horizon non-persistent VDI, with existing profiles and FSLogix 2210 HF4...
We followed all the pre-requisites provided by Microsoft to switch to New Teams, FSLogix was already installed on our golden image with HF4, and with existing profiles MSTeams seems to do not correctly registered in the VDI session.
We tried to replace AppxPackages.xml file by a login GPO (using file generated with a fresh new profile) in %localappdata%/Fslogix, for some environment this workaround is working, for other one no.
It's currently a nightmare to manage this transition to new Teams...
The issue seems related to FSlogix, and nothing else.
Jul 24 2024 10:31 AM - edited Jul 24 2024 12:22 PM
we have frustration as well....users have to login every time the image recomposes. Definitely points to fslogix as the issue. Took it all the way to some fslogix team in Microsoft. they kind of washed thier hands of it.