Block New Teams 2.1 Autostart on Published Apps only

[Jeff Riechers]

So I have a deployment where we publish Desktops and Apps to the same delivery group.  

When users login to the Desktop we want them to have the choice of auto starting Teams when they get there.  But in Published Apps we don't want Teams to launch.

Worked great with Teams 1.x.  But with New Teams 2.1 it is handles autostart differently.  It reads from the HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\TeamsTfwStartupTask\State value.

So anyone else found an answer for this yet?  As of right now we are probably going to hard code that disabled State value with WEM, and then have users put teams in their personal Startup.  But want to avoid that if possible.

With more and more UWP style apps coming, I think this is going to creep up more and more, and don't really feel like having to police helper app auto launches if possible.

[Matthias Kaiser]

Hello,

No, we haven't found a solution for this yet. We are currently setting up a test environment. Out of interest, which platform and version FsLogix or UPM does your environment run on with the new Teams version 2.x?

Thanks

[Jeff Riechers]

2022.  LTSR 2203 cu4.1.  FSlogix HF3.

 

I have an article I am writing up on how best to run Teams 2.1 with Citrix and FSLogix.  Hopefully out this weekend.

[Jeremiah Alger]

3 hours ago, Jeff Riechers said:

2022.  LTSR 2203 cu4.1.  FSlogix HF3.

 

I have an article I am writing up on how best to run Teams 2.1 with Citrix and FSLogix.  Hopefully out this weekend.

I am looking forward to it and thank you!

[Jeff Riechers]

Sorry for the delay.  Here is my first draft.  I may tune it up a bit, so let me know if you have any questions.

 

https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/

[Matthias Kaiser]

Thanks for your article. We will try to recreate the installation in our platform with Citrix UPM.