I'm really struggling with the installation inconsistency between Microsoft Teams and its Outlook add-in. It's so frustrating that Teams is deployed as an MSIX package, while the add-in for Outlook is still stuck using an MSI package. Especially since I work with various pooled VDIs, it makes it chaotic trying to keep everything updated. Honestly, the 'old Teams' was much easier to manage in this aspect. Can someone explain why there's such a difference?
3 Answers
Using a custom PowerShell script to handle the MSIX package can save a lot of headaches. It can also help you remove the old version of the meeting add-in and install the latest one from the recently installed Teams version. There are quite a few scripts out there that can help with this.
Have you thought about using the exe installer instead? It might work better for you.
You could also try the bootstrapper. It automatically downloads the MSIX for installation, but I know it can be hit or miss.
Yeah, we do that too, but it seems like the Teams add-in for Outlook doesn't always install properly for all users.
What exe installer are you talking about? I checked Microsoft's site and it only has the .msix, not an exe.