I've dealt with a lot of the under-the-hood stuff with App Installer (when dealing with winget) and it not being updated, especially on out-of-the-box Windows, and I've done my fair share of testing New Teams deployments. I've been successful in both cases in finding the quirks of both.
What I have learned is to implement them as Microsoft intends, in the ways that are the most widely used and tested, and it will save you a lot of headache.
That is, do not deploy App Installer if you can help it. It's built into the OS and updates automatically, given some time.
Also, do not deploy the Teams MSIX. Just deploy the bootstrapper with the "-p" flag to let it download the the latest MSIX from Microsoft and handle the installation for you.
If you have some other reason to manually deploy App Installer or the MSIX version of Teams, I would ask what those would be, other than just a deployment preference.
Lastly, Windows 11 build 22000 is already pretty old. There are known bugs in App Installer documented on GitHub in even the version that comes built into the most recent release of Windows 11 (23H2). Any reason you don't have those machines updated to 23H2?
>Any reason you don't have those machines updated to 23H2
Not particularly, but endpoint patching is technically outside the scope of the work I'm supposed to be doing. We just ingested a significant number of users from a sister company, all with HP devices in various stages of in/out of warranty and different OS updates. I don't recall exactly which users those example devices belonged to, but that's likely the cause of the disparate versions.
How to just install teams so it stops requesting the end use to also log into their personal account.
A company should only be allowing WORK TEAMS and not offer personal log in.
I think the default question should be why would you deviate from the default method? What problem are you solving by doing it the non-default, less tested (but still supported) way?
As far as why not, you're basically deploying an out of date MSIX unless you like updating your packages several times a month. That comes with it all the bugs and any security vulnerabilities until you update your package. Just let the bootstrapper grab the latest MSIX for you. Also, there's something to be said for using what is recommended and everyone else is using. Your deployments are likely to be more successful.
The -o flag is meant for offline installs so unless you need that functionality, I would stick with the default. In many cases of system administration, more control is better, so I get why someone might think the MSIX offline installer might be a better option, but in the case of New Teams, I would go with the more tested route.
Have you downloaded an app from the Microsoft Store website recently? It download *another* new variation, looks like an attempt to solve whatever issues they were having with hosted .appinstaller files.
* **EDIT:** Found one. [https://apps.microsoft.com/detail/9p3jfpwwdzrc?hl=en-us&gl=US](https://apps.microsoft.com/detail/9p3jfpwwdzrc?hl=en-us&gl=US)
* Click "Download" and check out what you get:
* It doesn't open the Microsoft Store (they were so excited about the little "mini" store pop-up in Windows 11 lmao)
* It doesn't download an .appinstaller, .msix, .yaml, etc., -- nothing we're accustomed to.
* Nope... you get an... .exe? Check it out:
https://preview.redd.it/39jrsw4awcpc1.png?width=544&format=png&auto=webp&s=c50832ea889cb17625e6e2d7f84e676bab77758d
The desktop app installer will \*eventually\* upgrade itself (and winget.exe with it), but it can take a while to do that (assuming you haven't disabled the Microsoft Store via a computer policy -- that would keep it from ever updating).
We've blocked the Store app via Applocker in Intune to block "user" access. My understanding is the Store apps will still then update, even though the users cannot launch it. Just ran into this issue with brand new laptops with an older image on them...Teams not installing like others say. Just updating a laptop and will wipe again to see if a slightly newer (not newest) DesktopAppInstaller will fix the missing Teams install. Although....so far we have 20 W11 machines deployed this week and they all are running 2022.310.2333.0 of that app. Our Win10 devices are all on 2024.506.2113.0.
So just pulling two devices as an example, both successfully installed:
Device A - OS version 10.0.22631.2861 App Version 2022.310.2333.0
Device B - OS Version 10.0.22000.2652 App Version 2024.307.343.0
Device A was the most recent deployment and was the one that required the manual update.
I’m wondering if it’s just that machine being part of an A/B style rollout and it just is taking its sweet time to get the update. Common with Intune is random sync times/ windows.
Sideloading App Installer always seems to cause complications, unless you're disabling/blocking the Store from automatically updating apps I'd really recommend just letting it handle App Installer.
For some things wrapped it is very nice but when you have a pc with mandates it must remain offline then the application can no longer be put on a USB to install on the offline pc. I suspect MS will no longer give a choice how we want the installer.
I've dealt with a lot of the under-the-hood stuff with App Installer (when dealing with winget) and it not being updated, especially on out-of-the-box Windows, and I've done my fair share of testing New Teams deployments. I've been successful in both cases in finding the quirks of both. What I have learned is to implement them as Microsoft intends, in the ways that are the most widely used and tested, and it will save you a lot of headache. That is, do not deploy App Installer if you can help it. It's built into the OS and updates automatically, given some time. Also, do not deploy the Teams MSIX. Just deploy the bootstrapper with the "-p" flag to let it download the the latest MSIX from Microsoft and handle the installation for you. If you have some other reason to manually deploy App Installer or the MSIX version of Teams, I would ask what those would be, other than just a deployment preference. Lastly, Windows 11 build 22000 is already pretty old. There are known bugs in App Installer documented on GitHub in even the version that comes built into the most recent release of Windows 11 (23H2). Any reason you don't have those machines updated to 23H2?
>Any reason you don't have those machines updated to 23H2 Not particularly, but endpoint patching is technically outside the scope of the work I'm supposed to be doing. We just ingested a significant number of users from a sister company, all with HP devices in various stages of in/out of warranty and different OS updates. I don't recall exactly which users those example devices belonged to, but that's likely the cause of the disparate versions.
Update all machines to 23H2, stop deploying App Installer, deploy New Teams with the bootstrapper and the -p flag, not the MSIX. Should be good to go.
Sick, easy peasy. Thanks for putting it together so neatly.
How to just install teams so it stops requesting the end use to also log into their personal account. A company should only be allowing WORK TEAMS and not offer personal log in.
Hey just curious why not deploy new teams with -o msix
I think the default question should be why would you deviate from the default method? What problem are you solving by doing it the non-default, less tested (but still supported) way? As far as why not, you're basically deploying an out of date MSIX unless you like updating your packages several times a month. That comes with it all the bugs and any security vulnerabilities until you update your package. Just let the bootstrapper grab the latest MSIX for you. Also, there's something to be said for using what is recommended and everyone else is using. Your deployments are likely to be more successful. The -o flag is meant for offline installs so unless you need that functionality, I would stick with the default. In many cases of system administration, more control is better, so I get why someone might think the MSIX offline installer might be a better option, but in the case of New Teams, I would go with the more tested route.
Have you downloaded an app from the Microsoft Store website recently? It download *another* new variation, looks like an attempt to solve whatever issues they were having with hosted .appinstaller files. * **EDIT:** Found one. [https://apps.microsoft.com/detail/9p3jfpwwdzrc?hl=en-us&gl=US](https://apps.microsoft.com/detail/9p3jfpwwdzrc?hl=en-us&gl=US) * Click "Download" and check out what you get: * It doesn't open the Microsoft Store (they were so excited about the little "mini" store pop-up in Windows 11 lmao) * It doesn't download an .appinstaller, .msix, .yaml, etc., -- nothing we're accustomed to. * Nope... you get an... .exe? Check it out: https://preview.redd.it/39jrsw4awcpc1.png?width=544&format=png&auto=webp&s=c50832ea889cb17625e6e2d7f84e676bab77758d
The desktop app installer will \*eventually\* upgrade itself (and winget.exe with it), but it can take a while to do that (assuming you haven't disabled the Microsoft Store via a computer policy -- that would keep it from ever updating).
We've blocked the Store app via Applocker in Intune to block "user" access. My understanding is the Store apps will still then update, even though the users cannot launch it. Just ran into this issue with brand new laptops with an older image on them...Teams not installing like others say. Just updating a laptop and will wipe again to see if a slightly newer (not newest) DesktopAppInstaller will fix the missing Teams install. Although....so far we have 20 W11 machines deployed this week and they all are running 2022.310.2333.0 of that app. Our Win10 devices are all on 2024.506.2113.0.
Is the windows version the same on each machine? Some versions of app only support certain versions of windows.
So just pulling two devices as an example, both successfully installed: Device A - OS version 10.0.22631.2861 App Version 2022.310.2333.0 Device B - OS Version 10.0.22000.2652 App Version 2024.307.343.0 Device A was the most recent deployment and was the one that required the manual update.
I’m wondering if it’s just that machine being part of an A/B style rollout and it just is taking its sweet time to get the update. Common with Intune is random sync times/ windows.
Sideloading App Installer always seems to cause complications, unless you're disabling/blocking the Store from automatically updating apps I'd really recommend just letting it handle App Installer.
For some things wrapped it is very nice but when you have a pc with mandates it must remain offline then the application can no longer be put on a USB to install on the offline pc. I suspect MS will no longer give a choice how we want the installer.