Best Option to Deploy MS Teams MSI Using SCCM | ConfigMgr

6
Deploy MS Teams using SCCM

Let’s check what are the Best Option to Deploy MS Teams MSI Using SCCM. I have a post about deploying Microsoft Teams using Office 365 ProPlus deployment workflow in SCCM. I don’t think it’s a great idea to Office 365 ProPlus deployment when you want to deploy ONLY MS Teams from Office 365 ProPlus package.

Introduction

I got a feedback that Office 365 ProPlus workload installation downloads 2 GB of complete office suite no matter what product you want to install from the wizard. I agree & I think in the specific case of Teams.

Microsoft announced that Skype for Business end of support coming by July 31, 2021. So, most of the organizations are started the migrations to MS teams. SCCM gives admins an easy option to deploy the application to Windows 10 devices.

Deploy MS Teams using SCCM - MSI
Deploy MS Teams using SCCM – MSI

Download MS Teams MSI

The best way to deploy MS Teams MSI when you already have Office 365 ProPlus package in your managed devices. Here is the option to download only the MSI from Microsoft (around 150 MB) and deploy it.

Altaro Office 365 Backup
Advertisement Altaro Office 365 Backup

Command Line Options

The following are the command line options for deploying the MS Teams MSI. You can use these commands while you deploy this MSI using Configuration Manager | SCCM.

msiexec /i Teams_windows.msi OPTIONS="noAutoStart=true"
msiexec /i Teams_windows_x64.msi OPTIONS="noAutoStart=true"

NOTE! – You can Disable auto launch for the MS Teams MSI installer. When a user logs in to Windows, Teams is installed with the MSI and a shortcut to start Teams is added to the user’s desktop.

Create MS Teams Application Using SCCM

  • Launch SCCM Console
  • Navigate to \Software Library\Overview\Application Management\Applications
  • Right Click on Applications node
  • Select Create Application
Select Create Application to Create MS Teams MSI
Select Create Application to Create MS Teams MSI

Specify Settings for this Application

  • Select the option called “Manually specify the application information
  • Click on NEXT button
Manually specify the application information - Deploy MS Teams MSI Using SCCM
Manually specify the application information – Deploy MS Teams MSI Using SCCM
  • Enter the name of the application you want to deploy – MS Teams MSI Application
  • Enter the Publisher Name – Microsoft
  • Click on NEXT to continue
Enter the name of the application you want to deploy - MS Teams MSI Application
Enter the name of the application you want to deploy – MS Teams MSI Application
  • Click on Browse to select the Software Center ICON for MS Teams
the Software Center ICON for MS Teams
the Software Center ICON for MS Teams
  • Download the following Teams ICON and Save the picture to a network location and use for the next step
Teams ICON and Save the picture - Deploy MS Teams MSI Using SCCM
Teams ICON and Save the picture – Deploy MS Teams MSI Using SCCM
  • Click on NEXT button once the Teams ICON is uploaded
Deploy MS Teams MSI Using ConfigMgr
Deploy MS Teams MSI Using ConfigMgr
  • On the Deployment Types page, you need to provide the following details.
    • Deployment Types include information about the installation method and the source files for the application
  • Click on ADD button to configure the MS Teams application
ADD button to configure the MS Teams application
ADD button to configure the MS Teams application

Deployment Type Creation for MS Teams

  • Specify the settings for this deployment type
    • Type of the Application – Windows Installer (*.msi file)
    • Click on Browse button to automatically identify the information about deployment type from MS Teams Installation File
Specify the settings for this deployment type - Deploy MS Teams MSI Using SCCM
Specify the settings for this deployment type – Deploy MS Teams MSI Using SCCM
  • Select the Downloaded Teams MSI – Teams_windows_x64.msi
  • Click on NEXT to continue
Specify the Settings for Teams MSI Deployment
Specify the Settings for Teams MSI Deployment
  • Click on NEXT to continue.
  • The following are the information which SCCM imported from MS Teams MSI file
General Information
Name: Teams Machine-Wide Installer - Windows Installer (.msi file) Technology: Windows Installer (.msi file)
Software version: 
Detection Method
Product code: {731F6BAA-A986-45A4-8936-7C3AAAAA760B}
User Experience
Installation behavior: Install for user
Teams Machine-Wide Installer - Deploy MS Teams MSI Using SCCM
Teams Machine-Wide Installer – Deploy MS Teams MSI Using SCCM
  • Enter the Name of the deployment – Teams Machine-Wide Installer – Windows Installer (*.msi file)
  • Installation Program – for 64 bit Teams MSI installation
    • msiexec /i Teams_windows_x64.msi OPTIONS=”noAutoStart=true”
  • Select Installation Behavior – Install for User
Teams Machine-Wide Installer - Windows Installer (*.msi file)
Teams Machine-Wide Installer – Windows Installer (*.msi file)
  • Click on NEXT to continue on Requirements page
MS Teams Requirements - Click NEXT to Continue - Deploy MS Teams MSI Using SCCM
MS Teams Requirements – Click NEXT to Continue – Deploy MS Teams MSI Using SCCM
  • Select the Software Dependencies of Team application
  • Click NEXT to Continue
Select the Software Dependencies of Team application
Select the Software Dependencies of Team application
  • Confirm the Settings of Teams Deployment configuration
  • Click on NEXT to continue
General Information:Name: Teams Machine-Wide Installer - Windows Installer (.msi file) •    Technology: Windows Installer (.msi file)
 •    Administrator comments:
 •    Languages:
 Content:
 •    Content location: \cmmemcm\Sources\Package Source\MS Teams MSI
 •    Installation program: msiexec /i Teams_windows_x64.msi OPTIONS="noAutoStart=true"
 Detection Method:
 •    Product code, equals, {731F6BAA-A986-45A4-8936-7C3AAAAA760B}
 User Experience:
 •    Installation behavior: Install for user
 Requirements:
 Dependencies:
Confirm the Settings of Teams Deployment configuration - Deploy MS Teams MSI Using SCCM
Confirm the Settings of Teams Deployment configuration – Deploy MS Teams MSI Using SCCM
  • Click on CLOSE to complete the MS Teams Application Deployment type using SCCM
CLOSE to complete the MS Teams Application Creation
CLOSE to complete the MS Teams Application Creation
  • Click on NEXT to Continue
Deployment Types for MS Teams - Deploy MS Teams MSI Using SCCM
Deployment Types for MS Teams – Deploy MS Teams MSI Using SCCM
  • Click on NEXT, NEXT, and CLOSE to complete the application creation process
CLOSE to complete the application creation process - Deploy MS Teams MSI Using SCCM
CLOSE to complete the application creation process – Deploy MS Teams MSI Using SCCM

Deploy MS Teams Using SCCM

  • Navigate to \Software Library\Overview\Application Management\Applications
  • Right click on the MS Teams application created above
  • Select DEPLOY
Select Deploy MS Teams Using SCCM
Select Deploy MS Teams Using SCCM
  • Click on BROWSE button near Collection
  • Select the COLLECTION you want to deploy MS Teams application
 Select the COLLECTION - Deploy MS Teams MSI Using SCCM
Select the COLLECTION – Deploy MS Teams MSI Using SCCM
  • Click on ADD button to distribute the Source files of Teams application to Distribution Point server
  • Select Distribution Point option
ADD button to distribute the Source files
ADD button to distribute the Source files
  • Select DP CMMEMCM.MEMCM.COM
  • Click OK to continue
Available Distribution Point to Distribute Teams application
Available Distribution Point to Distribute Teams application
  • Click on NEXT to continue
Content Distribution of Source files
Content Distribution of Source files
  • Select the installation ACTION as INSTALL
  • Select the Purpose as REQUIRED
Deployment Settings of Microsoft Teams - Deploy MS Teams MSI Using SCCM
Deployment Settings of Microsoft Teams – Deploy MS Teams MSI Using SCCM
  • Schedule the installation of MS Teams application on to Windows 10 devices
  • Installation Deadline
    • As Soon As Possible after the available time
Schedule -  As Soon As Possible after the available time
Schedule – As Soon As Possible after the available time
  • Click on NEXT button on USER EXPERIENCE page
  • Click on NEXT button on ALERTS page
  • Click NEXT and Confirm the summary page
General
 •    Software: MS Teams MSI Application
 •    Collection: All Desktop and Server Clients (Member Count: 1)
 •    Use default distribution point groups associated to this collection: Disabled
 •    Automatically distribute content for dependencies: Disabled
 Deployment Settings
 •    Action: Install
 •    Purpose: Required
 •    Allow end users to attempt to repair this application: Disabled
 •    Pre-deploy software to the user's primary device: Disabled
 •    Send wake-up packets: Disabled
 •    Allow clients to use a metered Internet connection to download content: Disabled
 Application Settings (retrieved from application in software library)
 •    Application Name: MS Teams MSI Application
 •    Application Version: V
 •    Application Deployment Types: Windows Installer (*.msi file)
 Scheduling
 •    Time based on: UTC
 •    Available Time: As soon as possible
 •    Deadline Time: Disabled
 •    Delayed enforcement on deployment: Disabled
 User Experience
 •    User notifications: Display in Software Center and show all notifications
 •    Ignore Maintenance Windows: Disabled
 •    When software changes are required, show a dialog window to the user instead of a toast notification: Disabled
 •    System restart  (if required to complete the installation): Disabled
 •    Commit changes at deadline or during a maintenance window (requires restarts): Enabled
 Alerts
 •    Enable System Center Operations Manager maintenance mode: Disabled
 •    Generate System Center Operations Manager alert when a software installation fails: Disabled
 •    Create a deployment alert when the threshold is lower than the following: Disabled
 •    Create a deployment alert when the threshold is higher than the following: Disabled
 Content (1):
 •    CMMEMCM.MEMCM.COM
  • Click CLOSE to finish the deploy MS Teams using SCCM
CLOSE to finish the deploy MS Teams using SCCM
CLOSE to finish the deploy MS Teams using SCCM

Results

Software Center shows MS Teams application successfully INSTALLED on the Windows 10 Device.

Software Center shows MS Teams application successfully INSTALLED
Software Center shows MS Teams application successfully INSTALLED
  • Restart the Windows 10 machine to complete the installation of MS Teams

Resources

6 COMMENTS

  1. Anoop, this is the installation of the “Teams Machine-Wide” Installer which if set to default will start to automatically update the users version on it’s own from Microsoft as new versions come out. Since the MSI Product code was selected for the deployment type detection method, what happens when new versions of the Users Teams client are automatically downloaded, do they have the same Product Code? If not will the Application Deployment detection method, detect the change and try to re-deploy then now older package on the MECM server? Note: The detection method is for the team wide installer so it may remain the same on the client while the updated user teams client keep increasing higher. In that case when does the MECM package which is installed on new machines become so old that it does not install a user teams client that can update automatically?

      • Anoop, You are correct the teams machine-wide install for new builds works well, we have deployed it in our enterprise successfully, although I used a file version detection method.
        The machine wide installer does not get updated by Office 365 ProPlus update as far as I have observed, nor does it need to since at that point the user has clicked on the teams icon on the desktop and the teams machine wide installer has installed into the users profile the same version which WILL get updated using Office 365 ProPlus update. That will work just fine, automatic updates for the users install. But lets say a year or two from now the user leaves the company and a new user logs in. He will click on the Teams icon on the desktop and invokes the machine-wide installer, which by now is at least a year old, it will probably work just fine, but will not support any new features unless it starts auto updating, which it should as long as Microsoft supports that version of the Machine-wide installer. This is a very remote scenario I suppose. If we update the Teams machine-wide installer in MECM a couple of times a year and use it for new installs only then if Microsoft supports it for at least 3 years our lease replacements will solve the problem(if there is one) as they will just go away.

        Our teams package was created using the PowerShell Application Tool Kit wrapper. Using the information from Microsoft and a script they created as a way to completely uninstall teams from all users on a machine, our wrapper can be used with the MECM Application “Repair” to completely remove all user instances of the teams and the Teams machine-wide installer and then install the latest version of the Teams Machine Wide installer. Seems to work.

        In any case we will have to wait some months to see if the Teams machine-wide installer gets updated and if it does how does it interact (if at all) with the current updated user instances?

        Microsoft is pretty smart, they probably have all of this covered, but it is something to be aware of.

        I subscribe to your emails and they have been very helpful. Thanks for all you have done for the MECM community.

  2. This seem to work for NEW user profiles, installing Teams after initial login. However, doesnt appear to work for existing user profiles. Am I missing something, or have others seen this behavior?

    Thanks
    Richie

    • Richie,
      The Machine wide installer stages the product on the machine and when the user next logs on after the install, the machine wide installer, installs an instance of teams in each users profile when they log on to the machine. In the Microsoft Teams docs on installation.
      https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment

      https://gallery.technet.microsoft.com/scriptcenter/Install-and-Uninstall-Teams-a9d2ebbc

      Once installed for a user the MS Teams app will automatically update every few days from Microsoft and it is then newer in the user instance than the Teams/Machine wide install.

      The script references explain it better than I can, but using that script you can “Scrub” both the machine wide installer and all user instances, the reinstall the latest version of the machine wide installer and have the user log off and then back on so that the Teams shortcut re-appears on their desktop, click on that, provide their credentials.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.