How to Deploy Microsoft Teams Using SCCM

This article details the steps to deploy Microsoft Teams using SCCM. Configuration Manager makes it easier to package and deploy Microsoft Teams to your organization.

If you have Microsoft 365 deployed for your organization, Microsoft Teams should be available for you. You can still deploy Microsoft Teams using SCCM.

Microsoft Teams is built on Microsoft 365 groups, Microsoft Graph, and the same enterprise-level security, compliance, and manageability as the rest of Microsoft 365 and Office 365

Integrated with Office 365, Microsoft Teams is a chat-based work-space. Microsoft Teams bring together conversations, content, meetings, files, Office apps, and third-party integrations to provide a single hub for teamwork in Microsoft 365.

I have been working on deploying Microsoft Teams app to an organization. This organization currently has Skype for business installed on the computers.

Teams can also be distributed to your organization as part of Microsoft 365 Apps for enterprise. For more information, see Deploy Microsoft Teams with Microsoft 365 Apps for enterprise.

Download Microsoft Teams Installers

Microsoft provides 32-bit, 64-bit, and ARM64 MSI files that you can use to bulk deploy Microsoft Teams to select users and computers.

MSI files can be used with Microsoft Endpoint Configuration Manager, Group Policy, or third-party distribution software, to deploy Teams to your organization.

Whereas the Bulk deployments are useful because users don’t need to download and install the Teams client manually.

Microsoft recommends that you deploy the Teams package to computers rather than a specific user. By targeting computers, all new users of those computers will benefit from this deployment.

To download the latest version of Microsoft Teams, visit the Download Microsoft Teams page. There are two options available for Windows computers.

  • Download Microsoft Teams for Desktop
    • Teams for home or small business
    • Teams for work or school
  • Download Microsoft Teams for Mobile

If you want to download Microsoft Teams MSI installers, you can visit the bulk install teams using MSI installers page and get the installers.

How to Deploy Microsoft Teams Using SCCM

We will now create a new application for Microsoft Teams in SCCM and deploy it to our endpoints. To deploy Microsoft Teams using SCCM, launch the Configuration Manager console. Create a new Application and select Manually specify the application information. Click Next.

Deploy Microsoft Teams Using SCCM
Deploy Microsoft Teams Using SCCM

On the General Information page, specify information about the Microsoft Teams application and click Next.

Deploy Microsoft Teams Using SCCM
Deploy Microsoft Teams Using SCCM

Add a new deployment type and select Manually specify the deployment type information. Click Next.

Deploy Microsoft Teams Using SCCM
Deploy Microsoft Teams Using SCCM

Specify the content location and use the following as install and uninstall commands.

Installation program - "Teams_windows.exe" -s
Uninstall Program - "%LocalAppData%\Microsoft\Teams\Update.exe" --uninstall -s

After you specify the above commands, click Next to continue.

Deploy Microsoft Teams Using SCCM
Deploy Microsoft Teams Using SCCM

We will now look at the detection method for Microsoft Teams. If you notice the uninstall command for Teams, it is supplied by Microsoft and is stored in the registry. So, we will use the same to detect the presence of Microsoft Teams application.

Microsoft Teams Registry Detection Method
Microsoft Teams Registry Detection Method

To detect the presence of Microsoft Teams app, let’s add a new detection rule. In the detection rule choose the setting type as Registry. Specify the following as mentioned below.

  • Hive – HKEY_CURRENT_USER
  • Key – SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Teams
  • Value – DisplayVersion
  • Data Type – String

Select the option “This registry settings must satisfy the following rule to indicate the presence of this application“. Choose Operator to Equals and specify value as 1.0.00.6903.

Click OK and close the detection rule window. Click Next.

Microsoft Teams Detection Method in SCCM
Microsoft Teams Detection Method in SCCM

On the User Experience window, set the Installation behavior to Install for a user. Set the installation program visibility to Hidden. Click Next.

Deploy Microsoft Teams Using SCCM

Complete the remaining steps of the create application wizard and on the completion page click Close.

Deploy Microsoft Teams Using SCCM

Distribute the Microsoft Team app to distribution points. In the next step deploy the Microsoft Teams app to the desired collection.

Testing the Teams Deployment using Software Center

In the above steps, we packaged and deploy Microsoft Teams application using SCCM. It’s time to test the Microsoft Teams client installation on computers.

On the client computer, launch the software center. Click Application and under the list of Applications select Microsoft Teams and click Install.

The Microsoft Teams client is downloaded from the local distribution point server and installation begins.

Deploy Microsoft Teams Using SCCM
Deploy Microsoft Teams Using SCCM

Using the CMTrace tool open the AppEnforce.log file on the client computer to monitor the Microsoft Teams install and uninstall process.

Check out the complete list of SCCM Log Files useful for troubleshooting Configuration Manager issues.

In my lab both install and uninstall of Microsoft Teams worked well. The installation and uninstallation was tested on Windows 7, Windows 10 operating systems.

Deploy Microsoft Teams Using SCCM
Testing the Teams Deployment using Software Center

42 thoughts on “How to Deploy Microsoft Teams Using SCCM”

  1. Hi Prajwal,

    We are facing issue with the teams upgrade the earlier version is not getting upgraded to higher version only the machine wide installer gets upgraded.

    Reply
  2. Hello Prajwal,

    I did just like you write but I have error “Application not discovered”.
    The detection method is set like in your instruction above, but that doesn’t worked for me.
    Application is installing very well, but the “failure” status is showing in Software Center, so it will be confusing for users…

    Can u help me with this?

    Thanks,
    Lucas

    Reply
  3. HI. Thanks for tutorial. What if you want to update the deployment and put in its place the latest Teams msi? So you want to keep this deployment, but you want it to deploy the latest app? Say for example if you had brand new pcs. Can we just remove the old app and put in its place a new app in its place in Windows Explorer?

    Reply
  4. Thanks for another great tutorial!
    I am getting this error when I deploy.
      Unsupported configuration. App is targeted to Machine and enforcement is set to run in a user context.   AppEnforce   06/08/2020 11:57:13 AM   8796 (0x225C)
    CommenceEnforcement failed with error 0x87d0031e.   AppEnforce   06/08/2020 11:57:13 AM   8796 (0x225C)
    Method CommenceEnforcement failed with error code 87D0031E   AppEnforce   06/08/2020 11:57:13 AM   8796 (0x225C)
    ++++++ Failed to enforce app. Error 0x87d0031e. ++++++   AppEnforce   06/08/2020 11:57:13 AM   8796 (0x225C)

    I have doubled checked the deployment, it’s definitely set for a user

    Reply
  5. Can you create a guide on how to create and Deploy Microsoft Teams Rooms by using Microsoft Endpoint Configuration Manager

    Reply
  6. Hello. When I click the install button, I get the information “Status: Failed”. Click on more information and give this error 0x87D00324 (-2016410844). But in the end the Teams is installed. What should be the problem?

    Reply
    • I get the same error. I have tried several different detections, but nothing has changed. It does uninstall without any errors.

      Reply
    • That’s an application detection issue because I had the same issue while using the method mentioned in the post. However, I changed the detection method little bit, I chose “This registry setting must exist on the target system to indicate presence of this application” and run the machine policy retrieval and it worked like a charm!!!

      Reply
  7. i am running this query to see how many machines currently have teams installed by come up with nothing

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like “Microsoft Teams%”

    Reply
      • Hello,

        I have used below query still I am getting the same error, not working.

        select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like “%Microsoft Teams%”

        Reply
      • Hello Prajwal,

        We are getting multiple entries for single computer and seeing all different versions with different user, do you know why there are multiple entries getting created for same computer either with different version or different user in report. how to get accurate report.

        Reply
  8. Hi Prajwal,

    First of all thank you for this post,

    I just have a question why you choose the “Installation Behavior” to Install for user?

    Because as i know “Install for system” is better in regards to privilege.

    Thank you,

    Reply
  9. How to change the installation path? If it installs to current user profile then users will need admin privilege for the install.
    I know SCCM will use system account. What is I am doing manually or pushing through GPO.

    Reply
  10. Hi Praj,
    Thanks for this post. Also let me say, many of your posts have helped me greatly. I appreciate your efforts.
    I’m having an issue with this app always saying Failed, even though it installs and works successfully. Only thing different is that I have version 1.1.00.2251. App detection always fails after install. Seems like it is trying to do detection before it is completely installed.
    Any thoughts?
    Thank you

    Reply
      • I did multiple times and tried multiple detections.
        I had a suspicion that it was installing “too fast”. I found a link that confirmed this. So, per the link, i created a .bat file with the following 2 lines:
        teams_windows.exe /s
        ping 127.0.0.1 -n 60

        it now installs without the false failure.
        Thanks

        Reply
        • Is it installing as expected? I’ve noticed that for my deployment, it’s creating a folder in ProgramData, for each user on a computer that runs the install (e.g. “C:\ProgramData\username\Microsoft\Teams\…”). The uninstaller is placed in ProgramData as well, instead of in LocalAppData.

          Reply
            • The REG values for install and uninstall location is “C:\ProgramData\username\Microsoft\Teams\…”

              I did further testing this morning, and it seems that it only installs to LocalAppData if I am using the built-in administrator account. All other users, both local standard/admin or domain standard/admin, install to ProgramData.

              I also noticed that it is creating a folder named “SquirrelTemp” in LocalAppData, which does contain a copy of the Update.exe file. I’m going to test starting the uninstall command in that location. If that doesn’t work, I’ll probably need to make an uninstall script that checks LocalAppData and ProgramData for the uninstaller, as a workaround.

              Or wait for Microsoft’s MSI installer, which “will be available in the coming months” (as of March 8, 2018):(https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17380159-improve-install-options-install-for-all-users-an)

              Reply
              • Thanks for that info. Looks like in the new installer they have changed install location folders. I never noticed squirreltemp in appdata during my packaging. msi installer would solve most of the things here.

                Reply
                • I figured out what’s going on in my environment. We have a GPO that blocks installs from AppData, and I did not whitelist Teams.

                  It was installing to ProgramData when it couldn’t install to LocalAppData. It installs normally when that GPO is not applied.

                  Still hoping for that MSI installer so we can deploy from task sequence.

                  Reply
  11. i would recommend changing the operator from “Equals” to “Greater than or equal to” in the detection rule window. This way, even if a higher version is installed, there would not be any problems. As, MS updates teams frequently, and there is a possibility of the version value to Change in the registry.

    Reply
  12. Hi prajwal,
    Thanks for sharing this. Is there way to block startup automatic loading?

    I did the same deployment changing the success code in the program

    Reply
    • Hi

      You can stop it starting automatically by by removing the RUN key in the registry

      Command line

      reg delete HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run /v com.squirrel.Teams.Teams

      Powershell

      Remove-ItemProperty -path HKCU:\Software\Microsoft\Windows\CurrentVersion\Run\ -Name com.squirrel.Teams.Teams

      Reply

Leave a Comment