I administer a Windows domain at my job that I do 40 hours a week so your assessment of me is just wrong and also offensive.
I just restarted one of the workstations with Teams startup enabled and Teams ran when the computer restarted. Then I tried disabling Teams startup in the task manager on the same workstation and then restarted the workstation, and Teams hasn't started. I checked the startup tab in the task manager and Teams is still disabled after the restart. It hasn't appeared in the task manager either. This is Windows 10 Pro, so the behavior might be different on different versions/editions of Windows. Also this behavior might be affected by updates. These machines automatically install updates every Saturday, so they're running the latest Windows 10. Even if the setting is reset on a future update, I can create a GPO to disable it or even a scheduled task if I'm not allowed to manage this computer at the domain level.
This is the thing: Windows admins praise Windows when they are running a completely different edition of Windows with different configurable behaviors. It looks a lot different for home users who almost certainly do not even know what a GPO is. And this also raises the suspicion of which exact Windows edition those admins are running on their home computer(s) and how they obtained the license for that...
You haven't re-created the described problem - Teams sets itself to auto-start again after you start it yourself. After all, it's very reasonable that you might want to join the occasional Teams meeting but not want it running after every boot.
Not sure about other people here but I really liked how autostart used to work in 7 and before - just drop a shortcut in the Start menu folder and you're done. In 10 at some point, in order to have 3rd party software launched at login I had to use task scheduler.
jacobwilliamroy|1 year ago
I just restarted one of the workstations with Teams startup enabled and Teams ran when the computer restarted. Then I tried disabling Teams startup in the task manager on the same workstation and then restarted the workstation, and Teams hasn't started. I checked the startup tab in the task manager and Teams is still disabled after the restart. It hasn't appeared in the task manager either. This is Windows 10 Pro, so the behavior might be different on different versions/editions of Windows. Also this behavior might be affected by updates. These machines automatically install updates every Saturday, so they're running the latest Windows 10. Even if the setting is reset on a future update, I can create a GPO to disable it or even a scheduled task if I'm not allowed to manage this computer at the domain level.
bragh|1 year ago
dsalfdslfdsa|1 year ago
skywhopper|1 year ago
pndy|1 year ago
Also, funny thing: clicking this link pushes me thru https://login.microsoftonline.com/common/oauth2/v2.0/authori...(...) - feels like they're expecting me using Edge so they could log me in automatically with snatched MSA credentials
BoppreH|1 year ago
[1] https://github.com/winfsp/sshfs-win