New Teams aka our favorite product rn... How are you dealing with shortcut creation?

Start menu shortcut gets created, but what about Desktop? How do you configure the Action in WEM for example?

Go to shell:appsfolder, create a shortcut of Teams, place the shorcut in a shared location. Then use filecopy to copy it to the desired location. C:\Program Files\WindowsApps\MSTeams_24033.803.2689.2248_x64__8wekyb3d8bbwe this path will change with a new Teams version so creating a shortcut directly from there is maybe not useful.

Nice, new MS Teams is so much fun… 😠

Thats the way you should start WindowsApps and therefore also the new MS Teams-App: https://wslguy.net/2021/06/11/one-way-to-run-new-windows-applications-from-the-command-line/

Disable “Auto start Teams” per User:

HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\TeamsTfwStartupTask

Set DWORD State to 0

%localappdata%\Microsoft\WindowsApps\ms-teams.exe is what we're using to create a shortcut towards, looks to be a low hassle always correct path that is also used for the run command: ms-teams

How to force push the new Windows apps... how unpractical it is. Win32 was much better.

In our environment of non persistent VDI's, we create a New shortcut in public folder, pointing to ms-teams.exe, and choose an icon for it. Teams has to be installed when doing it, but you can uninstall it afterwards. Now every user has a Shortcut on their desktop.

WEM Application pointing to %localappdata%\Microsoft\WindowsApps\ms-teams.exe

Thanks @Lucas Van den Broeck and @Paul Brown! I will give it a try and report back in a couple of minutes.

This thread is really useful. I found the desktop icon path easy enough and was able to create the wem app for that, but my days of searching how to set autostart via registry was fruitless. Until today, and @Dennis's posts above. 👏

You can also change the Teams user settings in app_settings.json with WEM and JSON actions! This is the better approach, but it will not work initially, because Teams overwrites the json file after the first Teams start. Don’t forget to activate JSON (I did 😁).

Hello hive mind. I know it's late Friday so this may not be seen (at all) but, how are we all first launching teams 2.0 in non-persistent VDI? I've a situation where users expect a desktop icon to launch. Desktop icon won't work though until teams has run 1 time. I built the VDI image with teams autostart disabled, but i'm beginning to think that was a mistake. The normal locations to start the app via a script don't exist until it is launched one time, and the only place it can be launched now is from the "special" start menu icon which provides no clue on where it is running it from. c:\program files\windowsapps\ contains nothing, so does %localappdata%\Microsoft\WindowsApps\ Do I just cut my losses and have it autostart?

You prob should and then remove it via json and you can control the startup if you want/need. They should give us a GPO to control new app :/

You cannot control these new apps via GPO because of the JSON crap. But you can use WEM to control the JSON files.

Yes I know like for Teams 1.0, Json. I'm giving out at MS making our life difficult. 🙂

Rebuilt with autostart enabled and visible in task manager. By the time it is packaged into a MCS catalog though the autostart entry is gone - not sure why. So back to square one. Short term fix for now was dragging the none standard entry MS puts in the start menu onto the desktop to create a shortcut, then moving that desktop shortcut to a shared drive so we can call it on login for everyone via WEM. That gets me around the catch 22 of not being able to launch from a desktop icon until it has been launched one time, but not the most elegant of fixes.

@Paul Brown I see the same things. You found anything yet?

@Chris Schrameyer nothing repeatable with other users. If i ran the installer inside my userlayer session it completed and then worked fine from that point on. Not a great solution, but i'd take it at this point if it worked for the couple hundred users we have running userlayers....But testing with another colleague shows it does not. They get the above error messages even if manually installing. Edit - asked Rob in the applayer channel. Sounds like a known issue Citrix is working on, so i'm leaving userlayer users as is for now.

https://worldofeuc.slack.com/archives/CK6TCV3JN/p1709721436590869?thread_ts=1709715054.661659&cid=CK6TCV3JN @Dennis while testing an unconfigured teams also has "State": Dword:2 How do you filter, if teams was already open and configured? I want to set this "autostart off" only once, so if the user re-enables it, it doesnt overwrite users choice. I found ...AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\PersistedTabData only exists at a configured teams. Maybe I´ll use this. Oh folks.. that was so easy in teams 1.x 😞

What does that do? "WasEverActivated"

for me it seems that WasEverActivated is created when the user logs in into teams.

linking to another conversation about teams 2.1, this time regarding profile management. My experience is a required folder is being actively ignored by UPM even if added to folder inclusions. Anyone else seeing this behavior?

I am still determining if it will work with UPM (CPM Files). Honestly, I would think it would be buggy. I know it works with the container approach. So you can do Teams 2.1 with the container side within the CPM policy for the Teams aspects. Can you test this? Pics attatched Then try adding the Appdata\Local\Temp to the container Inclusion only.

I saw your earlier post - got dragged into another issue so not tried yet. Not sure how i can do that though for "just me" without first making a targeted profile management policy with all the existing setup in wem.. I do have the above pictured settings in the policy tho.

I assumed you had a setup where you could test things separately.

kinda..

@Marco Zimmermann, what exactly are you doing with the "WasEverActivated?" I am just curious. For the Start menu deal, I tried looking in this location and am still looking for a solution for that as well. Locations I looked, but came up empty C:\Users\username\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\LocalState

%ProgramData%\Microsoft\Windows\Start Menu\Programs
%AppData%\Microsoft\Windows\Start Menu\Programs