Downloads:

7,581,028

Downloads of v 1.3.00.28779:

395,863

Last Update:

07 Nov 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)

This is not the latest version of Microsoft Teams Desktop App (Machine-Wide Install) available.

  • 1
  • 2
  • 3

1.3.00.28779 | Updated: 07 Nov 2020

Downloads:

7,581,028

Downloads of v 1.3.00.28779:

395,863

Maintainer(s):

Software Author(s):

  • Microsoft Corporation

  • 1
  • 2
  • 3
Microsoft Teams Desktop App (Machine-Wide Install) 1.3.00.28779

This is not the latest version of Microsoft Teams Desktop App (Machine-Wide Install) available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Deployment Method: Individual Install, Upgrade, & Uninstall

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:

>

Deployment Method:

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade microsoft-teams.install -y --source="'INTERNAL REPO URL'" --version="'1.3.00.28779'" [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="'INTERNAL REPO URL'" --version="'1.3.00.28779'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install microsoft-teams.install
  win_chocolatey:
    name: microsoft-teams.install
    version: '1.3.00.28779'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'microsoft-teams.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.3.00.28779'
end

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


cChocoPackageInstaller microsoft-teams.install
{
    Name     = "microsoft-teams.install"
    Version  = "1.3.00.28779"
    Source   = "INTERNAL REPO URL"
}

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


package { 'microsoft-teams.install':
  ensure   => '1.3.00.28779',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. 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 07 Nov 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.28779/Teams_windows.msi'
$url64      = 'https://statics.teams.cdn.office.net/production-windows-x64/1.3.00.28779/Teams_windows_x64.msi'
$checksum32 = '3d6114134a5abe9e73eb0ce953cd3f54be0db17e7e71893b445a2b410c9c0bd8'
$checksum64 = 'bd405f1fd163bd703fb9615c28c93506073d92674fed4261a950a1350febb8c5'

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

Add to Builder Version Downloads Last Updated Status
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.26376 682284 Thursday, September 30, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.22976 36 Friday, September 24, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.22472 606869 Saturday, August 28, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.19572 527896 Tuesday, July 27, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.16575 403090 Thursday, July 1, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.11161 707243 Tuesday, May 18, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.8872 479057 Thursday, April 8, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.7174 140164 Thursday, March 25, 2021 Approved
Microsoft Teams Desktop App (Machine-Wide Install) 1.4.00.4167 228877 Saturday, February 27, 2021 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