Blog Post

Microsoft Teams Blog
2 MIN READ

New Microsoft Teams bulk installer is now available for Windows

bing_gao's avatar
bing_gao
Icon for Microsoft rankMicrosoft
Feb 02, 2024

We are happy to share that the new Microsoft Teams bulk installer is now available for Windows.


We shared the news of the general availability of new Microsoft Teams in this blog post, and we have also made available tools that help admins to install the new Teams app. More details can be found in Bulk deploy the new Microsoft Teams desktop client.


Online deployment: Download and install the latest new Teams app machine wide:

  • Command (Run with admin privilege): teamsbootstrapper.exe -p
  • During online deployment, the bootstrapper app detects the CPU architecture of the system and downloads the corresponding installer of most recently released new Teams client and installs the client machine wide.

Offline deployment: Install pre-downloaded new Teams client MSIX package machine wide: Download Microsoft Teams Desktop and Mobile Apps 

  • For admins concerned with network bandwidth usage of online deployment, offline deployment mode is a great alternative. Admins can download the client only once and use the bootstrapper to bulk deploy machines in their tenant.
  • Command for local path (Run with admin privilege): teamsbootstrapper.exe -p -o "c:\path\to\teams.msix"
  • Command for UNC path (Run with admin privilege): teamsbootstrapper.exe -p -o "\unc\path\to\teams.msix"
  • During offline deployment, the bootstrapper app installs the admin specified package from either local system or UNC path. Please make sure the correct version of new Teams client is downloaded.

Bulk remove new Teams:

  • Command for deleting every occurrence of new Teams installation: teamsbootstrapper.exe -x
  • If you choose the bulk removal option, it will uninstall both the machine level and the user level installations. New Teams app instances that are running will be stopped.

We advise admins to use the bulk installer tool to install new Teams client for their tenants.

  • There are separate new Teams installer files depending on the target system's CPU architecture: X64/X86/AMR64. The bootstrapper automatically detects the system architecture and downloads the appropriate installer file to avoid performance degradations.
  • Online mode automatically downloads the most recent released version of the new Teams app. This prevents the problem of outdated versions of the app being installed over and over, which can increase network usage (outdated app versions will update to the newest release right after installation), and slow down essential feature or security updates.
  • The bootstrapper can be deployed by admins using the deployment tools they already have for example intune/sccm.

Upcoming features and bug fixes:

  • Auto start support - Create a new command line option that launches the new Teams app for all users on the machine after provisioning.
Updated Feb 05, 2024
Version 2.0
microsoft teams

45 Comments

Show More
  • StevenM2330's avatar
    StevenM2330
    Brass Contributor
    Feb 07, 2024

    We would like the autostart to roam with fslogix office container. In a stateless vdi the new teams does not autostart if a user configures this. When will this work? 

  • KenThomas's avatar
    KenThomas
    Brass Contributor
    Feb 06, 2024

    Where is the option to uninstall Classic Teams in this process? 

  • Ronan_Fahy's avatar
    Ronan_Fahy
    Brass Contributor
    Feb 06, 2024

    The bootstrapper seems to only take an absolute path to the offline package or else it fails with error code 0x80070057

    For example if we try run it as an SCCM deployed app, we would expect to be calling the bootstrapper.exe from the working directory which would be whatever SCCM cache directory is assigned at run time. Then the bootstrapper calls the MSIX installer relatively - either same folder or a subfolder. 

    e.g.

    teamsbootstrapper.exe -p -o Installer\Teams-X64.msix

     

    But that doesn't work. Haven't found a quick fix as yet but it seems like an oversight if that is indeed the behaviour. 

  • sfarnik's avatar
    sfarnik
    Brass Contributor
    Feb 06, 2024

    what about integration in Microsoft Store so we can leverage the integration in Intune ?

  • AdamGrossTX's avatar
    AdamGrossTX
    MVP
    Feb 03, 2024

    Now if they can just find a way to add centralized ENTERPRISE management tools like EVERY other enterprise product, that’s would be stellar. It’s great that we can set auto start during the install, but what if we JUST want to toggle it on or off centrally for certain classes of users/devices?

     

    Consider this - a user has Teams and no desk phone. If having Teams started is required for phone calls to come through, and the user’s job is phone based, it would be critical to force Teams auto start for those users.

     

    But also, we globally want to force Teams to start minimized by default. How can we push this setting out? What about new Windows builds where New Teams is pre-installed? We don’t get to configure the startup options for those devices.


    Point being, ENTERPRISE controls, available in Intune Settings Catalog, should be a requirement for any MS app like this.