I've been doing a lot of testing with the new teams client and I am still not able to get the UPM quite right. I'm running CVAD LTSR 2203 CU4 across the board on 2022 server. PVS is used to deploy 2022 server hosted shared desktops. I've followed the Microsoft guidance here: https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy
I have teams installed as described in the above link, reg keys set for webview and auto update, and I have the UPM inclusions/exclusions set as follows
Inclusions from MS KB
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams (directory)
AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\app_switcher_settings.json
AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\tma_settings.json
My additional inclusions
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\Localstate (directory) - This directory is empty and I do not know why it needs to roam, but if it is not roamed teams seems to load as a first time launch at every logon (no setting changes stick)
Exclusions from MS KB
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage
My additional exclusions (the following house 1,000's of very small files that increase UPM load times significantly)
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Code Cache
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Cache
AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Service Worker\CacheStorage
After all of this, Teams works almost perfectly, with only one caveat that i cannot overcome. When you logon to a VDA and open teams, you get a toast notification that says, "Microsoft Teams (work or school) is now configured to run when you log in....". If you log off and back on, it does not load automatically and when you launch it, it again pops the same message. The ONLY way that i have been able to resolve this is to enable the policy to disable automatic configuration for UPM and roam usrclass.dat* - this file will not roam, even if explicitly set, when automatic configuration is enabled. My understanding is that you absolutely do not want to roam usrclass.dat due to start menu issues when roaming and that is why it is hard coded to not roam when automatic configuration is enabled.
All of this to ask.....has anyone else had this issue and do you know how to overcome this annoying obstacle?
