Forum Discussion
Microsoft 365 Apps - Teams not installed (Using Company Portal)
- ITInfraFeb 23, 2024Copper Contributor
We think we've fixed ours. Rogue setting blocking store apps that aren't trusted, e.g. msix. Not 100% but manually changing the reg key allowed it to install. CasparAbo
- ITInfraFeb 23, 2024Copper Contributor
First check here: CasparAbo
Trust apps needs to be 1, if it is then try the below. If it isn't then you're probably blocking store apps by GPO/Intune policies.
If it is, this is what we did: Removed Teams from the 365 apps installer in Intune
Created a new Teams app from https://go.microsoft.com/fwlink/?linkid=2243204&clcid=0x409
Settings:
Install commandteamsbootstrapper.exe -pUninstall commandteamsbootstrapper.exe -xInstallation time required (mins)60Allow available uninstallYesInstall behaviorSystemDevice restart behaviorApp install may force a device restartReturn codes0 Success1707 Success3010 Soft reboot1641 Hard reDetection script:# Define the path where New Microsoft Teams is installed
$teamsPath = "C:\Program Files\WindowsApps"# Define the filter pattern for Microsoft Teams installer
$teamsInstallerName = "MSTeams_*"# Retrieve items in the specified path matching the filter pattern
$teamsNew = Get-ChildItem -Path $teamsPath -Filter $teamsInstallerName# Check if Microsoft Teams is installed
if ($teamsNew) {
# Display message if Microsoft Teams is found
Write-Host "New Microsoft Teams client is installed."
exit 0
} else {
# Display message if Microsoft Teams is not found
Write-Host "Microsoft Teams client not found."
exit 1
}I think because 365 Apps was device pushed it had no license, so didn't install Teams. This way installs it like any other app, you just need to keep the bootstrapper up to date. This way will keep the latest Teams installing for each build though.
- ITInfraFeb 23, 2024Copper Contributor
Confirmed resolved for us.
In new policies it's call explicit allow unlock.