Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
As part of the deployment for the Teams client, we have information on the executables, locations, and the installer package of the client. Organizations may have different settings in their environment, such as antivirus, network settings, QoS, and so on.
- Name and location: Teams client uses ms-teams.exe & ms-teamsupdate.exe for installation. These files are located in: "Program Files\WindowsApps\MSTeams_[appversion]_[cpu arch]__8wekyb3d8bbwe".
- MSIX Installer technology stays current with the newest OS patches. Customers with installation problems in the past may resolve them with the latest OS updates.
Note
Make sure your third-party software is ready to function with the Teams client.
Checklist
- OS/WV2 prerequisites: Make sure the device has an updated Operating System (OS) and WebView2 (WV2) version. see Teams client system requirements. NOTE: The Teams client doesn't work on lower OS versions.
- Device policies restrictions: Policies must not block the Teams installation (MSIX) and the Teams Meeting add-in (MSI) or the Webview2 updater.
- Network considerations: For a good meeting experience, review any configuration to make sure the correct Teams file paths or binary name is being used. Some examples include configurations for:
- Local Firewalls: If you use Windows Firewall policies to define inbound/outbound rules specific to the Teams application, you need to update them to reference the Teams executable name and path. With each update, the Teams executable path changes. One approach for creating rules that account for the path change is to use Windows Defender Application Control (WDAC) application tagging policies. For an example, refer to the following guidance: WDAC Application Tagging for Teams.
- Split Tunneling/Proxy: If you're referencing a split tunneling and/or proxy configuration, ensure that any references include the Teams client executable and path.
- Quality of Service (QoS): If your organization's set up QoS, refer to the following guidance related to Teams:
- Software blocks: Any management software including Antivirus or AppLocker should include the Teams client. For third-party products, refer to the manufacturer's documentation.
- Machine-wide deployment or multi-user devices: Use Microsoft 365 apps or teamsbootstrapper to deploy Teams machine-wide.
- Make sure all users have Teams installed: As Teams is deployed, track usage to validate that intended users and systems are updated via the usage report for Teams client.