Hacker News Reader

Yes it is auto-installed and auto starts and is very annoying to get rid of, as a sysadmin. It also installs itself per-user, so non-admins get prompted constantly to install it themselves and can do so even with limited privileges. It is persistent.

View on HN

What's the annoyance? It's an MSI. Use msiexec /x to remove it (probably via PDQ Deploy or SCCM or a PowerShell Script), and then block the installer from running again during an Office install with GPO [0]. It's definitely easier than cleaning up some of the other garbageware in Pro.

0: https://docs.microsoft.com/en-us/deployoffice/teams-install#...

You can disable teams entirely from your deployment.

Good luck doing that when it was automatically enabled and deployed, so now users have data on it already.

If you're deploying office anyway you simply remove teams from the config XML for the installer. Pretty simple really.

So then give users time to migrate to an alternative and shut it down.

Reply on news.ycombinator.com