New Teams Won't Show in Start Menu or Add/Remove Programs After Intune Install

[A-Dog]

Hi..

We are starting to add the new Teams app to our Intune autopilot deployment sequence. We are using the teamsbootstrapper.exe file to install

The problem is that while we know it does install as we can see the Teams folder in c:\ProgramFiles\WindowsApps directory, Teams icon/shortcut does not get added to the Windows start menu nor is it listed in add/remove programs.

In Intune we've tried the following install commands:

1: teamsbootstrapper.exe -p

2: and this powershell script:

function ProvisionTeams {
    param (
        [string]$ProvisionMode
    )

    
    if ($ProvisionMode -eq "AllUsers") {

        Start-Process -FilePath ".\teamsbootstrapper.exe" -ArgumentList "-p" -Wait -WindowStyle Hidden
    }
    elseif ($ProvisionMode -eq "CurrentUser") {
        Start-Process -FilePath ".\teamsbootstrapper.exe" -ArgumentList "-p" -Wait -WindowStyle Hidden
    }
    else {
        Write-Host "Invalid ProvisionMode specified. Use 'AllUsers' or 'CurrentUser'."
    }
}

# Provision for all users
ProvisionTeams -ProvisionMode "AllUsers"

# Provision for the current user
ProvisionTeams -ProvisionMode "CurrentUser"

And neither yield allow for Teams to show up in start menu for users to access.

Anyone got any ideas????

[#2]

Hi,

Does the new Teams appear for the user after a restart of the device?

[#3]

@NicklasOlsen  No sir, it does not.

[#4]

Try to follow this guide, I have tried and it worked without any issues 🙂

https://cloudinfra.net/deploy-new-microsoft-teams-app-on-windows-using-intune/

[#5]

Yep.. done that, and no change. Everything looks good when deployed outside of autopilot, but it's autopilot where we see this issue and need it fixed so we can give users a machine with everything setup correctly.

[#6]

When deployed via Autopilot, and you restart the PC. What happens when the user logs in again, does Teams become available for the user?

Which context are you deploying the application?

[#7]

We've deployed the app as in both the system and user context. No user ever sees the app.
Is there a "provision teams" command with tnbe new teams that's similar to the available switch in the old teams msi installer?

[#8]

Hi A-Dog,

I'm not quite sure, I understand the question.
However, this is the official deployment guide for the new Teams from Microsoft:

https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client

[#9]

Yes.. that's the guide we followed when we first started testing. Teams will NOT show up in Start menu / List of apps when installed via Autopilot.

If installed from company portal or as a required install outside of autopilot there is no issue.

[#10]

Sorry, I haven't had the time to test with Autopilot. I will try one of the next days 🙂
How are you deploying it at the moment?

[#11]

@NicklasOlsen 

We deploy as a win32 app with the system behavior.

the install command is teamsbootstrapper.exe -p

[#12]

@A-Dog 

we have the same issue and i think its related to the detection script. the script from this link only checks

if the package is under C:\Program Files\WindowsApps. 

This doesnt check if its actually installed and useable for the user. if the check only checks the presence of the bootstrapper or the appx file but doesnt check if its installed for the user -> useless script.

i work on a detection based on the install status of a Appx product. it must be in the list of installed software products. thats what i would check against

[#13]

We've had a similar problem.
Not using Intune, but installed Teams with the teamsbootstrapper.exe in non-persistent VDI with FSlogix (roaming profiles).

Teams was showing in admin context, not in user context. After reading and applying this article: https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/mysteriously-disappearing-st..., Problem solved.

[#14]

Finally found a solution for Intune.

Despite what Microsoft claims on the Microsoft Learn page, you don't need the bootstrapper..
Just upload the MSIX to intune and let it run under user context.

Ps. I work at a MSP.
Only saw this behavior with Hybrid joined devices.
When only using Entra joined we are able to get this working like it says on the learn page.

Hope this helps someone!