New Teams not loading with FSLogix 2210 HF4, Horizon non-persistent VDI
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 Using the ODFC container in a dual container configurationisn'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 information has 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)
InstallAppXPackages not working (Microsoft Store, MSEdge Apps, AppX)
Running FSLogix version: 2210 hotfix 3 (2.9.8784.63912) The problem: Microsoft Edge "Apps" and apps installed through Microsoft Store (such as "TypeClipboard") do not persist after logoff on dedicated machines (assigned user always logs into same machine). Workaround: User must reinstall Microsoft Edge "Apps" and apps from Microsoft Store every time they sign-in with a new Windows session. Attempted solution #1: InstallAppXPackages=1 The outcome of attempted solution: Seems to be 100% ineffective, problem remains unresolved. I do confirm the `AppData\Roaming\FSLogix\AppxPackages.xml` file is being correctly written within the Profile Container. Attempted solution #2: Exclude `AppData\Local\Packages` with Copy=0 Attempted solution #3: Exclude `AppData\Local\Packages` with Copy=3 Outcome of attempted solutions 2 and 3: Ineffective, problem remains unresolved. Solutions 2 and 3 reversed. Solution 1 still in effect at time of writing. Machines OS: Windows 10 22H2 ADMX configuration is as follows: Logging\Log Keeping Period = 3 Profile Containers\Container and Directory Naming\Flip Flop Profile Directory Name = 1 Profile Containers\Container and Directory Naming\Volume Type = VHDX Profile Containers\Enabled = 1 Profile Containers\Install Appx Packages = 1 Profile Containers\Is Dynamic = 1 Profile Containers\Locked Retry Count = 3 Profile Containers\Locked Retry Interval = 15 Profile Containers\Reattach Count = 3 Profile Containers\Reattach Interval = 15 Profile Containers\Size In MBs = 76800 # 75 GB Profile Containers\VHD Locations = \\contoso.lan\FSLData # DFS share used Profile Containers\Roam Identity = 1 # Workaround for Microsoft 365 re-auth issue, environment lacks true SSO configuration Profile Containers\Keep Local Directory (after logoff) = 1 # Applicable to assigned dedicated machines only Profile Containers\Redirection XML Source Folder = \\contoso.lan\FSLCfgDedi # Applicable to assigned dedicated machines only Profile Containers\Reboot On User Logoff = Reboot only on any FSLogix Profile logoff (3) # Applied only to test machine for time savings during troubleshooting Redirection XML being used here: <?xml version="1.0" encoding="UTF-8"?> <FrxProfileFolderRedirection ExcludeCommonFolders="33"> <Excludes> <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs</Exclude> <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs</Exclude> <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage</Exclude> <Exclude Copy="0">AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\meeting-addin</Exclude> </Excludes> <Includes> <Include>AppData\Roaming\Microsoft</Include> <Include>AppData\Local\Microsoft\Office</Include> <Include>AppData\Local\Microsoft\Credentials</Include> </Includes> </FrxProfileFolderRedirection> Things that DO work: Profile Container in general (creates in SMB repo if not exists, mounts, stores user data, dismounts on logoff) Persistence of Microsoft 365 authentication and user customizations (OneDrive, new MSTeams, Office apps, Outlook) Persistence of general application customizations Persistence of pinned Taskbar and Start Menu items Redirection XML setting ExcludeCommonFolders=33 Redirection XML excludes and includes Writing this post feels like preaching to the choir / beating a horse vibe after having done a lot of Googling on this.