Forum Discussion

ThomasSteibl's avatar
ThomasSteibl
Brass Contributor
Apr 24, 2020
Solved

Teams client not updating

A couple of clients within our company are already running with the Teams Version 1.3.00.9267 but on most of the other users (including me) we are still on the Version 1.3.00.8663 and there is no new...
release preference
teams version
update
  • Hosito's avatar
    Hosito
    Jan 23, 2021

    ThomasSteibl 

    Please try the next Powershell command 

    Update-TeamsAppInstallation

    Module:
    https://docs.microsoft.com/en-us/powershell/module/teams/?view=teams-ps

    Update a Teams App in Microsoft Teams.

    Syntax

    PowerShell 
    Update-TeamsAppInstallation
      [-AppInstallationId <String>]
      [-AppId <String>]
      -TeamId <String>
      [-Permissions <String>]
      [<CommonParameters>]
    PowerShell 
    Update-TeamsAppInstallation
      [-AppInstallationId <String>]
      [-AppId <String>]
      -UserId <String>
      [-Permissions <String>]
      [<CommonParameters>]

    Description

    Update a Teams App in Microsoft Teams.

    Note: This cmdlet is part of the Public Preview version of Teams PowerShell Module, for more information see https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install#install-teams-powershell-public-preview and also see https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-release-notes.

    Examples

    Example 1

    PowerShell 
    PS C:\> Update-TeamsAppInstallation -AppId b9cc7986-dd56-4b57-ab7d-9c4e5288b775 -TeamId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df

    This example updates a Teams App in Microsoft Teams specifying its AppId and TeamId.

    Example 2

    PowerShell 
    PS C:\> Update-TeamsAppInstallation -AppId b9cc7986-dd56-4b57-ab7d-9c4e5288b775 -TeamId 31f1ff6c-d48c-4f8a-b2e1-abca7fd399df -Permissions "TeamSettings.Read.Group ChannelMessage.Read.Group"

    This example updates a Teams App in Microsoft Teams specifying its AppId and TeamId and RSC Permissions.

    Parameters

    -AppId

    Teams App identifier in Microsoft Teams.

    Type: String
    Position: Named
    Default value: None
    Accept pipeline input: True
    Accept wildcard characters: False
    -AppInstallationId

    Installation identifier of the Teams App.

    Type: String
    Position: Named
    Default value: None
    Accept pipeline input: True
    Accept wildcard characters: False
    -Permissions

    RSC permissions for the Teams App.

    Type: String
    Position: Named
    Default value: None
    Accept pipeline input: True
    Accept wildcard characters: False
    -TeamId

    Team identifier in Microsoft Teams.

    Type: String
    Aliases: GroupId
    Position: Named
    Default value: None
    Accept pipeline input: True
    Accept wildcard characters: False
    -UserId

    User identifier in Microsoft Teams.

    Type: String
    Position: Named
    Default value: None
    Accept pipeline input: True
    Accept wildcard characters: False

    Inputs

    System.String

    Outputs

    System.Object

     

    Thanks 

    Host Zambrana 

    Microsoft L400 Teams Specialist 

CG-1717's avatar
CG-1717
Brass Contributor
Jul 23, 2020

rs_oakford 

Thank you for putting this out there! Our case is exactly the same. We have raised this question/concern to our account team as well and seems that no one has the right answer. All we hear is that features roll out in waves and now we know that users with the same exact version have not the same features (what??!! - first product ever that handle changes like this?) What is the version for then? What are the differences between versions if it's not features?. 

It has been extremely difficult and frustrating to manage changes on Teams for us. The video backgrounds feature started showing up first week of April for us, then only a couple of users would get it from time to time... It's almost end of July we still have users that do not have that feature available! Completely unacceptable. Users get frustrated and what's worst is that we do not have an accurate answer for them. 

Would love to hear something different from someone at Microsoft that is not what we have already heard which does not explain anything at all. 

 

Thanks

Cristina

MTLang's avatar
MTLang
Copper Contributor
Nov 19, 2020

CG-1717 "It's almost end of July we still have users that do not have that feature available!" It's not November 2020, and I have the exact same problem. I cannot use the desktop client at all. It won't open, because it says it needs an update, but clicking on the "update" button does nothing. 

  • K_Scrupa's avatar
    K_Scrupa
    Copper Contributor
    Jan 11, 2021

    MTLangLike you, we noticed a similar problem, even well after everyone else got an update.

     

    The cause was our 3rd-party endpoint protection squelching 'Update.exe  --processStart "Teams.exe"' for some users' profiles when we first started using Teams.  We allowlisted it, but the ones that were initially blocked still weren't updating. After a fresh deployment, they started getting updates again.

     

    n.b.: We are using the Teams MSI & exe pushed through Endpoint Config Mgr, (not deployed through O365).

Resources