sippo Posted February 28, 2022 Posted February 28, 2022 We have recently installed Apps for Enterprise on our Windows 21H2 image. We cannot find a way of TEAMs not autostarting on login. Any idea's? Can't find anything online anywhere.
p858snake Posted February 28, 2022 Posted February 28, 2022 Can't comment on auto starting, but there is a user setting for it to start in the background, Just a note, If you use outlook integration for status, it won't kick in until you open teams from the tray.
Steve21 Posted February 28, 2022 Posted February 28, 2022 The reg key it sets up to install Teams per user also makes it auto start (or used to when I last updated our deployments) It’s under (assuming 64bit): HKLM software wow6432node Microsoft currentversion run And it’s the TeamsMachineInstsller key that makes Teams run and if not installed then install Steve 1
sippo Posted February 28, 2022 Author Posted February 28, 2022 I can't find those in Regedit. Grrr. What we are finding is that teams is starting in Appdata, and with mandatory profiles its a pain.
Steve21 Posted February 28, 2022 Posted February 28, 2022 It runs from appdata, but the installer is in program files if deployed via 365 Or are you deploying it separately? Did you def check the wow6432node bit? Not just current version The other bit that makes it run (but you’d need the one I mentioned above to install it in the first place) is under HKCU software Microsoft windows currentversion run And then it’s com.squirrel.teams.something But that should only get populated if installed by the machine installer in the first place Steve
chaplic Posted February 28, 2022 Posted February 28, 2022 (edited) I've done this, I've no idea why it's so convoluted, Im sure it was a good idea at the time $fixscript = $($env:LOCALAPPDATA + "\DeleteTeamsAutorun.ps1") $bootstrap= $($env:LOCALAPPDATA + "\BootstrapDeleteTeams.vbs") $script="Dim shell,command command = ""powershell.exe -nologo -executionpolicy bypass -File $fixscript"" Set shell = CreateObject(""WScript.Shell"") shell.Run command,0" $script | out-file -FilePath $bootstrap "start-sleep -seconds 60; Remove-ItemProperty -LiteralPath 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Run' -Name 'com.squirrel.Teams.Teams'" | Out-File -FilePath $fixscript New-ItemProperty -LiteralPath 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Run' -Name 'NeverTeamsOnStart' -Type String -Value "$bootstrap" -Force Edited February 28, 2022 by chaplic
sippo Posted February 28, 2022 Author Posted February 28, 2022 I cannot find Currentversion under microsoft or wow6432node
Steve21 Posted February 28, 2022 Posted February 28, 2022 (edited) Let me login on a pc and copy paste the links rather than typing Right so -> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run Which should have TeamsMachineInstaller and Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run Which should have com.squirrel.Teams.Teams Should be able to copy/paste those above into regedit directly Steve Edited February 28, 2022 by Steve21 1
georgeescott Posted April 3, 2022 Posted April 3, 2022 Working on this myself at the moment, we've done it with the Prevent Microsoft Teams from starting automatically after installation GPO setting. Although if Teams is installed before this setting is set you'll need to run the Teams autostart reset script on a per-user basis to clear out existing autostart settings so it can pick up the GPO. You'll want to make sure you have a recent copy of the Administrative Template files (ADMX/ADML) for Microsoft 365 Apps for enterprise/Office added to your PolicyDefinitions central store too.
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