I'm trying to find a way to install Microsoft Teams on a machine so that it's available for all users, rather than installing it per individual user. I've attempted a few methods: I placed Teams in the c:userspublicdesktop, tried the 64-bit MSI installer, and even tried using teamsbootstrapper to push it out, but none have worked. This issue is frustrating because we have users rotating through workstations, and I constantly have to reinstall Teams each time a new user logs in. While I considered using the browser version, most users aren't fond of that option. I'd really appreciate any suggestions you might have!
6 Answers
You might want to check out Microsoft's guide on bulk installation for Teams. It could offer a solution that fits your needs better. Here's the link: https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client.
We handle this by deploying Teams through Lansweeper. You can install under scanning credentials, and then it should be available for everyone’s profile as long as the Group Policy allows it.
Have you tried installing via PowerShell? Just use the command: `winget install Microsoft.Teams`. It installs it for all users if done with admin rights!
Are you aware that Teams often installs with Microsoft Office? It could be an option if your users have that software installed.
Though keep in mind, if you're in an EU country (and some other places), it might not be included.
Look into the Teams machine-wide installer. Just a heads-up though, it's deprecated too. The Teams bootstrap installer might be the way to go. It installs the new AppX version machine-wide and registers for each user when they log in!
Just to clarify, the old machine-wide installer really only dumped files in the program folder and didn't solve the per-user issue. The bootstrapper is your best bet, but you need to clarify what you mean by "none of these worked" for better troubleshooting.
Just so you know, local installations for Teams are becoming deprecated. It's recommended to use the browser version or the new app version instead. It's similar to the desktop version but avoids these installation troubles!
Don't forget to run `winget --version` to check your version and use `winget upgrade winget` to keep it updated!