Feb 20 2024 12:37 AM - edited Feb 20 2024 04:39 AM
Dear Community,
we want to enroll most of the Microsoft 365 Apps via Intune --> Apps --> Companyportal.
Everything works fine for Word, Exccel, Outlook etc. but we do not get Teams installed!? It's selected like the others:
We do see Microsoft 365 Apps within the companyportal on our "Entra joined devices" - installation runs quiet fast and everything works fine, only Teams is missing.
Do you have any idea what the problem could be!? I've already looked up some posts. Most of them were saying, that it should work after Mirosoft fixed it (status: Nov. 2023).
Thanks a lot guys!
Feb 21 2024 09:14 AM
Feb 21 2024 09:42 PM
Feb 22 2024 04:21 AM
Feb 22 2024 04:22 AM
Feb 23 2024 07:02 AM
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
Feb 23 2024 08:49 AM
Confirmed resolved for us.
In new policies it's call explicit allow unlock.
Feb 23 2024 09:15 AM
@ITInfra Nice, where exactly and what setting did you change?
Feb 23 2024 10:04 AM
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:
# 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.
Feb 24 2024 01:41 PM
Feb 26 2024 04:52 AM
thanks for your post.
I've created an intunewin-file and created a new app. I follow all of your steps but the app will not be installed.
can you figured out what i did wrong?
thanks a lot
Feb 26 2024 04:58 AM - edited Feb 26 2024 05:05 AM
Looks ok to me. Double check c:\program files\windowsapps has the msteams_* folder. Easiest way to see it is open notepad as admin and then manually navigate to the path (it's a hidden folder). Not sure if it's different for your region.
Run the script manually with the exit codes and if it's good it should say it's installed.
# Define the path where New Microsoft Teams is installed
$teamsPath = "%localappdata%\Microsoft\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."
} else {
# Display message if Microsoft Teams is not found
Write-Host "Microsoft Teams client not found."
}
Feb 27 2024 01:02 AM
thanks :)
May 23 2024 07:23 AM
Jun 04 2024 10:22 PM
@michaelguthrie We escalated admin privileges to get some users to install as we had teams also added as a universal LOB, however it still didn't work. Did you have it added as the M365 app as well when trying this?
I'm also not fond of this route for lack of auto update
Jun 05 2024 01:14 AM
Don't use the bootstrapper like Microsoft states in their docs? Asking for trouble imo. Also if you use the bootstrapper the user will always get the latest msix installer.
Jun 05 2024 05:42 AM