Microsoft Teams Installation

-->

In the past, Microsoft Teams was a separate installation from Microsoft 365 Apps. But starting with Version 1902, Teams is included as part of new installations of Microsoft 365 Apps. If Teams is already installed on the device, no changes are made to that installation of Teams.

In the past, Microsoft Teams was a separate installation from Microsoft 365 Apps. But starting with Version 1902, Teams is included as part of new installations of Microsoft 365 Apps. If Teams is already installed on the device, no changes are made to that installation of Teams.

Now, you need to download the installer for Microsoft Teams on VDI - you can find the installer here. Microsoft recommends installing the 64-bit version on 64-bit OSes, but there is also a 32-bit installer available as well. Save the installer to an easy-to-find folder. This package installs Microsoft Teams for all users using the MSI installer. Data - C: Program Files (x86) Teams Installer Teams.exe -checkInstall -source=default 2020-04-10 09:13:43 RegistryService: TrySetRegKey: HKEYCURRENTUSER Software Microsoft Office Teams InstallSource created 2020-04-10 09:13:43 RegistryService: TrySetRegKey: HKEYCURRENTUSER Software Microsoft Office Teams InstallSource set successfully.

Teams is also being added to existing installations of Microsoft 365 Apps on devices running Windows. For more information about when that occurs, see What about existing installations of Microsoft 365 Apps?.

Note

To complete the installation of Teams on new or existing installations of Microsoft 365 Apps, either restart the device or have the user log off and log back on.

If Skype for Business is already installed on the device, Skype for Business won't be removed and will continue to function as before. Skype for Business will continue to be installed with new installations of Microsoft 365 Apps, unless you configure your installation to exclude it.

You don't have to wait if you're ready now to deploy Teams to the users in your organization. You can deploy Teams for your users by following these instructions or you can have your users install Teams for themselves from https://teams.microsoft.com/downloads.

We also have the steps you can take to exclude Teams from new or existing installations of Microsoft 365 Apps if your organization isn't ready to deploy Teams.

Important

If you're in a GCC High or DoD environment, currently you need to exclude Teams from being installed with Microsoft 365 Apps. Instead, you need to install Teams by using the separate MSI-based installer. For links to the correct version of the MSI-based installer for your environment, see Install Microsoft Teams using Microsoft Endpoint Configuration Manager. In the future, you'll be able to install Teams along with Microsoft 365 Apps in GCC High or DoD environments without needing to use the separate MSI-based installer.

If you're using Office for Mac, see Microsoft Teams installations on a Mac.

If you're using shared computers or Virtual Desktop Infrastructure (VDI), see Shared computer and VDI environments with Microsoft Teams.

When will Microsoft Teams start being included with new installations of Microsoft 365 Apps?

The date when Teams starts being installed with new installations of Microsoft 365 Apps depends on which update channel you're using. The following table shows the schedule.

Update channelVersionDate
Current ChannelVersion 1902March 4, 2019
Monthly Enterprise ChannelVersion 2003May 12, 2020
Semi-Annual Enterprise Channel (Preview)Version 1902March 12, 2019
Semi-Annual Enterprise ChannelVersion 1902July 9, 2019

Note

Teams is also included with the following new installations:

  • Microsoft 365 Apps for business, starting with Version 1901, which was released on January 31, 2019. Microsoft 365 Apps for business is the version of Office that is included with some Microsoft 365 business plans, such as Microsoft 365 Business Premium.
  • Office for Mac, starting with Version 16.21, which was released on January 16, 2019. Office for Mac comes with any plan that includes Microsoft 365 Apps. For more information, see Microsoft Teams installations on a Mac.

How to exclude Microsoft Teams from new installations of Microsoft 365 Apps

If you don't want Teams included when you install Microsoft 365 Apps on devices running Windows, you can use Group Policy or the Office Deployment Tool. Or, as an alternative, you can let Teams be installed, but use Group Policy to prevent Teams from automatically starting when the user signs in to the device.

If you want to use the Office Deployment Tool, you can use the ExcludeApp element in your configuration.xml file, as shown in the following example.

Tip

Instead of using a text editor to create your configuration.xml, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration.xml file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool.

If you're deploying Microsoft 365 Apps by using the Office 365 Client Installation wizard in Microsoft Endpoint Configuration Manager (current branch), you can set Teams to the Off position in the configuration UI.

If you're deploying Microsoft 365 Apps by using Microsoft Intune, there is a checkbox to exclude Teams on the Configure App Suite pane.

If you're letting your users install Microsoft 365 Apps for themselves from the Office 365 portal, you can't exclude Teams from being included as part of the installation, unless you use Group Policy.

To remove Teams after it's been installed, go to Control Panel > Uninstall a program and uninstall Microsoft Teams and any instances of Teams Machine-Wide Installer. If you previously installed Teams separately from installing Microsoft 365 Apps, you might see multiple instances of Teams Machine-Wide Installer. You can also use PowerShell to remove Teams as shown in this script sample.

What about existing installations of Microsoft 365 Apps?

Teams is also being added to existing installations of Microsoft 365 Apps on devices running Windows as part of the normal update process. There is no change to existing installations of Mac.

Whether Teams gets added to an existing installation of Microsoft 365 Apps is determined by what version is installed, what version you're updating to, and some other factors. Version 1906 that was released in Current Channel in July is the first version that started including Teams as part of the update process. But not all devices updating to Version 1906 or later have received Teams as part of the update process because the rollout has been a gradual process over several months. So if you've updated a device to the latest version of Microsoft 365 Apps, but Teams hasn't been installed, that is probably expected and not necessarily an error. It's likely a future update will install Teams. If you want Teams on that device now, you can install it manually from https://teams.microsoft.com/downloads.

Important

If you're updating your existing installation of Microsoft 365 Apps to Version 1908 (Build 11929.20300) or later, Teams will be added. To complete the installation of Teams after the update, either restart the device or have the user log off and log back on.

The date when Teams can start being added to existing installations of Microsoft 365 Apps depends on which update channel you're using. The following table shows the schedule.

Update channelVersionDate
Current ChannelVersion 1906July 9, 2019
Monthly Enterprise ChannelVersion 2003May 12, 2020
Semi-Annual Enterprise Channel (Preview)Version 1908September 10, 2019
Semi-Annual Enterprise ChannelVersion 1908January 14, 2020

If you don't want Teams to be added to existing installations of Microsoft 365 Apps when you update to a newer version, you can use Group Policy or the Office Deployment Tool. Or, as an alternative, you can let Teams be added, but use Group Policy to prevent Teams from automatically starting when the user signs in to the device.

If you want to use the Office Deployment Tool, you need to run the Office Deployment Tool in /configure mode on each device before you update to the new version of Microsoft 365 Apps. The following is a configuration.xml file you can use with the Office Deployment Tool to exclude Teams from being added to your existing installation of Microsoft 365 Apps for enterprise.

Note

  • Be sure you're using the most current version of the Office Deployment Tool available on the Microsoft Download Center.
  • If your existing installation of Microsoft 365 Apps has excluded other apps, such as Access, you need to include a line in your configuration.xmi file for each of those excluded apps. Otherwise, those apps will be installed on the device.
  • If you have Microsoft 365 Apps for business installed, use O365BusinessRetail for the Product ID in your configuration.xml file.

Also, in some situations, doing an Online Repair results in Teams being installed. For example, if Microsoft 365 Apps is configured to get updates from the Office Content Delivery Network (CDN) and the update channel or version you're using includes Teams as part of the installation.

Use Group Policy to control the installation of Microsoft Teams

Download

If your organization isn't ready to deploy Teams and you use Group Policy, you can enable the Don't install Microsoft Teams with new installations or updates of Office policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.

Note

  • This policy setting only applies if you are installing or updating to Version 1905 or later of Microsoft 365 Apps.
  • To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.

If you enable this policy setting, Teams won't be installed in the following scenarios for Version 1905 or later:

  • New installations of Microsoft 365 Apps
  • Updates to existing installations of Microsoft 365 Apps
  • Users installing Microsoft 365 Apps for themselves from the Office 365 portal
  • An Online Repair of an existing installation of Microsoft 365 Apps

If you have Microsoft 365 Apps for business or can't use Group Policy for some other reason, you can add the preventteamsinstall value to the HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftOffice16.0commonofficeupdate key in the registry. The type for preventteamsinstall is REG_DWORD and the value should be set to 1 if you don't want Teams installed.

Use Group Policy to prevent Microsoft Teams from starting automatically after installation

If you want Teams to be installed, but don't want Teams to start automatically for the user after it's installed, you can use Group Policy and enable the Prevent Microsoft Teams from starting automatically after installation policy setting. You can find this policy setting under User ConfigurationPoliciesAdministrative TemplatesMicrosoft Teams.

By enabling this policy setting before Teams is installed, Teams won't start automatically when the user logs in to the device. Once a user signs in to Teams for the first time, Teams is configured to start automatically the next time the user logs into the device. The user can configure Teams to not start automatically by configuring user settings within Teams or by clearing the Open Teams on startup check box on the sign in screen for Teams.

Tip

If you've already installed Teams but you want to use this policy setting to prevent Teams from starting automatically, enable this policy setting and then run this script on a per-user basis to reset the autostart setting for Teams.

But even if you enable this policy setting so that Teams doesn't start automatically, an icon for Microsoft Teams will appear on the user's desktop.

Important

  • This policy setting only applies if you are installing or updating to the following versions of Microsoft 365 Apps:
    • Version 1906 or later of Current Channel
    • Version 1902 (Build 11328.20368) or later of Semi-Annual Enterprise Channel or Semi-Annual Enterprise Channel (Preview)
    • Version 2003 or later of Monthly Enterprise Channel
  • To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.

If you have Microsoft 365 Apps for business or can't use Group Policy for some other reason, you can add the PreventFirstLaunchAfterInstall value to the HKEY_CURRENT_USERSOFTWAREPoliciesMicrosoftOffice16.0Teams key in the registry. The type for PreventFirstLaunchAfterInstall is REG_DWORD and the value should be set to 1 if you don't want Teams to automatically start after installation.

Shared computer and VDI environments with Microsoft Teams

If devices in your organization are shared by multiple users, be aware that Teams is installed separately for each user that signs into that device. Installations of Teams average about 500 mb, so hard disk space, as well network bandwidth for updates, might become an issue for these shared devices installed with Teams. In cases where shared devices are used by a significant number of users, you might want to consider not installing Teams on those shared devices.

If you plan to use Teams in a Virtual Desktop Infrastructure (VDI) environment, see Teams for Virtualized Desktop Infrastructure. Teams installed with Microsoft 365 Apps as described in this article is NOT currently supported in VDI environments.

Feature and quality updates for Microsoft Teams

After Teams is installed, it's automatically updated approximately every two weeks with new features and quality updates. This update process for Teams is different than the update process for the other Office apps, such as Word and Excel. For more information, see Teams update process.

Microsoft Teams installations on a Mac

If you're using Version 16.21, or later, of the Office suite install package to deploy on a Mac, Teams will be included as part of the installation.

If you don't want Teams included as part of the installation, there is an Office suite install package available that doesn't include Teams. You can also use the install packages for individual applications, such as Word or Excel. For links to the most current install packages, see Update history for Office for Mac.

If you're letting your users install Office for themselves on a Mac, such as from https://teams.microsoft.com/downloads, you can't exclude Teams from being included as part of the installation.

To uninstall Teams on a Mac, quit Teams by right-clicking the Teams app in the dock, then hold down Option and choose Force Quit. Open the Application Folder, select Microsoft Teams, and move it to the Trash.

What about Office 365 plans that don't include Microsoft Teams?

Some Office 365 plans include Microsoft 365 Apps, but don't include the Teams service. Even if a plan doesn't include the Teams service, Teams will still be installed with Microsoft 365 Apps, as described earlier in this article. To prevent Teams from being installed, follow the steps outlined earlier in this article.

For Office 365 plans that don't include the Teams service, a free trial version of Teams that's valid for 1 year is available. Your users can start using it when they sign in to Teams. For more information about this free trial version and providing your users access to it, see Manage the Microsoft Teams Commercial Cloud Trial offer.

Additional information about installing Microsoft Teams

  • There is no change to new or existing installations of Office 2019, such as Office Professional Plus 2019.
  • Teams is installed with Microsoft 365 Apps in the same way that Teams is installed if you use the MSI-based installer for Teams. For each new user that signs into the device, the Teams installer runs and the Teams application is installed in the user's AppData folder.
  • The architecture (sometimes referred to as the bitness) of Teams and Microsoft 365 Apps installed on the device don't have to match. For example, you can install the 32-bit version of Teams on a device running the 64-bit versions of Microsoft 365 Apps. To change the architecture of Teams, for example from 32-bit to 64-bit, you need to uninstall the 32-bit version of Teams and then install the 64-bit version of Teams.
  • For more information for IT Pros about Microsoft Teams, see Microsoft Teams documentation.

Microsoft Teams Installation File

Microsoft has finally released Microsoft Teams installer that installs all files to Program Files. But still, it is not perfect, because it supposed to be only for Virtualized Desktop Infrastructure (VDI). The big question is if it is possible to install it on regular Windows 10? This is what the Master Packager team tried to figure out.

How does Microsoft Teams MSI for VDI work

Installation
  1. The Teams MSI package can be downloaded from Microsoft using one of the following links:
    32-bit version
    64-bit version

  2. Following command line installs Microsoft Teams:
    msiexec /i 'path_to_msi' ALLUSER=1.

  3. By setting ALLUSER=1 property MSI will install Teams to Program Files. Please note, that it is not ALLUSERS very well-known property, but Microsoft Teams custom created ALLUSER property without letter S. This choice of public MSI property name has confused many of us.

  4. It's not possible to disable auto-launch of Teams with property OPTIONS='noAutoStart=true' when installing Teams on VDI using the ALLUSER property.

  5. By installing on regular Windows 10 using ALLUSER=1 property MSI will return error:
    Installation has failed. “Cannot install for all users when a VDI environment is not detected.”
    This error is not configured through MSI tables but is returned by Teams.exe. At this point we launch Process Monitor to detect what is needed for Teams to successfully be installed.
    Teams.exe needs ”HKEY_LOCAL_MACHINESOFTWARECitrixPortICA” registry key to be created on a target machine in order to install Teams using property ALLUSER=1.

  6. Auto updates will not work when using property ALLUSER=1 meaning each version needs to be deployed by IT administrator manually.

  7. What’s inside the MSI:

    1. Without setting ALLUSER=1 property Teams MSI behaves as we previously described in one of our blog posts: https://www.masterpackager.com/blog/how-microsoft-teams-installer-should-have-looked-like-from-the-beginning. In short Teams MSI installs Teams.exe to Program Files that is the actual installer triggered by each user on windows login by the run registry.

    2. By setting ALLUSER=1 property Teams MSI still is not using Windows Installer tables for installing all the files, instead, additional Custom Actions were created by Microsoft that will unpack all the files from Teams.exe to Program files as well uninstall them.
      CA “RunInstalledExecutable' will install files to Program Files using Teams.exe with switch –allUsers.
      CA “UninstallAllUser' will uninstall all files using in Binary table saved script.

MST to install Teams on regular Windows 10

Microsoft Teams Installation Failed

We created MST file that will enable Teams MSI to be installed on regular Windows 10. Here are the changes we made in the MST file:

  1. Created [HKEY_LOCAL_MACHINESOFTWARECitrixPortICA] registry key

  1. Set ALLUSER property to 1

  1. Created ALLUSERS property and set to 1 to make Microsoft Teams entry visible in Add/Remove Programs

  1. Created ARPNOMODIFY property and set to 1 to not show modify button in Add/Remove Programs

  1. Changed ProductName property from “Teams Machine-Wide Installer” to “Microsoft Teams”

  1. Added Microsoft Teams Icon to be displayed in Add/Remove Programs

Download microsoft teams
  1. Created Custom Action “CA_DeleteDesktopShortuct' that will delete the desktop shortcut.

  1. Created NODESKTOPSHORTCUT=1 property to delete the desktop shortcut. To leave the desktop shortcut just change NODESKTOPSHORTCUT property to 0. Default value set to 1.

Microsoft Teams Installation Base

  1. Create Custom Action “CA_DisableMSTeamsAutoRun' that will delete Teams run registry to stop auto launching for every user.

  1. Created DISABLEMSTEAMSAUTORUN=1 property to delete Teams run registry. To leave run registry unattached just change DISABLEMSTEAMSAUTORUN property to 0. Default value set to 0.

Summary

Microsoft Teams Installation Fail

As just described, with little modification via MST file it is possible to install Microsoft Teams MSI to all Windows 10 machines, not just on VDI. It would be nice to see a proper MSI for Teams that use MSI tables instead of being bundled in a binary file inside the MSI.

Microsoft Teams Installation Location

Read our blog post about 'How Microsoft Teams installer should have looked like from the beginning'.

Microsoft

If you want to look into MSI/MST files, create MSI/MST from the scratch and do all possible modifications to them in the intuitive user interface, you are welcome to download Master Packager Standard edition for free. It is all you need when working with MSI/MST files.