Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Direct or "bulk" upgrades are helpful because users don't need to manually download and install the Teams client. Microsoft provides an executable (.exe) file for the new Teams client so you can upgrade the application directly to the computers in your organization using your choice of software management tools, such as Intune or Configuration Manager.
The Teams installer installs the Teams MSIX package on a target computer, making sure that Teams can interoperate correctly with Office and other Microsoft software.
Note
New. An offline installer option is now available. Learn more: Download and install new Teams using an offline installer
TeamsBootstrapper is a lightweight online installer with a headless command-line interface. It allows admins to provision (install) the app for all users on a given target computer.
When teamsbootstrapper.exe is run on a computer:
Important
Users who have installed a different Teams version will have their version replaced with the provisioned version.
Important
You must use the latest version of the bootstrapper.exe. If you downloaded the .exe previously, verify you have the latest version by viewing Properties > Details > Product version on your version and compare it to the properties on the latest download.
For new Teams to be successfully installed, computers must meet the minimum requirements listed in New Teams system requirements.
Additional requirements:
Requirement | Version/Description |
---|---|
Office | Microsoft 365 Apps or Office LTSC 2021 Learn more: Office versions and connectivity to Microsoft 365 services |
Settings | Turn on the "Show Notification Banners" setting in System > Notifications > Microsoft Teams to receive Teams Notifications. |
Webview2 | Update to the most current version. Learn more: Enterprise management of WebView2 Runtimes |
Delivery optimization (DO) | DO powers Teams automatic updates, which are required as part of the Servicing Agreement. Overview: What is Delivery Optimization? Recommended settings: Set up Delivery Optimization Note: Download Mode 100 (Bypass) isn't supported. |
All steps must be completed to successfully upgrade to the new Teams.
Important
You must run the latest version of the bootstrapper.exe to avoid any issues that may have been already fixed. If you have downloaded the file previously, confirm you have the latest version by checking Properties > Details > Product version on your version and compare it to the latest download.
To install new Teams on a single computer with many users, follow these steps:
Admins can also use a local teams MSIX to provision new Teams. This option minimizes the amount of bandwidth used for the initial installation. The MSIX can exist in a local path or UNC.
For local path, enter: .\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix"
Example:
For UNC, enter: .\teamsbootstrapper.exe -p -o "\unc\path\to\teams.msix"
Example:
To deploy this installer to a group of computers, or your entire organization, follow these steps:
If the customer tenant is on the GCCH, DoD, or Gallatin, the customer may need to set the initial cloud endpoint through the following registry key. Setting the endpoint with the registry key restricts teams to connecting to the correct cloud endpoint for pre-sign-in connectivity with Teams, as shown here:
HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Teams
Value = CloudType
value type = DWORD
1 = Commercial, 2 = GCC, 3 = GCCH, 4 = DOD, 7 = Gallatin
If the customer tenant is on the GCCH, DoD, or Gallatin, the customer may need to set the initial cloud endpoint through the following .plist configuration key. Setting the endpoint with the .plist configuration restricts teams to connecting to the correct cloud endpoint for pre-sign-in connectivity with Teams, as shown here:
Domain: com.microsoft.teams2
Key: CloudType
Data Type: Int
Value: {Enter number associated with the cloud}
1 = Commercial, 2 = GCC, 3 = GCCH, 4 = DOD, 7 = Gallatin
The .plist configuration can be propagated to managed devices using Intune as described in Add preference file settings to macOS devices in Microsoft Intune.
For more information, see How to uninstall the new Teams client and Uninstall the classic Teams client using a script.
For more information, see Uninstalling classic Microsoft Teams.
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in