Profile Container DFS Setup - App doesn't find VHD Profile
I'm trying to Setup FSLogix Profile Container for 2 Terminalsserver for another department of my company. To get some sort of higher availability, I did setup 2 Profile Server Nodes with DFS Namespaces. In my Test-Environment, this worked great, I could take down one of my DFS Server Nodes and FSLogix would just wait for the Profile Path to be available again and mount the vhd file. Now, when I try to set the same thing up in my productive environment, I run into a strange issue. The initial creation of the vhd file of my test-user is working fine, but as soon as I try the failover by taking the DFS Server Node down, where the Profile vhd was initially created, the test-user gets a local profile (after the Path is back online again of course). In the Logfile I can see, that the App says, that it couldn't find the Profile, and therefore tried to create a new one, but as soon as it tries to create it, it says, that the file it tried to create, does already exist. So the problem is, that the Profile is there, but for some reason FSLogix doesn’t “see” the vhd file as the Profile of the Testuser.. Does anyone have any idea where to troubleshoot for this problem?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 https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/comment-page-1/ 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... https://learn.microsoft.com/en-us/fslogix/tutorial-configure-odfc-containers 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 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)