In this post, I will show you how to deploy new Microsoft Teams using SCCM. I will use the MS Teams MSIX installer for installing the new Teams application on Windows devices using SCCM.
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.
For those of you who are not aware, the new Teams desktop client installs and loads faster than the classic version and ensures more efficient use of device resources. Users will have a positive experience after moving from classic teams to new teams.
As per Microsoft, upgrading to the new Teams experience is quick and seamless. There is no migration necessary for users! To switch to the new Teams, classic Teams users can now select the “Try the new Teams” toggle in the upper-left corner of the classic Teams app.
This guide is extremely useful for organizations looking to roll out new Microsoft Teams (work or school) deployments via SCCM. For deploying older versions of Teams, refer to the guide on deploying Microsoft Teams Classic using SCCM.
Download New Microsoft Teams MSIX installer
For enterprise deployments, Microsoft provides a MSIX installer for the new Teams application. To download the latest version of the new Microsoft Teams app, visit Download New Microsoft Teams for Windows Desktop.
There are two options that you see while downloading the new teams:
- Teams for home
- Teams for work or school
Teams for Home is a free version exclusively for home users, whereas Teams for Work or School works for business and educational organizations to make it easy to collaborate, plan and innovate together.
For new Microsoft Teams enterprise deployments, you must download the Teams for work or school MSIX installer. If you have only 64-bit operating systems in your enterprise, go for the 64-bit version of the new Teams desktop client. And in case you have both 32-bit and 64-bit OS in your setup, download both installers.
Prepare for New Teams deployment
Thanks to Microsoft, the new Microsoft Teams for Windows desktop is available as .MSIX installer. MSIX is a Windows app package format that provides a modern packaging experience for all Windows apps. Configuration Manager supports deploying MSIX installers to Windows devices, and it’s much easier than deploying a typical executable installer.
To prepare for the deployment, I have saved the new Teams MSIX installer and an icon to a folder within the ‘Sources‘ folder on my ConfigMgr server. This folder acts as a content location while creating the app in SCCM.
Specifying an icon for an application in SCCM is optional, but I strongly recommend it because it appears along with the app in the Software Center. For more details, refer to the guide on customizing software center in SCCM.
Create New Microsoft Teams application in SCCM
Perform the following steps to create an application for new Microsoft Teams in SCCM:
- Launch the Configuration Manager console.
- Go to Software Library > Overview > Application Management.
- Right-click Applications and select Create Application.
On the General window, select Automatically detect information about this application from installation files. Then select the following:
- Type: Click the drop-down and choose Windows app package
- Location: Choose the content location of the MSTeams-x64.msix installer.
Click Next to proceed.
The Configuration Manager imports the following information from the MS Teams MSIX installer.
Application name: Microsoft Teams (work or school)
Publisher: Microsoft
Software version: 24033.811.2738.2546
Architecture: x64
Framework: No
OS max version tested: 10.0.22621.0
OS min version: 10.0.17763.0
Description: Microsoft Corporation
Deployment type name: Microsoft Teams (work or school) - Windows app package (*.appx, *.appxbundle, *.msix, *.msixbundle)
Detection Method:
Name:MSTeams
Publisher:Microsoft
Architecture: x64
Resource ID:
Version:24033.811.2738.2546
Publisher ID:8wekyb3d8bbwe
Content location: \\corpcm\Sources\Applications\Teams\
Number of files: 1
Content files:
MSTeams-x64.msix
Click Next.
On the General Information tab, specify the basic information, which includes Name, Publisher, Software version, etc. for the new MS Teams application. Click Next.
Review the configuration settings on the Summary tab and click Next. On the Completion tab, click Close to exit the Create Application Wizard.
Assign an icon for the new MS Teams application in SCCM
This step is optional but like I mentioned before, you can assign an icon to the new MS Teams application in SCCM. This icon will appear in the Software Center for users along with the new MS Teams app. Learn more about customizing the Software Center in ConfigMgr.
To assign an icon, right-click the new MS Teams app and select Properties. Switch to the Software Center tab, and at the bottom, click on Browse and select an icon. The icon that you selected should appear now. Click Apply and OK.
Deploy New Microsoft Teams using SCCM
In this section, I will cover the steps to deploy new MS Teams application using SCCM to a device collection. You can also create a device collection and include a set of devices for testing the application deployment.
To deploy the new Microsoft Teams application in the SCCM console, go to Software Library > Application Management > Application. Right-click the New Microsoft Teams (work or school) app and select Deploy.
On the General page of the Deploy Software Wizard, click Browse and select a Windows device collection to which you want to deploy the new MS Teams application. Click Next.
On the Content page, click the Add button and specify the distribution points to which you would like to distribute the new Microsoft Teams application content. You may also select distribution point groups here. Click Next to continue.
On the Deployment Settings window, specify the settings to control the deployment. Select the Action as Install and Purpose as Available. Learn the difference between Available and Required deployment in SCCM. Click Next.
- Scheduling: With the scheduling option, you can schedule new Teams application deployments in SCCM. You can set a date and time to trigger the application deployment. To deploy the application soon after you complete this wizard, click Next.
- User Experience: Configure the user experience settings for the new MS Teams application deployment. Click Next.
- Summary: Review the overall application deployment settings for MS Teams and click Next.
On the Completion window, click Close. This completes the new Microsoft Teams deployment using SCCM.
Verify new MS Teams deployment on Windows Computers
In this section, we will verify if the new Teams application installs correctly on the Windows computers. Log in to a remote computer and launch the software center. Click on the Applications tab and select the New Microsoft Teams (work or school) application.
On the New Microsoft Teams (work or school) 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 New Microsoft Teams (work or school) has been installed successfully on the computer.
You can review the application installation progress by opening the AppEnforce.log located in the C:\Windows\CCM\Logs folder. Furthermore, I would like you all to go through a list of all the SCCM Log files for troubleshooting issues.
The line App enforcement completed for App DT Microsoft Teams (work or school) in the AppEnforce.log confirms that the new Teams application has been installed successfully.
+++ Starting Install enforcement for App DT "Microsoft Teams (work or school) - Windows app package (*.appx, *.appxbundle, *.msix, *.msixbundle)" ApplicationDeliveryType - ScopeId_7C1AC255-2599-4BB0-AACA-12578D86C0BC/DeploymentType_27df019a-63c9-4e63-a0df-e9b8b1a9d9e5, Revision - 1, ContentPath - C:\Windows\ccmcache\3, Execution Context - User EnforceApp (MSTeams) ScopeId_7C1AC255-2599-4BB0-AACA-12578D86C0BC/DeploymentType_27df019a-63c9-4e63-a0df-e9b8b1a9d9e5,1 completed. Returning 0x0 +++ Enforce completed for ScopeId_7C1AC255-2599-4BB0-AACA-12578D86C0BC/DeploymentType_27df019a-63c9-4e63-a0df-e9b8b1a9d9e5, 1 using Package: MSTeams_24033.811.2738.2546_x64__8wekyb3d8bbwe. +++ AppX Install Info added. [AppDT Id: ScopeId_7C1AC255-2599-4BB0-AACA-12578D86C0BC/DeploymentType_27df019a-63c9-4e63-a0df-e9b8b1a9d9e5] ++++++ App enforcement completed (13 seconds) for App DT "Microsoft Teams (work or school) - Windows app package (*.appx, *.appxbundle, *.msix, *.msixbundle)" [ScopeId_7C1AC255-2599-4BB0-AACA-12578D86C0BC/DeploymentType_27df019a-63c9-4e63-a0df-e9b8b1a9d9e5], Revision: 1, User SID: S-1-5-21-1071632028-1363351252-2116187111-1106] ++++++
During my deployment, I also tested the uninstallation of the new Microsoft Teams application from the Software Center, which worked successfully. There were no errors during the app uninstallation.
Uninstalling the Classic Teams app
I am sure you will have the following question: will the classic Teams app be uninstalled after installing the new MS Teams app via SCCM? Well, the answer is no. During my testing, I discovered that following the new Microsoft Teams deployment via SCCM, the classic Teams app is not uninstalled.
I am expecting that Microsoft could uninstall the old version of Teams (classic teams) with a Windows update, or it can be done with a simple PowerShell script. I will gather more information regarding this topic and produce a separate guide for deleting the Classic Teams app from Windows devices.
To summarize, I hope this guide assists you in deploying new Microsoft Teams via SCCM (ConfigMgr). If you have any questions, please ask in the comments section.
I have created an installation via PSADT where the MSIX is installed by the PSADT Script.
This way it is possible to use a powershell script as detection method AND install it during a task sequence.
Although I am still fuguring out this part. For the MSIX for teams the user has to be around to install it and when I install it without user logged in, later it shows being installed, but the user cannot open it.
MSFT, what a mess!!!
Thank you, helpful guide as usual
any news regarding the: “Uninstalling the Classic Teams app” ?
Has anyone found a better way to get around auto updates and the SCCM deployment? My issue is that when I need to report on the deployment status, most of the devices show error as they have already auto updated. For me to keep updating the teams deployments with a new file almost weekly is not possible. I cant use an available deployment as I also need Teams to auto deploy. Using an MSI was the best as we could setup the detection method. MSIX is annoying.
As you’re using the MSIX installation method, when the application auto-updates and increments past 24033.811.2738.2546, it’ll detect as no longer being installed. How do you cater for this, without having to create a new application every week. Ideally, we could choose 24033.811.2738.2546 *or later*, but I haven’t found a way to do this yet. Any ideas?
This is always our issue. My only solution is to make this application available and not required so it doesn’t continuously fail once someone’s Teams gets updated.
I’ve the same issue.
The application is “available”, however users keep trying to install it and the installation fails because they already have a later version ♂️
I thought about creating a device collection to associate the deployment with, but I still haven’t been able to build a query that could detect the actual presence of a more recent file.
The New Teams is at the path “C:\Program Files\WindowsApps\MSTeams_{installed-version}_x64__8wekyb3d8bbwe\ms-teams.exe”
Any ideas?
I’ve limited the depoly to a collection with a query rule like this:
select SMS_R_System.Name, SMS_G_System_WINDOWS8_APPLICATION.FullName, SMS_G_System_WINDOWS8_APPLICATION.Version from SMS_R_System inner join SMS_G_System_WINDOWS8_APPLICATION on SMS_G_System_WINDOWS8_APPLICATION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_WINDOWS8_APPLICATION.FullName like “MSTeams%” and SMS_G_System_WINDOWS8_APPLICATION.Version < "24102"
Where 24102 is the Teams version in my envirnoment.
You cannot deploy SCCM MSIX Applications in a task sequence. So this solution sucks for OSD.
What will happen when Teams gets updated by Microsoft and the detection method no longer works since you cannot change the detection method when importing the msix?
Is it recommended to provision the install to all users in the General Information Screen?
I’ve been trying to deploy this install but it’s been nothing but trouble?
How is “new” teams updated once this is deployed in this manner via SCCM?
Should be same as before. Once you install the version you install, Teams will automatically update to the latest vesion.