Ansible
PS DSC
Downloads:
3,037,168
Downloads of v 1.0.2508703:
91,661
Last Update:
30 May 2025
Package Maintainer(s):
Software Author(s):
- Microsoft Corporation
Tags:
teams office 365 chat collaboration- Software Specific:
- Software Site
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Microsoft Teams (new client) Bootstrapper (Machine-Wide Install)
- 1
- 2
- 3
1.0.2508703 | Updated: 30 May 2025
- Software Specific:
- Software Site
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
3,037,168
Downloads of v 1.0.2508703:
91,661
Maintainer(s):
Software Author(s):
- Microsoft Corporation
Microsoft Teams (new client) Bootstrapper (Machine-Wide Install) 1.0.2508703
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Microsoft Corporation. The inclusion of Microsoft Corporation trademark(s), if any, upon this webpage is solely to identify Microsoft Corporation goods or services and not for commercial purposes.
- 1
- 2
- 3
This Package Contains an Exempted Check
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Microsoft Teams (new client) Bootstrapper (Machine-Wide Install), run the following command from the command line or from PowerShell:
To upgrade Microsoft Teams (new client) Bootstrapper (Machine-Wide Install), run the following command from the command line or from PowerShell:
To uninstall Microsoft Teams (new client) Bootstrapper (Machine-Wide Install), run the following command from the command line or from PowerShell:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download microsoft-teams-new-bootstrapper --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade microsoft-teams-new-bootstrapper -y --source="'INTERNAL REPO 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-new-bootstrapper -y --source="'INTERNAL REPO URL'"
$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-new-bootstrapper
win_chocolatey:
name: microsoft-teams-new-bootstrapper
version: '1.0.2508703'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'microsoft-teams-new-bootstrapper' do
action :install
source 'INTERNAL REPO URL'
version '1.0.2508703'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller microsoft-teams-new-bootstrapper
{
Name = "microsoft-teams-new-bootstrapper"
Version = "1.0.2508703"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'microsoft-teams-new-bootstrapper':
ensure => '1.0.2508703',
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 was approved as a trusted package on 30 May 2025.
The Teams installer installs the Teams MSIX package on a target computer, making sure that Teams can interoperate correctly with Office and other Microsoft software.
TeamsBootstrapper is a lightweight online installer with a headless command-line interface. It allows admins to provision (install) the app for all users on a given target computer.
When TeamsBootstrapper is run on a computer:
- The installer downloads the latest Teams MSIX package from Microsoft
- The installer installs the Teams application for all users on the computer, and any users who may be added afterwards.
Users who have installed a different Teams version will have their version replaced with the provisioned version.
Package Parameters
/VDI- The package will install the Teams Meeting Add-in for all users
Package Specific
Note that TeamsBootstrapper.exe will cause the the latest Teams MSIX package to be installed from Microsoft. Once Teams is installed it is self-updating. As such there's likely no need to install updates of this Chocolatey package.
The package version is based on the 'product version' property of TeamsBootstrapper.exe
# Ensure the script runs with administrative privileges
if (-not ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) {
Write-Error "This script must be run as an Administrator."
exit
}
# Identify and Remove MS Teams Installations
Write-Host "Identifying installed MS Teams packages for all users..."
$teamsPackages = Get-AppxPackage -AllUsers | Where-Object {$_.PackageFullName -like "*Teams*"}
$provisionedPackages = Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -like "*Teams*"}
if ($teamsPackages.Count -eq 0 -and $provisionedPackages.Count -eq 0) {
Write-Host "No MS Teams installations found."
} else {
Write-Host "Found the following MS Teams packages:"
$teamsPackages | ForEach-Object {Write-Host $_.PackageFullName}
$provisionedPackages | ForEach-Object {Write-Host $_.PackageName}
}
# Remove provisioned MS Teams packages
$provisionedPackages | ForEach-Object {
if ($_) {
Write-Host "Removing provisioned package: $($_.PackageName)"
Dism /Online /Remove-ProvisionedAppxPackage /PackageName:$($_.PackageName)
} else {
Write-Host "No provisioned packages to remove."
}
}
# Remove installed MS Teams packages for all users
$teamsPackages | ForEach-Object {
if ($_) {
Write-Host "Removing installed package for all users: $($_.PackageFullName)"
Remove-AppxPackage -AllUsers -Package $_.PackageFullName
} else {
Write-Host "No installed packages to remove."
}
}
# Uninstall Microsoft Teams Meeting Add-in for Microsoft Office Using MSIExec
Write-Host "Uninstalling Microsoft Teams Meeting Add-in for Microsoft Office..."
# Check if WMIC is available and try to get the GUID of the add-in
try {
if (Get-Command wmic -ErrorAction SilentlyContinue) {
Write-Host "WMIC is available. Searching for the Teams Meeting Add-in GUID..."
# Find the Teams Meeting Add-in for Microsoft Office GUID using WMIC
$teamsAddinGUID = (wmic product where "name like 'Microsoft Teams Meeting Add-in for Microsoft Office'" get IdentifyingNumber | findstr /i /r "[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}").Trim()
if (-not [string]::IsNullOrEmpty($teamsAddinGUID)) {
Write-Host "Found Microsoft Teams Meeting Add-in for Microsoft Office, GUID: $teamsAddinGUID"
Write-Host "Uninstalling using MSIExec..."
# Use msiexec to uninstall the add-in by GUID
$msiExecCommand = "msiexec.exe /x $teamsAddinGUID /quiet /norestart"
Invoke-Expression $msiExecCommand
Write-Host "Uninstall process initiated for Microsoft Teams Meeting Add-in for Microsoft Office."
} else {
Write-Host "No GUID found for Microsoft Teams Meeting Add-in for Microsoft Office. Skipping uninstallation."
}
} else {
Write-Host "WMIC is not available on this system."
}
}
catch {
Write-Host "An error occurred while trying to get the Microsoft Teams Meeting Add-in GUID: $_"
}
# Manually Delete Global Teams-Related Folders
Write-Host "Deleting global Teams-related folders..."
$globalFoldersToDelete = @(
"C:\Program Files (x86)\Microsoft\Teams",
"C:\Program Files (x86)\Microsoft\TeamsMeetingAddin",
"C:\Program Files (x86)\Microsoft\TeamsPresenceAddin"
)
foreach ($folder in $globalFoldersToDelete) {
if (Test-Path $folder) {
Write-Host "Deleting folder: $folder"
Remove-Item -Recurse -Force -Path $folder
} else {
Write-Host "Folder not found: $folder"
}
}
# Clean up Scheduled Tasks related to Teams
Write-Host "Cleaning up any leftover scheduled tasks related to Microsoft Teams..."
$scheduleTasks = Get-ScheduledTask | Where-Object { $_.TaskName -like "*Teams*" }
if ($scheduleTasks) {
$scheduleTasks | ForEach-Object {
Write-Host "Removing scheduled task: $($_.TaskName)"
Unregister-ScheduledTask -TaskName $_.TaskName -Confirm:$false
}
} else {
Write-Host "No Teams-related scheduled tasks found."
}
# Remove Chocolatey package folder from lib directory
Write-Host "Cleaning up Chocolatey package folder for Microsoft Teams 2..."
$chocoPackageFolder = Join-Path $env:ChocolateyInstall "lib\microsoft-teams-new-bootstrapper"
if (Test-Path $chocoPackageFolder) {
Write-Host "Deleting Chocolatey package folder: $chocoPackageFolder"
Remove-Item -Recurse -Force -Path $chocoPackageFolder
} else {
Write-Host "No Chocolatey package folder found for Microsoft Teams 2."
}
Write-Host "Microsoft Teams 2 uninstallation and cleanup process completed successfully." 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.
2023 Microsoft Corporation
This package has no dependencies.
Ground Rules:
- This discussion is only about Microsoft Teams (new client) Bootstrapper (Machine-Wide Install) and the Microsoft Teams (new client) Bootstrapper (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 (new client) Bootstrapper (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.