Here's my Teams 2.1 on 2022 with FSLogix setup guide. Have it running in a customer environment and works great, both as only Teams, and side by side with 1.x classic. https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/

Hi Jeff, reading your article I found this: "Also with Server 2022 I recommend NOT using ODT and full profiles in FSLogix. I recommend just using full profiles with either VHDLocation or CloudCache." May you elaborate?

Sure. In my environments I haven't seen a benefit to separating the Office 365 data from the rest of the user profiles. With proper setup anything that is being stored in that ODT container can just be re-cached if the profile needs to be recreated. It removes a layer of complexity from many environments. I will recommend people only use Office Containers if they use an alternate profile solution that doesn't have containerization, like Mandatory profiles, or older UPM deployments. Etc.

Hm, thanks Jeff. @Cathy Leik had a different experience and as we are in a similar situation, we are about to do the same.

think you have to use separate containers if you want to support multiple simultaneous logins with OST files.

I work to prevent that whenever possible. And will setup RW to RO for consecutive logins. That way they can read data through the containers, but any of those extra rights go away. And if integrated with Onedrive for data protection data is saved, and the RO profile changes just go away.

yeah, hope they fix the online mode. Using the Outlook client in online mode with Office365 just takes a little bit longer to show emails in the preview pane. Not dealing with OSTs would be nice.

@Jeff Riechers is spot on and is our official recommendation when looking at profiles + ODFC or just profiles. As always, YMMV based on requirement.

If users DO want Teams to launch when they get into a Desktop, just create a shortcut in their %userprofile%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup folder to “C:\Program Files\WindowsApps\MSTeams_24033.811.2738.2546_x64__8wekyb3d8bbwe\ms-teams.exe” I don’t think that this will work. Users don’t have access to this folder. They need to start Teams from appdata\local

Ok, I think I did the shortcut as my admin to the user's account. I will update my notes on that. Thank you!

Is that path going to change when the program gets updated? @Dennis?

I have the following issue. Start Menu shortcut is present and is working, however i want to start teams by not using this shortcut. In %localappdata%\Microsoft\WindowsApps\ms-teams.exe does not exist unless i only start teams using the shortcut in start menu. i tried to copy out WindowsApps\ms-teams.exe from a already started session but cannot copy it to a different folder. Any ideas? I cannot start it from C:\Program Files\WindowsApps "Access Denied"