Problem: Unlike previous versions of MS Teams which can be installed via a standard .msi or .exe file, the New MS Teams installation process uses an MSIX and is installed as an app package and complete functionality is not guaranteed when packaged as a FlexApp. This recipe outlines a process for capturing the New Microsoft Teams as a FlexApp package by capturing the MSIX installation, registering the MSTeams app package during playback, and removing the app package upon reverse playback. This is a best effort recipe in that
Resolution:
*NOTE*: Microsoft Edge WebView2 Runtime is required and must either be: a) installed in the desktop and FPC base images, or b) installed during the packaging process. To avoid package clutter, ensure Edge and WebView2 are updated prior to performing the capture.
Microsoft Edge WebView2
There are two options for delivering New Teams:
Option 1:
Use ProfileUnity to deploy the actual MSIX package via the 'MSIX Apps' module in a configuration.
Option 2:
Capture the contents of the New Teams MSIX in a FlexApp package as outlined below:
Installation:
- Download the 'new-teams-installer_v2.6.txt' script at the bottom of the page
- Open the properties of the file and unblock it
- Rename the extension from .txt to .ps1
- Stage the script either locally on the FPC or remote location accessible via the FPC
-
Open an elevated Powershell prompt on the FPC and run the command below:
Set-ExecutionPolicy -ExecutionPolicy Bypass -Force - Log into the FPC and begin the package creation process
-
Install New Teams by running the command below from the working directory of the script:
.\new-teams-installer_v2.6.ps1 - Follow the steps outlined in the script prompt after installation to complete the packaging process and add the post-activation script
Product: FlexApp
Product Version: 6.8.6
Expires on: 365 days from publishing
Updated: 22 January, 2026