SimonInOz Posted April 15, 2019 Posted April 15, 2019 Hi, Attempting to stop Teams from Autostarting. Did a group policy to remove the registry entry for: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run com.squirrel.Teams.Teams This worked, in the sense that it removes this entry, however teams still starts. Did a search through the registry, this turns up: HKEY_USERS\S-1-5-21-2654906830-3500376121-894219130-5496\Software\Microsoft\Windows\CurrentVersion\Run com.squirrel.Teams.Teams Unfortunately, all my attempts to remove this have failed. Not sure the S key is stable across all users anyway to use a registry delete entry in GP. Anyone had any luck with Powershell to stop this? Cheers
Fazza Posted April 15, 2019 Posted April 15, 2019 We found it slows the computers down tremendously so only ended up deploying it to one computer suite and recommended staff uninstall it as 90% of people complaining about slow laptops had the Teams app installed. Never managed to get it to stop autostarting on the computers that need it. I think it's to do with the way it installs for each and every user.
Ben_Stanton Posted April 15, 2019 Posted April 15, 2019 DON'T DO IT - same reason as above. It used to be there were some functions not available in the web experience, but for 99% of what our staff use it for, the browser version works hunky-dorey. So we've just put a link to teams.microsoft.com in the start menu, SSO sorts the rest out
free780 Posted April 15, 2019 Posted April 15, 2019 It's actually a per machine setting that updates teams and starts it for each user. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run A per machine real installer is coming. You can use powershell remove-itemproperty I believe. I used GPP to remove the setting.
free780 Posted April 16, 2019 Posted April 16, 2019 So if you create Registry GPP Item. Create a GPO Computer Configuration>Preferences>Registry. The Registry Key Path is SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run If you are using Teams I recommend this method I did rather than the per machine installer which is now bundled with Office 365 ProPlus. https://broadsystemadmin.wordpress.com/2018/10/10/microsoft-teams-on-shared-devices/ When Microsoft release a proper per machine version of Teams it will solve many of the issues. The Autostart in the current per-machine installer is due to the way it has been packaged. If it just provided the shortcut on the start menu to start teams but not Autostart it would be fine. Microsoft's Windows Virtual Desktop seems to be forcing Microsoft to provide per machine installers. But it takes time due to MS wanting to thoroughly test.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now