This message was deleted.

It requires something that can handle persisting uwp apps. Like FSLogix or Citrix Profile Management with the new Enable uwp apps feature which is still tech preview.

If you enable the UWP Apps does that mean all other office apps could potentially be storing stuff in it - also to clarify i am sure FSL does this already - is CPM in Tech preview for this feature?

Yes all uwp apps are automatically included https://docs.citrix.com/en-us/profile-management/current-release/configure/uwp-app-roaming.html

@Nick Pylarinos Yea all UWP apps will be picked up and stored at the root of the Fileshare. This is by design for users to share the VHDX. This was explained as I wasn't sure myself. @Rob Zylowski this should not be needed if only use CPM containers from my understanding for new Teams. If using the CPM file base then, yes. I am working with some of the backend folks to iron details out on the new teams parts with full CPM containers too.

@Ray Davis I dont think CPM containers will work without this because the UWP app files that get installed wont be included in the container so what happens is your profile thinks the uwp was insatalled but the files for the installation are not longer there. User layers would work because they capture all changes to the VDA after logon.

I see what you are saying; let me clarify this some, sorry. So yeah, the UWP part is needed, If you take this approach "UWP app files that get installed" for the user side. But Teams, in this case, would be the machine side, golden image, UWP part should not play a role in this. Two parts here. 1. UWP apps that are installed in the session that is User base, then yes, the GPO for UWP is needed to capture that. 2. For Teams, A machine-based install is not needed, from what I was told by the dev team, and the full CPM containers are supposed to grab it. Now, W10 is not working. W11 This is working with a temp workaround provided to me. I can't share yet publicly. But I can DM you on the details if needed.

The new teams has no machine install really. The installer installs an install folder. Then when the user opens teams it install but not into the profile into a different place on C I think its in a package cache. Its that second install that the profile container wont store and that would confuse things. This is what gets paced in the vhdx file in the central; store.

I understand what you are saying, and yeah, It makes sense. Install example .\teamsbootstrapper.exe -p -o "C:\Installs\newTeams\MSTeams-x64.msix" - Provisions Teams for all users - I took this as a machine installer and perhaps I need to fix my verbiage for this. new Teams installs it here. C:\Program Files\WindowsApps\MSTeams_24004.1305.2651.7623_x64__8wekyb3d8bbwe Then, when you log in. It takes this and slips it into the user profile based on my large amounts of testing. ( I now wondering if what I seen in procmon is incorrect now? This appeared to be what I seen AppData\Local\Packages\MSTeams_8wekyb3d8bbwe Let me know if you can share this "different place on C I think its in a package cache" I am curious on this now.

ill look when i get a chance

@John Gallacher - fyi