This message was deleted.
# citrix-wems
Slackbot
12/19/2023, 4:02 PMThis message was deleted.
s
Sharp Guo
12/20/2023, 11:21 AMNot sure about it. Will test it against the UWP Apps. thanks!
Sharp Guo
12/21/2023, 2:32 AMI tried one UWP app through the application action and it works for me. I use the "file or folder" type and specify the application path for it. for my test app, the path is C:\Program Files\WindowsApps\21336V3TApps.ScreenRecorder-FREE_1.0.22.0_x64__bzg06mxvgh4fa\Record Screen - FREE.exe
😀 1
m
Matt Sliva
12/21/2023, 2:35 AMThanks Sharp!
Matt Sliva
02/08/2024, 9:12 PMHere is my experience with creating a WEM action for the New Teams.
After installing the New Teams with ./teamsbootstrapper.exe, all user profiles get a new start menu shortcut called "Microsoft Teams (work or school)".
A user with a new profile can click the UWP created "Microsoft Teams (work or school)" shortcut and have the New Teams launch and sign in just fine.
If I assign a WEM action to open Teams at "C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe", New Teams does not launch for a user with a new profile. If they open the UWP created shortcut at least once, the WEM shortcut will work.
How is your testing with deploying the New Teams going? Are you using WEM to create shortcuts? Are you just installing the Universal Windows app, letting it create it's own start menu shortcut and calling it a day? What do you do if not everyone should have access to launch Teams?
k
Keith Perri
02/08/2024, 10:21 PMI haven't tested this in Citrix because we aren't able to package the new Teams using AppLayering yet, but I found a shortcut to Teams in the User's appdata that could be used with WEM to create a start menu shortcut:
"C:\Users\%username%\AppData\Local\Microsoft\WindowsApps\ms-teams.exe"
Not sure when this gets created (before or after first launch). But it may be one possible solution.
m
Matt Sliva
02/08/2024, 10:22 PMI don’t see that folder until Teams is launched.
s
Sharp Guo
02/09/2024, 6:03 AMgot it. will continue to investigate later.
r
Ray Davis
02/09/2024, 7:47 PMFor those who wonder about how it is created.
When it's installed via the bootstrap. It gets installed "C:\Program Files\WindowsApps\MSTeams_24004.1305.2651.7623_x64__8wekyb3d8bbwe" for example.
Then when a user logs into Windows and launches it, during teams registration, those files will be created under c:\users\username\appdata\local\microsoft\windowsapps
Ray Davis
02/09/2024, 7:48 PM@Matt Sliva what OS? I asked because I have some issues myself.
m
Matt Sliva
02/09/2024, 7:49 PM2022
r
Ray Davis
02/09/2024, 7:50 PMokay man, For testing only, see if you can call it form here "C:\Program Files\WindowsApps" which will put it in the user profile. Not recommended but this is what I have done for testing.
Ray Davis
02/09/2024, 7:51 PMServer 2022 is way better than 2019 IMHO
m
Matt Sliva
02/09/2024, 7:58 PMWell that’s what I tried. My WEM action points to “C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe". It does not launch for a new user profile. If the user opens Teams from the auto created UWP shortcut, the WEM shortcut will work after that.
Matt Sliva
02/09/2024, 8:01 PMI am finding this UWP app is going to do what it wants and managing it with WEM is impossible. It’s not the only UWP on the system. Calculator comes to mind and it’s start menu shortcut behaves like a traditional Win32 app.
s
Sharp Guo
02/20/2024, 9:28 AMThat is caused by the registration process of new Teams. The new Teams needs the user to run it and the registry info will be generated. The UPM and FsLogic can help generate the registry information automatically during the user logon process.
🤔 1