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 version regarding the update check within Teams. My user is the only one with release preference: targeted release within the O365 admin portal.Any ideas?

ThomasSteibl Please try the next Powershell command Update-TeamsAppInstallation Module: MicrosoftTeamsPowerShell Update a Teams App in Microsoft Teams. Syntax PowerShellCopy Update-TeamsAppInstallation [-AppInstallationId <String>] [-AppId <String>] -TeamId <String> [-Permissions <String>] [<CommonParameters>] PowerShellCopy 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 Install Teams PowerShell public preview and also see Microsoft Teams PowerShell Release Notes. Examples Example 1 PowerShellCopy 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 PowerShellCopy 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. TABLE 1 Type: String Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -AppInstallationId Installation identifier of the Teams App. TABLE 2 Type: String Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -Permissions RSC permissions for the Teams App. TABLE 3 Type: String Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -TeamId Team identifier in Microsoft Teams. TABLE 4 Type: String Aliases: GroupId Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -UserId User identifier in Microsoft Teams. TABLE 5 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

Teams client not updating | Microsoft Community Hub

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

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

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

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

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

CG-1717
Brass Contributor
Apr 29, 2020
ThomasSteibl

Check this out:
https://answers.microsoft.com/en-us/msteams/forum/all/loss-of-blur-and-background-feature-with-microsoft/62329b94-8e48-45fa-8e66-407eca706ea3?page=2

I was looking for some info also since we had the same (some users with the 1.3.00.8663 version that had the Teams meetings backgrounds feature available and others with the 1.3.00.9267 where suddenly some features disappeared). Looks like there is an "issue" with this version so I would not be surprised if they "stopped" releasing anything until they figure it out.
- PeterRising
  MVP
  Apr 29, 2020
  CG-1717
  
  That sounds like a reasonable assumption if you have seen issues with 1.3.00.9267.
- ChristianBergstrom
  Silver Contributor
  Apr 30, 2020
  ThomasSteibl Hi, just want to let you know I wiped the Teams cache and rebooted, no difference. I then uninstalled Teams and rebooted, installed the desktop app again (via Teams web). Got an pretty old version. Actually succeeded in updating that one. But no difference. I am stuck on 1.3.00.8663 with a few of my colleagues having the later release. In other words, just a confirmation of CG-1717 post 😉
rs_oakford
Iron Contributor
Jul 23, 2020
ThomasSteibl, I had a similar question off the back of a recent UserVoice announcement (on https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17010055-show-video-for-all-people-in-video-meeting) that 7x7 was enabled for "desktop Teams client 19173 or later" :
In the comments of the associated blog post (see https://techcommunity.microsoft.com/t5/microsoft-teams-blog/new-meeting-and-calling-experience-in-microsoft-teams/bc-p/1540827) a conversation ensued that covered two points: (a) how to get the latest client version and (b) do which features are available depend only on the client version?

(a) It's still not clear to me how to download the latest client version (checking for updates in-app clearly don't trigger a download of the latest release). https://support.microsoft.com/en-us/office/what-s-new-in-microsoft-teams-d7092a6d-c896-424c-b362-a472d5f105de only shows app versions for each date on the "Desk phones" tab. Presumably, if you know which version numbers exist, you could download it directly by replacing the relevant part of the URI: https://statics.teams.cdn.office.net/production-windows-x64/1.3.00.19565/Teams_windows_x64.exe

(b) It turns out, a given user's Office 365 release settings didn't have an impact on the 7x7 (preview) feature being available (even when users in that same tenant were all on "desktop Teams client 19173 or later"), and within a single tenant only select users might have the feature available.

It would be great to get an official response on this - I missed the most recent Ask Microsoft Anything (AMA) and can't seem to start a new conversation on the https://techcommunity.microsoft.com/t5/microsoft-teams-ama/bd-p/MicrosoftTeamsAMA board so am adding my comment here in the hope someone from Microsoft with some insider knowledge will respond 😊
- 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
    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.
PeterRising
MVP
Apr 24, 2020
ThomasSteibl

I am also on 1.3.00.8663 and a check for updates does not bring anything new. Are the clients with the newer versions on Windows Insider builds or something like that? Teams updates kind of "are what they are" and there is very little control over them as things stand.
- Hosito
  Microsoft
  Jan 23, 2021
  PeterRising
  
  Peter try this please
  
  Update-TeamsAppInstallation
  
  Module:
  
  MicrosoftTeamsPowerShell
  
  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 Install Teams PowerShell public preview and also see Microsoft 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.
  
  TABLE 1
  
  Type: String
  
  Position: Named
  
  Default value: None
  
  Accept pipeline input: True
  
  Accept wildcard characters: False
  
  -AppInstallationId
  
  Installation identifier of the Teams App.
  
  TABLE 2
  
  Type: String
  
  Position: Named
  
  Default value: None
  
  Accept pipeline input: True
  
  Accept wildcard characters: False
  
  -Permissions
  
  RSC permissions for the Teams App.
  
  TABLE 3
  
  Type: String
  
  Position: Named
  
  Default value: None
  
  Accept pipeline input: True
  
  Accept wildcard characters: False
  
  -TeamId
  
  Team identifier in Microsoft Teams.
  
  TABLE 4
  
  Type: String
  
  Aliases: GroupId
  
  Position: Named
  
  Default value: None
  
  Accept pipeline input: True
  
  Accept wildcard characters: False
  
  -UserId
  
  User identifier in Microsoft Teams.
  
  TABLE 5
  
  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
  - ChristianBergstrom
    Silver Contributor
    Jan 23, 2021
    Hi, never seen this before. How would that be used to force a client update of the Teams desktop app to a newer version as the topic of the conversation asks?
    
    For reference (current workaround)
    https://techcommunity.microsoft.com/t5/microsoft-teams/force-teams-desktop-client-update/m-p/2056566
ChristianBergstrom
Silver Contributor
Apr 24, 2020
ThomasSteibl Hello Thomas, I don't know if you're familiar with the Teams client update process, but this is how it works https://docs.microsoft.com/en-us/microsoftteams/teams-client-update and could possibly explain the scenario you're describing.

I'm also on version 1.3.00.8663 and the problem for me is that my laptop is never idle 🙂 I have noticed a couple of times that functionality appear/reappear when doing a manual sign out/sign in, but that's just a general tip.
- ThomasSteibl
  Brass Contributor
  Apr 28, 2020
  I would have hopened that a sign out from teams and restarting my computer would solve it. But it did not. ChristianBergstrom
  - ChristianBergstrom
    Silver Contributor
    Apr 28, 2020
    ThomasSteibl Hello Thomas, same here actually. But as I mentioned in the previous post it's going to happen in idle mode.
    
    "Teams desktop client updates are released every two weeks. If a critical update is required, Teams will bypass this schedule and release the update as soon as it’s available.
    The desktop client updates itself automatically. Teams checks for updates every few hours behind the scenes, downloads it, and then waits for the computer to be idle before silently installing the update.
    
    Users can also manually download updates by clicking Check for updates on the Profile drop-down menu on the top right of the app. If an update is available, it will be downloaded and silently installed when the computer is idle."
Hosito
Microsoft
Jan 23, 2021
ThomasSteibl

Please try the next Powershell command

Update-TeamsAppInstallation

Module:

MicrosoftTeamsPowerShell

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 Install Teams PowerShell public preview and also see Microsoft 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.

TABLE 1

Type: String

Position: Named

Default value: None

Accept pipeline input: True

Accept wildcard characters: False

-AppInstallationId

Installation identifier of the Teams App.

TABLE 2

Type: String

Position: Named

Default value: None

Accept pipeline input: True

Accept wildcard characters: False

-Permissions

RSC permissions for the Teams App.

TABLE 3

Type: String

Position: Named

Default value: None

Accept pipeline input: True

Accept wildcard characters: False

-TeamId

Team identifier in Microsoft Teams.

TABLE 4

Type: String

Aliases: GroupId

Position: Named

Default value: None

Accept pipeline input: True

Accept wildcard characters: False

-UserId

User identifier in Microsoft Teams.

TABLE 5

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

Forum Discussion

Teams client not updating

Update-TeamsAppInstallation

Syntax

Description

Examples

Example 1

Example 2

Parameters

Inputs

Outputs

Update-TeamsAppInstallation

Syntax

Description

Examples

Example 1

Example 2

Parameters

Inputs

Outputs

Update-TeamsAppInstallation

Syntax

Description

Examples

Example 1

Example 2

Parameters

Inputs

Outputs

Share

Resources