Windows 11 & Teams?

[Rundc]

How are you guys deploying teams?

 

We're just testing windows 11 and upgrading office from 2019 to M365 apps... so I removed our machine wide installer and all seemed to be good.

 

A few patch cycles later and I have teams listed 3 times in the start menu, New Teams I presume i becuase i turned it on for myself in our tenant, anyone know how to stop this from happening or where each instance is coming from?

 

[ITGuyNW]

New Teams app and Windows 11 for me is a nightmare. It now installs through a Windows store app process and keeps complaining the user has no right to install it, even though everything in GPO is allowed.

 

I can't wait for the new version to come to web based in January and bin off the app.

[andy_b]

New Teams app and Windows 11 for me is a nightmare. It now installs through a Windows store app process and keeps complaining the user has no right to install it, even though everything in GPO is allowed.

 

I can't wait for the new version to come to web based in January and bin off the app.

 

Have you installed (and made sure it is up to date) the App installer - https://apps.microsoft.com/detail/app-installer/9NBLGGH4NNS1?hl=en-US&gl=US

 

Once this was installed I was finally able to install new teams.

[ITGuyNW]

Yep. The installer opens up but then I get an error saying :

 

 

Sorry to hijack the ops thread. Mine is the same! I assume because technicially they are different programs, it lists them all. Tried uninstalling the original?

[Boredguy]

We have been using the Machine Wide Installer, and with Windows 11 22H2 build, it meant we also had the "personal" version of Teams, as well as the "School or Work" version (difference being the colour of the square and the T on the logo)

 

Deployed out Windows 22 23H2 this morning, and so far test stations don't have the "Personal" version of Teams in the educational build.

As for rolling out the new teams, well you can download the msix file for offline deployment, and use the command line to update the package on the station.

[Rundc]

Yep. The installer opens up but then I get an error saying :

 

[ATTACH=CONFIG]70344[/ATTACH]

 

Sorry to hijack the ops thread. Mine is the same! I assume because technicially they are different programs, it lists them all. Tried uninstalling the original?

No worries!

 

Glad im not the only one, we only have the machine wide insatller and Teams showing in control panel, Im looking for a way to deploy cleanly, for teachers we have a redirected start menu, which I was going to scrap for win11 but now i'm haviong second thoughs as at least we redirect the start menu I can display only one version

[Rundc]

We have been using the Machine Wide Installer, and with Windows 11 22H2 build, it meant we also had the "personal" version of Teams, as well as the "School or Work" version (difference being the colour of the square and the T on the logo)

 

Deployed out Windows 22 23H2 this morning, and so far test stations don't have the "Personal" version of Teams in the educational build.

As for rolling out the new teams, well you can download the msix file for offline deployment, and use the command line to update the package on the station.

 

This is what i've discoverted this morning, Personal version, school or work then the new school or work.

 

Comments re 23H2 are interesting... I may create a 23H2 image and see what results I get!

[Boredguy]

This is what i've discoverted this morning, Personal version, school or work then the new school or work.

 

Comments re 23H2 are interesting... I may create a 23H2 image and see what results I get!

 

Well with how the New Teams is deployed out, you won't need the "machine wide" installer anymore, since it's just a blasted MS App (which also means making shortcut can be a pain if the app number changes as it's currently in C:\Program Files\WindowsApps\MSTeams_23272.2707.2453.769_x64__8wekyb3d8bbwe\ms-teams.exe)

[Rundc]

Well with how the New Teams is deployed out, you won't need the "machine wide" installer anymore, since it's just a blasted MS App (which also means making shortcut can be a pain if the app number changes as it's currently in C:\Program Files\WindowsApps\MSTeams_23272.2707.2453.769_x64__8wekyb3d8bbwe\ms-teams.exe)

I didn't deploy it using the machine wide installer, I deployed it via the M365 apps package, but my understanding is that the package deploys the machine wide insatller then at each user log on it installs teams, therefore there's a delay.

 

So at the minute if we turn off 'new' teams which is standard for our tenant, bar IT, users will only have 2 apps... is there anyway to prevent the ms teams 'app' being pushed by microsoft, or how do we remove this as part of our deployment or even using a GPO?

[ITGuyNW]

So I had to update the app installer app in microsoft store for the Teams app to install via the MSIX package.

 

However.

 

What I have found is if one user logs into teams, signs out of both Teams and their machine, then someone else uses that machine, teams remembers their credentials and you can easily log in. It's not the worst thing in the world as we only use teams with staff on their own dedicated devices but might be an issue for those who share?

[NeoNebula]

Dealing with multiple Teams apps popping up in Windows 11 can be a bit of a hassle, especially when you've moved to M365. Here's a simpler way to handle it:First, figure out where each Teams app is coming from. It could be from the standalone installer, the one in M365, or the pre-installed one in Windows 11.Next, just uninstall any Teams versions you don't need.You can use group policies or some setup scripts to make sure only the Teams version you want gets installed and stays updated.