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_MACHINESOFTWAREPoliciesFSLogixODFCIncludeTeams

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:

does anyone have new Teams 2.1 working with FSLogix HF4 and single container profile?is ODFC required for Teams 2.1 to operate? If so is there any definitive MS documentation to say this as it seems rather vague and support are not giving us any further informationhas anyone got a stable non-persistent VDI desktop working with Teams 2.1 and FSLogix in general?

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)

​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-deployHKEY_LOCAL_MACHINESOFTWAREPoliciesFSLogixODFCIncludeTeams However we don’t use ODFC as FSLogix is in single-profile mode as recommended here… Configure ODFC containers tutorial – FSLogix | Microsoft Learn Using the ODFC container in a dual container configuration isn’t necessary or recommended.So my question is:does anyone have new Teams 2.1 working with FSLogix HF4 and single container profile?is ODFC required for Teams 2.1 to operate? If so is there any definitive MS documentation to say this as it seems rather vague and support are not giving us any further informationhas anyone got a stable non-persistent VDI desktop working with Teams 2.1 and FSLogix in general?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)   Read More

​