SOLVED

Teams no longer auto launches

%3CLINGO-SUB%20id%3D%22lingo-sub-1107762%22%20slang%3D%22en-US%22%3ETeams%20no%20longer%20auto%20launches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107762%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20getting%20reports%20of%20teams%20not%20auto-launching%20at%20login%20anymore%20despite%20being%20set%20to%20do%20so.%20re-installing%20seems%20to%20have%20no%20effect.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20else%20can%20I%20try%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1107762%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eauto%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Elaunching%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107834%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20no%20longer%20auto%20launches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107834%22%20slang%3D%22en-US%22%3EHave%20you%20already%20checked%20the%20Startup%20tab%20under%20Task%20Manager%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107842%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20no%20longer%20auto%20launches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107842%22%20slang%3D%22en-US%22%3E%3CP%3Eyes%2C%20still%20listed%20in%20there%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107853%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20no%20longer%20auto%20launches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107853%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%224%22%3EHow%20to%20Enable%20the%20Auto-start%20application%20of%20teams%20using%20GPO%20(back%20to%20beginning)%20%3A%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20I%20already%20noted%20the%20registry%20key%20that%20was%20created%20by%20the%20application%20so%20I%20created%20a%20GPO%20with%20the%20following%20syntax%20and%20applied%20at%26nbsp%3B%20OU%20level.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F165327i0EA3FC46FAAB2199%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EAs%20you%20can%20see%20above%2C%20the%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Evalue%20data%20(C%3A%5CUsers%5C%25username%25%5CAppData%5CLocal%5CMicrosoft%5CTeams%5CUpdate.exe%20--processStart%20%22Teams.exe%22%20--process-start-args%20%22--system-initiated%22%20)%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ethat%20we%20used%20is%20same%20as%20the%20one%20that%20we%20deleted%20initially%2C%20but%20this%20doesn't%20work%20on%20end-user%20PC%20during%20logon.%3C%2FP%3E%3CP%3EThe%20GPO%20applied%20correctly%20and%20teams%20never%20load%20automatically%20so%20i%20copied%20the%20syntax%20and%20tried%20opening%20in%20cmd%20window%20and%20it%20works%20but%20auto-start%20do%20not%20work.%3C%2FP%3E%3CP%3Eso%20after%20spending%20sometime%20reviewing%26nbsp%3B%20%2Cfinally%20fixed%20it%20by%20changing%20the%20command%20line%20from%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Esystem-initiated%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eto%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Euser-initiated%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F165329i4204411A9EE434BC%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_1.jpeg%22%20title%3D%22clipboard_image_1.jpeg%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F165328i01272A55290168E9%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_2.png%22%20title%3D%22clipboard_image_2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EValue%20Data%3A%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EC%3A%5CUsers%5C%25username%25%5CAppData%5CLocal%5CMicrosoft%5CTeams%5CUpdate.exe%20--processStart%20%22Teams.exe%22%20--process-start-args%20%22--user-initiated%22%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EIf%20the%20user%20has%20teams%20installed%20(if%20you%20did%20not%20change%20the%20default%20install%20location)%2C%20this%20GPO%20will%20launch%20teams%20automatically%20during%20login.%3C%2FP%3E%3CP%3EWhat%20happens%20if%20the%20computer%20doesn't%20have%20teams%20installed%20but%20still%20the%20GPO%20applied%20%3F%20does%20it%20pop-up%20any%20error%3F%20No%2C%20there%20won't%20be%20any%20error%20or%20pop-up%20on%20the%20computers%20that%20don't%20have%20teams%20installed%20and%20you%20are%20safe%20to%20apply%20to%20everyone%20who%20wants%20to%20have%20the%20auto-start%20application%20enabled.%3C%2FP%3E%3CP%3EI%20hope%20it%20helps!%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F462142%22%20target%3D%22_blank%22%3E%40trandall%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1108119%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20no%20longer%20auto%20launches%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1108119%22%20slang%3D%22en-US%22%3ELooks%20very%20promising!%20I'll%20try%20this%20ASAP%20and%20let%20you%20know.%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you!%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I'm getting reports of teams not auto-launching at login anymore despite being set to do so. re-installing seems to have no effect. 

 

What else can I try?

 

Thank you

4 Replies
Highlighted
Have you already checked the Startup tab under Task Manager?
Highlighted

yes, still listed in there

Highlighted
Solution

 

How to Enable the Auto-start application of teams using GPO (back to beginning) :

 

Since I already noted the registry key that was created by the application so I created a GPO with the following syntax and applied at  OU level.

clipboard_image_0.png

As you can see above, the value data (C:\Users\%username%\AppData\Local\Microsoft\Teams\Update.exe --processStart "Teams.exe" --process-start-args "--system-initiated" ) that we used is same as the one that we deleted initially, but this doesn't work on end-user PC during logon.

The GPO applied correctly and teams never load automatically so i copied the syntax and tried opening in cmd window and it works but auto-start do not work.

so after spending sometime reviewing  ,finally fixed it by changing the command line from system-initiated to user-initiated

clipboard_image_1.jpegclipboard_image_2.png

Value Data: C:\Users\%username%\AppData\Local\Microsoft\Teams\Update.exe --processStart "Teams.exe" --process-start-args "--user-initiated"

If the user has teams installed (if you did not change the default install location), this GPO will launch teams automatically during login.

What happens if the computer doesn't have teams installed but still the GPO applied ? does it pop-up any error? No, there won't be any error or pop-up on the computers that don't have teams installed and you are safe to apply to everyone who wants to have the auto-start application enabled.

I hope it helps!

@trandall 

Highlighted
Looks very promising! I'll try this ASAP and let you know.

Thank you!