Downloads:

2,594,113

Downloads of v 1.3.00.26064:

56,770

Last Update:

14 Oct 2020

Package Maintainer(s):

Software Author(s):

  • Microsoft Corporation

Tags:

microsoft-teams teams office 365 chat collaboration slack admin

Microsoft Teams Desktop App (Machine-Wide Install)

1.3.00.26064 | Updated: 14 Oct 2020

Downloads:

2,594,113

Downloads of v 1.3.00.26064:

56,770

Maintainer(s):

Software Author(s):

  • Microsoft Corporation

Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.26064

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Microsoft Teams Desktop App (Machine-Wide Install), run the following command from the command line or from PowerShell:

>

To upgrade Microsoft Teams Desktop App (Machine-Wide Install), run the following command from the command line or from PowerShell:

>

To uninstall Microsoft Teams Desktop App (Machine-Wide Install), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade microsoft-teams.install -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade microsoft-teams.install -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure microsoft-teams.install installed
  win_chocolatey:
    name: microsoft-teams.install
    state: present
    version: 1.3.00.26064
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'microsoft-teams.install' do
  action    :install
  version  '1.3.00.26064'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: microsoft-teams.install,
    Version: 1.3.00.26064,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller microsoft-teams.install
{
   Name     = 'microsoft-teams.install'
   Ensure   = 'Present'
   Version  = '1.3.00.26064'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'microsoft-teams.install':
  provider => 'chocolatey',
  ensure   => '1.3.00.26064',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install microsoft-teams.install version="1.3.00.26064" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 15 Oct 2020.

Description

Microsoft Teams is a messaging app for teams where all conversations, meetings, files, and notes can be accessed by everyone, all in one place. It's a place for collaboration and work to happen in the open.

Here's why you should use it:

  • It's great.
  • It makes communicating one-on-one and with groups a snap.
  • Collaboration happens in real time.
  • Everything your team cares about (all your files, docs, contact info, and more) is in once place.

This package installs Microsoft Teams for all users using the MSI installer.

The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of the Teams app will be installed in that user's AppData folder. If a user already has the Teams app installed in the AppData folder, the MSI installer will skip the process for that user.

See https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment for more information about how the MSI installer works (and is different to a regular Teams install).

Package Specific

Package Parameters

The following package parameters can be set:

  • /AllUsers - When you set this parameter, Teams Machine-Wide Installer appears in Programs and Features in Control Panel and in Apps & features in Windows Settings for all users of the computer. All users can then uninstall Teams if they have admin credentials on the computer.
  • /NoAutoStart - 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. Teams won't start until the user manually starts Teams. After the user manually starts Teams, Teams automatically starts whenever the user logs in.

To pass parameters, use --params "''" (e.g. choco install packageID [other options] --params="'/ITEM:value /ITEM2:value2 /FLAG_BOOLEAN'").

eg.

choco install microsoft-teams.install --params "'/AllUsers /NoAutoStart'"

To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades.


tools\chocolateybeforemodify.ps1
# To avoid "WARNING: This MSI requires uninstall prior to installing a different version.",
# we uninstall here

$ErrorActionPreference = 'Stop'; # stop on all errors
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Teams Machine-Wide Installer'
  fileType      = 'MSI' #only one of these: MSI or EXE (ignore MSU for now)
  # MSI
  silentArgs    = "/qn /norestart"
  validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
}

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | ForEach-Object { 
    $packageArgs['file'] = "$($_.UninstallString)"
    
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''
    }

    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | ForEach-Object {Write-Warning "- $($_.DisplayName)"}
}
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$packageName= 'microsoft-teams.install'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url32      = 'https://statics.teams.cdn.office.net/production-windows/1.3.00.26064/Teams_windows.msi'
$url64      = 'https://statics.teams.cdn.office.net/production-windows-x64/1.3.00.26064/Teams_windows_x64.msi'
$checksum32 = 'ac2c58703f0cc3fecdbdb45c16d3d6e455e3180595c25cb92acae67ef9404566'
$checksum64 = '5740e2eaf99b6022399d04cb654ad8efd332c84051801851b7c80730df7636bd'

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'MSI'
  url           = $url32
  url64bit      = $url64

  softwareName  = 'Teams Machine-Wide Installer'

  checksum      = $checksum32
  checksumType  = 'sha256'
  checksum64    = $checksum64
  checksumType64= 'sha256'

  silentArgs    = "/qn /norestart /l*v `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log`"" # ALLUSERS=1 DISABLEDESKTOPSHORTCUT=1 ADDDESKTOPICON=0 ADDSTARTMENU=0
  validExitCodes= @(0, 3010, 1641)
}

$pp = Get-PackageParameters

if ($pp['NoAutoStart']) {
  $packageArgs.silentArgs += ' OPTIONS="noAutoStart=true"'
}

if ($pp['AllUsers']) {
  $packageArgs.silentArgs += ' ALLUSERS=1'
}

Install-ChocolateyPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.24755 451533 Friday, September 25, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.21759 513711 Saturday, August 22, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.19173 196999 Friday, July 24, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.13565 385997 Thursday, June 4, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.12058 161772 Thursday, May 7, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.8663 100426 Thursday, April 16, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.4461 90980 Wednesday, March 25, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.3564 93541 Saturday, February 29, 2020 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.362 90501 Friday, January 31, 2020 Approved

Discussion for the Microsoft Teams Desktop App (Machine-Wide Install) Package

Ground Rules:

  • This discussion is only about Microsoft Teams Desktop App (Machine-Wide Install) and the Microsoft Teams Desktop App (Machine-Wide Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Microsoft Teams Desktop App (Machine-Wide Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus