Has anyone else been struggling with getting the new Teams 2.0 to install across multiple machines? We often share desktops across different shifts, so it's crucial for Teams to be set up for all users. This wasn't a problem with the previous classic MSI version before it was retired. We're currently midway through transitioning to Windows 11, which has made the issue more apparent.
I've tried the usual installation methods, such as using the -p or -m flags, and even wrote a script to reinstall Teams for each user at login. However, it feels pretty hit or miss. We also attempted using a pre-packaged install through Pulseway, but it seems Teams only installs for the currently logged-in user, meaning any new users won't have access unless we rerun the setup.
We're operating on Windows 11, build 26100.4351, and had some issues with Excel 2021 in the previous build—specifically, it would crash often if you copied and pasted filtered items. I know it may seem like a small hiccup, but it's really becoming a nuisance!
3 Answers
Funny enough, we haven’t encountered any issues at all. We’re calling the bootstrapper with the -p -o flags along with the x64 msix file, and it’s running smoothly.
Have you checked out the bulk deployment guide from Microsoft? It might help streamline the installation process for multiple users. It’s a good resource to understand how to set it up more effectively, especially for shared desktops.
I actually figured it out! I recreated the installation using offline files, and now it’s working beautifully. I added an auto-run registry key for HKLM—everything’s functioning as it should with pinning and SSO!
What exactly seems to be the core issue for you? We’re using the bootstrapper with -p on our Windows images, and when users log in, Teams is accessible through the Start menu. It doesn’t auto-start like the classic version, which can get frustrating during quick tests with shared systems.
So basically, we’re installing using -p post-image. It works fine for the first admin account but doesn’t show up for regular users unless we rerun the install with them logged in. It's annoying having to deal with that every time a new user logs in.
Totally get it! Our team faced similar issues until we figured out how to integrate Teams into the base image. If it were just searchable, it wouldn’t be such a big deal, but with so many users on shared desktops, it’s a nightmare for those who aren’t tech-savvy!
I'm not sure what I was doing wrong initially, but I got it working now. Thanks for the input!