Microsoft Teams is one of the latest updates to Microsoft Office 365. This chat-based collaboration software has been designed for members in a business setting, but it can also be used by individual consumers. If you want to learn more about how to set up your personal Microsoft Teams machine, this guide will tell you everything you need
The “teams machine-wide installer” is a tool that allows users to install the Microsoft Teams for all of your Windows devices. It also allows you to set up any machines that have not yet been configured.
Is it necessary to set up Microsoft Teams on your computer? Is it possible that you’ll need to distribute Teams to a larger number of people? Deploying Teams may seem difficult at first, but it does not have to be. And the Teams Machine-Wide installer will guarantee that everyone in your organization benefits from Teams’ magnificence.
In this article, you’ll learn how to set up the Teams Machine-Wide installation in various different methods. You’ll also learn how to completely uninstall it if necessary. Let’s get started if you’re ready!
Prerequisites
This page will serve as a guide. You’ll also need a Windows 10 PC if you want to follow along. The build 19043 of Windows 10 will be used in this tutorial.
Identifying the Scope of the Team’s Installation
Teams installation comes in two flavors. User-based, in which Teams is installed for a single user, and machine-wide, in which Teams is installed for all users. What’s the best way to figure out which one you have?
To determine what type of Teams installation exists on your machine, check the Apps & features list. To do so, follow the steps below.
First, open the Apps & features window. To do so, right-click on the Start button or press WIN+X to bring up the context menu. Next, click Apps and Features menu item, as in the screenshot below:
Opening the Apps & features window
On the Apps & features page, filter the apps list by typing teams into the search box. As you can see below, there are three Teams-related apps on this computer—Microsoft Teams and two instances of Teams Machine-Wide Installer.
Teams may be found by filtering the applications list.
In rare scenarios, the Teams Machine-Wide installer may appear twice in the program list. When the initial Teams MSI installation occurred in the user context, for example, the duplicate installation may occur.
If you install using the system account, the current user installation will not be detected. As a result, the list will show two instances of Teams Machine-Wide Installer.
There are no procedures in the installer that are disrupted by double installation. There is no need to remove any of the items from the list.
The default locations for the Teams Machine-Wide Installation are ‘percent PROGRAMFILES(X86) percent Teams Installer’ for 32bit and ‘percent PROGRAMFILES percent Teams Installer’ for 64bit, depending on the installer version.
If the Teams Computer-Wide Installer is installed, it will attempt to install Microsoft Teams to any user profile on the machine. However, if the Microsoft Teams client is already installed in the user profile, the installer will not install it again.
If you just see Microsoft Teams in the list of applications, Teams is only accessible to your user profile. If any other users on the computer wish to utilize Teams, they must do so independently.
Using an MSI to Create Teams
When installing software, MSI files provide administrators with more freedom and customization possibilities. The MSI installation for Teams is no exception. And, if you’re going to deploy Teams, you have a few alternatives to choose from, depending on your needs.
Download the 32-bit or 64-bit MSI installer first, depending on your system architecture, before installing Teams.
Installing the Machine-Wide Installer for Teams
You’re ready to install the Teams Machine-Wide Installer now that you’ve downloaded the MSI installer. To do so, execute the command below in PowerShell as an administrator.
How to Run PowerShell as an Administrator is a related topic.
Using the ALLUSERS=1 parameter makes the Teams Machine-Wide Installer appear in the Programs and Features in Control Panel and Apps & features in Windows Settings after installation. In which case, any user with admin access to the computer can uninstall the Teams Machine-Wide Installer.
ALLUSERS=1 msiexec /i Teams windows x64.msi
Admins may use the ALLUSER=1 option to select per-machine installation when deploying Teams to a Virtualized Desktop Infrastructure (VDI) (note the absence of a ‘S’ in the parameter name). The ALLUSERS=1 argument is not the same as this one.
During the installation, you should see a progress bar similar to the one below. It should just take a few seconds to complete the installation.
Installing the Machine-Wide Installer for Teams
Installing a prior version of Teams while waiting for a bug patch is a possibility in rare circumstances where the newest version is affected by a problem. The installation procedure is the same in both cases. The only difference is that you’ll be using a previous version of the Teams installation.
Using the Command Line to Disable Teams Autostart
When a user logs in, the Teams client launches immediately by default. However, by selecting the noAutoStart=true option during the Teams Machine-Wide Installer installation, you may avoid this behavior.
Disabling Teams from starting automatically may be handy throughout the migration process. You may, for example, allow your users to choose whether or not to utilize Teams.
Run the command below in PowerShell as administrator to install the Teams Machine-Wide Installer and deactivate Teams autostart.
Teams windows x64.msi msiexec /i ALLUSERS=1 OPTIONS=”noAutoStart=true”
Using Group Policy, disable Teams Autostart.
You may activate the Prevent Microsoft Teams from beginning immediately after installation option if you use Group Policy Objects (GPO). User ConfigurationPoliciesAdministrative TemplatesMicrosoft Teams is where you’ll discover this.
To regulate this option centrally, use Group Policy Objects to prohibit Microsoft Teams from beginning immediately after installation. For example, you may make Teams the default choice for all users, but not for a subset of them.
This article does not cover the deployment of group policies. However, you may use the group policy editor to test or validate this policy locally. To do so, follow the steps below.
1. First, to open the Group Policy Editor, click Start —> Run. On the Run window, type gpedit.msc in the Open box and press Enter or click OK.
The group policy editor is opened.
2. Navigate to User ConfigurationPoliciesAdministrative TemplatesMicrosoft Teams in the Group Policy Editor window. To modify the configuration, double-click Prevent Microsoft Teams from beginning immediately after installation.
Choosing a group policy option
3. When you’re in the settings panel, choose Enabled. When this option is enabled, Teams will not start when the user signs on to the computer. To implement the adjustment and dismiss the settings box, click OK.
Changing the group policy setting’s value
What is a Group Policy, and How Does It Work?
Installing in a Quiet Environment
Teams Machine-Wide Installer may be installed in the background. This alternative is more user-friendly since it does not cause the user any inconvenience. Use the /qn option to install in quiet mode.
In addition to deactivating Teams autostart, the program below does a silent installation. Remember to perform the commands below as an administrator in PowerShell.
Teams windows x64.msi /qn msiexec ALLUSERS=1 OPTIONS=”noAutoStart=true”
Using Microsoft 365 Apps for Business to Create Teams
Deploying Microsoft 365 Apps for Enterprise is another option for installing Teams. Starting with version 1902, Microsoft 365 Apps for Enterprise incorporates Teams. The Teams Machine-Wide Installer will be installed on the computer as part of this installation process, which will then install the Teams client.
Using Microsoft 365 Apps for Business to Set Up Teams
Follow the steps below to install Microsoft 365 Apps for Enterprise, including Teams.
1. Go to the office.com website using your web browser.
2. Use your Microsoft 365 account to log in.
3. In the top-right corner, select the Install Office icon after you’ve logged in. Then, as seen below, choose Office 365 applications.
If you don’t have Office 365 applications, either your license doesn’t contain them or your administrator has blocked the end-users’ ability to download them.
Installing Office 365 programs from the official website
4. To begin the installation, follow the browser’s three-step instructions. To run the OfficeSetup.exe installation, click Run (1). To begin installation, answer Yes (2) to the question. After the installation, stay online (3), open Microsoft Office, and login in with your account.
For instructions on how to execute the installation file in your browser, go here.
The Office Deployment Tool does not include Teams Installation.
In certain circumstances, skipping the installation of Microsoft Teams with Microsoft 365 Apps is a good idea. You could already have a functioning solution for deploying Teams, for example.
It’s also a good idea to keep Teams and Microsoft 365 Apps separate for shared remote PCs. You normally want your users to utilize Teams directly on their workstations to save delays.
Microsoft gives a number of options for installing Microsoft 365 Apps outside of Teams. Let’s have a look at them!
This article does not cover how to install Microsoft 365 apps using the Office Deployment Tool (ODT). As a result, the examples below will only show how to create a configuration file to exclude Teams from Microsoft 365 Apps installation using ODT.
You may explicitly define the ExcludeApp element in the configuration.xml file to exclude Teams if you use ODT to install Microsoft 365 Apps. For example, the configuration file below would prevent Microsoft 365 Apps from installing Teams and traditional OneDrive.
<Configuration ID=”8182a584-99e8-486f-babb-8b873ad77e10″> <Add OfficeClientEdition=”64″ Channel=”Current”> <Product ID=”O365ProPlusRetail”> <Language ID=”en-us”/> <ExcludeApp ID=”Groove”/> <ExcludeApp ID=”Teams”/> </Product> </Add> <Updates Enabled=”TRUE”/> <RemoveMSI/> </Configuration>
If you don’t want to manually alter the configuration.xml file, another option is to use the Office Customization Tool to generate a new configuration file (OCT). To build a configuration file that excludes Teams, follow the instructions below.
To get started, go to https://config.office.com/ on your browser.
2. Once you’ve arrived at the App Admin Center page, scroll to the bottom and select the Create button.
In the Office Customization Tool, create a new configuration.
3. Under the Products and releases —>Products section, click the Office Suites dropdown and choose Microsoft 365 Apps for Enterprise.
deciding the product to use in the installation
4. Go to the Apps section and turn off the Teams app.
In the Apps area, turn off Teams.
5. Next, expand the Language section by clicking. Select the main language for the installation from the selection box under Select primary. This example will use the English language (United States). After you’ve chosen your language, click Export.
Choosing the preferred language for installation
6. Select your favorite choice from the options on the Default File Format pop-up page. In this case, the option to Keep Current Settings will be selected. Click OK once you’ve made your option, and your browser will begin downloading the configuration.xml file.
Choosing a file format as the default
Microsoft Endpoint Manager does not provide Teams installation.
When implementing Microsoft 365 Apps for Enterprise using Microsoft Intune and Microsoft Endpoint Configuration Manager, there are choices to omit Teams, similar to the OCT.
To add Microsoft 365 Apps to Microsoft Intune without Teams, follow the steps below.
1. Open a web browser and go to https://endpoint.microsoft.com. Sign in using your Microsoft account.
2. After signing in, click Apps (1) —> All apps (2) —> Add (3).
In the Endpoint Manager admin center, add the app.
3. In the Pick app type fly-out, select Windows 10 from the App type selection under Microsoft 365 Apps.
Selecting an App Type
4. Select the App type and then click the Select button.
Choosing an app type and confirming it
5. Click Next after leaving the default settings in the App suite information tab.
Page with information on the app suite
6. In the Configure app suite page, deselect Teams in the Select Office apps dropdown.
In the app wizard, unchecking Teams
7. Next, choose an update channel from the Update channel (1) selection menu. In this example, we’ll use the Semi-Annual Enterprise Channel (2) and leave the rest of the settings alone. Finally, press the Next button (3).
Choosing an update channel
8. Select the persons or groups to whom Microsoft 365 Apps should be made accessible under the Assignments tab. This example will create the _Test Group group.
Click the Add group (1) option in the Available for enrolled devices section. Type to find the group you wish to add (2) on the Select groups fly-out, then click (3) the group name(s) from the results. To complete your choices, click Select (4).
App deployment: selecting a test group
9. Under the Available for enrolled devices section, you should now see the groups or users you’ve added. If required, you may repeat the procedure to add or delete groups and users at this point. Click Next after you’re through making your choices.
Ensure that the assignment settings are correct.
10. Now, under the Review + Create tab, you’ll see the summary, as seen in the image below. Click Create after checking the new app’s options.
Examining the situation
11. To access the app’s settings, go to the Properties menu once you’ve added it to Intune. Microsoft Teams is not included among the Apps to be installed as part of the package value, as you can see below.
Using Intune to see the Microsoft 365 Apps settings
Users install the Microsoft 365 Apps without Teams app through the Company Portal app or website now that you’ve added it to Intune.
Using Group Policy to Prevent Team Installation
Another method is to make advantage of the GPO setting. Microsoft Teams should not be installed with new Office installs or upgrades. Computer ConfigurationPoliciesAdministrative Templates is where you’ll locate this policy setting. Updates for Microsoft Office 2016 (Machine).
Make sure the Administrative Template files (ADMX/ADML) are version 4882.1000 or above. The editing window appears as seen in the image below.
Setting the desired group policy
Using the Registry to Prevent Teams Installation
Last but not least, you may change the registry to prevent Microsoft Teams from being installed automatically by Microsoft 365 Apps. Create the preventteamsinstall DWORD value in the registry and set the value to 1 to enable this behavior. To do so, follow the instructions below.
Changing keys in HKEY LOCAL MACHINE requires administrative access to the machine.
1. Press WIN+R on your keyboard to launch the registry editor. The Run window will appear on the screen. Then, as seen below, put regedit into the box and click OK.
Using the registry editor
2. Navigate to the HKEY LOCAL MACHINESOFTWAREPoliciesMicrosoftOffice16.0common key after launching Registry Editor. Create the keys from the route if they don’t already exist by right-clicking and creating a new key.
Making a new key
3. Inside the common (1) key, right click the space on the right pane and click New —> DWORD (32-bit) Value (2).
DWORD value creation
4. To add a new value, type preventteamsinstall and hit Enter.
The new DWORD value is being created.
5. To alter the value of the preventteamsinstall value you generated, double-click it. Change the Value data to 1 in the Edit DWORD (32-bit) Value box and click OK.
DWORD value modification
As a consequence, Microsoft Teams will no longer be included when installing Microsoft 365 Apps on a PC.
Machine-Wide Team Installations Updating
Microsoft Teams has a built-in system for checking for updates. If your machine-wide installer, for example, is out of date, Teams will request an upgrade if one is available.
Users must select Update Teams to continue with the Teams client update when they see an update prompt similar to the one below.
It’s worth noting that upgrading the Teams client also updates the Teams Machine-Wide Installer for completeness. As a result, when new users log in, the machine-wide installer will install the Teams version in their profile that came with the installation.
Teams requesting an update
Teams update is not accessible to users in VDI settings with per-machine Teams installations. To upgrade the Teams client, administrators must first remove the existing Teams MSI and then install the newest version.
Waiting for an update is not a pleasant experience for the user. Admins must maintain the installer up-to-date on a regular basis to guarantee that new users get the most recent Teams version.
Machine-Wide Teams Installation Removing and Reinstalling
Administrators and users should be aware of the consequences of uninstalling the Teams client and the Teams Machine-Wide Installer.
For Teams deployment cleanup, Microsoft offers an example script. This script uninstalls the Teams app and deletes the application data folder.
Visit the How to Uninstall Microsoft Teams on Windows 10 (For IT Pros) page for instructions on removing the Teams client and the Teams Machine-Wide Installer.
When you uninstall the Teams client, a new registry item is created: HKEY CURRENT USERSoftwareMicrosoftOfficeTeamsPreventInstallationFromMsi. The Teams Machine-Wide installer will not be able to reinstall the Teams client on the same user’s profile if this registry is set.
You must first delete the PreventInstallationFromMsi registry value before using the Teams Machine-Wide installer to reinstall Teams on the next login. To accomplish so, use PowerShell and perform the command below.
HKCU:SoftwareMicrosoftOfficeTeams’ -Name ‘PreventInstallationFromMsi’ Remove-ItemProperty -Path ‘HKCU:SoftwareMicrosoftOfficeTeams’
Related:How to Get a Registry Value with PowerShell (PS Drives and .NET)
On the other hand, unInstalling the Machine-Wide Installer for Teams will also uninstall the Teams client. This action is useful if you plan to reinstall a newer version of the Teams Machine-Wide Installer. You can then reinstall Teams using any of the methods you learned earlier in this article.
Conclusion
It may seem difficult to set up the Microsoft Teams Machine-Wide installation. Mostly because there are several deployment (or non-deployment) choices and an initial setup that seems to be complicated. This guide was written to provide you the information you need to get the Teams Machine-Wide installation up and running.
Is there anything missing from this article? Please let us know in the comments section. Learn more about Microsoft Teams by reading our other posts!
The “teams machine-wide installer vs microsoft teams” is a question that has been asked many times. The answer to this question is that the “teams machine-wide installer vs microsoft teams” can be done in 2 different ways. One way is by using the Microsoft Teams Machine, and the other way is by using a Windows 10 PC.
Related Tags
- what is teams machine-wide installer and do i need it
- can i uninstall teams machine-wide installer
- teams machine wide installer not working
- teams machine-wide installer latest version
- teams machine-wide installer latest version download
