How to Deploy Microsoft Classic Teams Using SCCM

This article details the steps to deploy Microsoft Classic Teams using SCCM. Configuration Manager makes it easy to perform Classic Teams deployment on Windows devices in your organization.

If you have Microsoft 365 deployed for your organization, Microsoft Teams should be available for you. The Classic Teams app is built on Microsoft 365 groups, Microsoft Graph, and the same enterprise-level security, compliance, and manageability as the rest of Microsoft 365.

Classic 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.

Install and Update Third Party Applications with Patch My PC

After March 31, 2024, users who are still on classic Teams will be automatically upgraded to the new Teams experience. If you are going to install Microsoft Teams in your organization, then it has to be the new Teams app. Here is the guide to deploy new Microsoft Teams using SCCM.

Table of Contents

Download Installers for Classic Teams

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 for Classic Teams deployment in your organization.

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.

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 Classic Teams Using SCCM

We will now create a new application for Microsoft Classic Teams in SCCM and deploy it to Windows devices.

Launch the Configuration Manager console. Go to Software Library > Overview > Application Management. Right-click Applications and select Create Application. Select the option Manually specify the application information. Click Next.

Deploy Microsoft Classic Teams Using SCCM

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

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

Specify the content location of the classic teams app and enter the following as install and uninstall commands.

Classic Teams Installation program - "Teams_windows.exe" -s

Classic Teams Uninstall Program - "%LocalAppData%\Microsoft\Teams\Update.exe" --uninstall -s

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

We will now look at the detection method for Classic Teams deployment. 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 Teams Classic applications.

Microsoft Teams Classic Detection Method

Detection method for MS Classic Teams

To detect the presence of Microsoft classic 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.

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

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

Distribute the Classic Teams app to distribution points. In the next step, right-click on the Microsoft Teams Classic application and use the option deploy. In the deployment software wizard, choose the device collection and assign the application. Complete the remaining steps in the wizard and complete the deployment.

Testing the Classic Teams Deployment

On the client computer, launch the software center. Click on the Applications tab and select the Microsoft Classic Teams application. On the application details page, click Install. The application is now downloaded from the local distribution point server for installation.

In the screenshot below, we see that Microsoft Teams (work or school) has been installed successfully on the computer.

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 the installation and uninstallation of Microsoft Classic Teams went smoothly. The installation and uninstallation were tested on the Windows 10 and 11 operating systems.

Still Need Help?

If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.

Forums Telegram Contact Me

45 Comments

Kyle Begle says:

at

Prajwal Desai makes the best SCCM guides! This one worked perfectly for us when rolling out Classic Teams.
Prajwal, any plans for a guide on installing New Teams via Task Sequence? Or maybe now that it is an MSIX this is no longer possible?

Reply
1. Prajwal Desai says:
  
  at
  
  It’s MSIX now, so the deployment happens with a new method.
  
  Reply
Jimmy Cleveland says:

at

Looking for information / direction on how to install / upgrade “New Teams” via MECM. I downloaded teamsbootstrapper.exe and MSTeams-x86.msix, and then created a MECM program to run teamsbootstrapper.exe -p -o “.\MSTeams-x86.msix” (ref: https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client), but it is not installing. I found no errors in the Event Log.

Reply
Ali says:

at

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
Lukas G says:

at

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
J Smith says:

at

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
deepak nawale says:

at

how to download teams msi file for sccm.

Reply
1. Prajwal Desai says:
  
  at
  
  The MSI installer is available and you can download it from Microsoft site.
  
  Reply
Alex says:

at

hi, there is a query to find who has already installed Teams on the pc ???

Reply
DannyJ says:

at

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
ITjunior says:

at

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

Reply
Ms. Proctor says:

at

Perfect instructions!

Reply
Sunil says:

at

Can we add MS Teams Application to Task Sequence?

Reply
Rangel says:

at

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
1. Paul says:
  
  at
  
  I get the same error. I have tried several different detections, but nothing has changed. It does uninstall without any errors.
  
  Reply
2. Philippe says:
  
  at
  
  Hello Seems like a détection problem, review your detection rules
  
  Reply
3. Eduardo Meza Pina says:
  
  at
  
  Create a CMD file adding the install line and the timeout Timeout /T 20 then EXIT
  
  Reply
4. Yugank says:
  
  at
  
  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
luke says:

at

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
1. Prajwal Desai says:
  
  at
  
  i see % missing just before Microsoft
  
  Reply
  1. Viraj says:
    
    at
    
    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
  2. Viraj says:
    
    at
    
    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
    1. Cage says:
      
      at
      
      How did you get the query working in the first place
      
      Reply
Milk says:

at

Oh wow this is horrible to uninstall, even with the machine-level MSI. What if we deployed it to an area and decided to uninstall it in bulk? It appears that you can’t. Any suggestions?

Reply
Kareem says:

at

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
1. Prajwal Desai says:
  
  at
  
  The Teams app installs to the user’s profile \ appdata, so it needs to install as the user.
  
  Reply
  1. Martin Thornton says:
    
    at
    
    What if there are multiple users in a student environment?
    
    Reply
    1. Riley Childs says:
      
      at
      
      It will install for each user on logon
      
      Reply
Anup Kumar Swain says:

at

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
Mike O'Hara says:

at

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
1. Prajwal Desai says:
  
  at
  
  Maybe you should re-check detection method.
  
  Reply
  1. Mike O'Hara says:
    
    at
    
    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
    1. Justin says:
      
      at
      
      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
      1. Prajwal Desai says:
        
        at
        
        I am not aware if they have changed the install folder location. What do you see in the registry under – SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Teams?.
        
        Reply
        
        Justin says:
        
        at
        
        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”
        
        Reply
        
        Prajwal Desai says:
        
        at
        
        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
        
        Justin says:
        
        at
        
        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
        
        Prajwal Desai says:
        
        at
        
        In that case you should change your uninstall commands and point to programdata.
        
        Reply
    2. Alex says:
      
      at
      
      Thanks, pause helped to fix 324 error.
      
      Reply
vamshi says:

at

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
pathum udana says:

at

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
1. Prajwal Desai says:
  
  at
  
  I don’t think so. It launches up every time when a user logs in. Something like skype for business.
  
  Reply
2. Norman McCutcheon says:
  
  at
  
  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
Dipam Pala says:

at

Hi,

I’ve tried this just now however the registry key is not there….

Any ideas why this is?

Thanks in Advance

Reply
1. Prajwal Desai says:
  
  at
  
  Is the app version same as what i mentioned in the post ?.
  
  Reply

Prajwal Desai

Prajwal Desai is a technology expert and 10 time Dual Microsoft MVP (Most Valuable Professional) with a strong focus on Microsoft Intune, SCCM, Windows 365, Enterprise Mobility, and Windows. He is a renowned author, speaker, & community leader, known for sharing his expertise & knowledge through his blog, YouTube, conferences, webinars etc.

How to Deploy Microsoft Classic Teams Using SCCM

Download Installers for Classic Teams

How to Deploy Microsoft Classic Teams Using SCCM

Detection method for MS Classic Teams

Testing the Classic Teams Deployment

Still Need Help?

Leave a Reply Cancel reply

45 Comments

Prajwal Desai

Join Community Forum

Join Telegram Group

Newsletter

Explore

About

Categories