Ansible
PS DSC
Downloads:
1,907,381
Downloads of v 1.0.2414501.20241115:
93
Last Update:
18 Dec 2024
Published Date:
18 Dec 2024
Reviewed Date:
02 Dec 2024
Reviewer:
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)
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
1.0.2414501.20241115 | Updated: 18 Dec 2024
- 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:
1,907,381
Downloads of v 1.0.2414501.20241115:
93
Published:
18 Dec 2024
Reviewed:
02 Dec 2024
Reviewer:
Maintainer(s):
Software Author(s):
- Microsoft Corporation
Microsoft Teams (new client) Bootstrapper (Machine-Wide Install) 1.0.2414501.20241115
(Waiting for Maintainer to take corrective action)
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
Some Checks Are Exempted or Have Failed
Not All Tests Have Passed
Validation Testing Failed
Verification Testing Exemption:
It requires at least Windows 10 version 10.0.19041 (which is newer than the test environment)
Scan Testing Pending
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
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." No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.
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.
flcdrg (maintainer) on 14 Nov 2024 21:56:25 +00:00:
User 'flcdrg' (maintainer) submitted package.
chocolatey-ops (reviewer) on 14 Nov 2024 22:29:58 +00:00:
microsoft-teams-new-bootstrapper has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
flcdrg (maintainer) on 14 Nov 2024 23:40:35 +00:00:
User 'flcdrg' (maintainer) submitted package.
chocolatey-ops (reviewer) on 15 Nov 2024 00:13:52 +00:00:
microsoft-teams-new-bootstrapper has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
flcdrg (maintainer) on 27 Nov 2024 07:57:10 +00:00:
User 'flcdrg' (maintainer) submitted package.
chocolatey-ops (reviewer) on 27 Nov 2024 08:31:37 +00:00:
microsoft-teams-new-bootstrapper has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Windos (reviewer) on 02 Dec 2024 02:59:25 +00:00:
Validation Status Change - Validation tests have been set to rerun.
chocolatey-ops (reviewer) on 02 Dec 2024 03:00:02 +00:00:
microsoft-teams-new-bootstrapper has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Windos (reviewer) on 02 Dec 2024 03:00:58 +00:00:
Validation Status Change - Validation tests have been set to rerun.
chocolatey-ops (reviewer) on 02 Dec 2024 03:01:35 +00:00:
microsoft-teams-new-bootstrapper has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
flcdrg (maintainer) on 18 Dec 2024 10:31:37 +00:00:
User 'flcdrg' (maintainer) submitted package.
chocolatey-ops (reviewer) on 18 Dec 2024 11:05:34 +00:00:
microsoft-teams-new-bootstrapper has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
chocolatey-ops (reviewer) on 07 Jan 2025 10:33:13 +00:00:
We've found microsoft-teams-new-bootstrapper v1.0.2414501.20241115 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.