Forum Discussion
Teams client not updating
- Jan 23, 2021
Please try the next Powershell command
Update-Teams
App Installation - Module:
- https://docs.microsoft.com/en-us/powershell/module/teams/?view=teams-ps
Update a Teams App in Microsoft Teams.
Syntax
PowerShellUpdate-TeamsAppInstallation [-AppInstallationId <String>] [-AppId <String>] -TeamId <String> [-Permissions <String>] [<CommonParameters>]
PowerShellUpdate-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
PowerShellPS 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
PowerShellPS 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
-AppIdTeams App identifier in Microsoft Teams.
TABLE 1 Type: String Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -AppInstallationIdInstallation identifier of the Teams App.
TABLE 2 Type: String Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -PermissionsRSC permissions for the Teams App.
TABLE 3 Type: String Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -TeamIdTeam identifier in Microsoft Teams.
TABLE 4 Type: String Aliases: GroupId Position: Named Default value: None Accept pipeline input: True Accept wildcard characters: False -UserIdUser 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
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.
I would have hopened that a sign out from teams and restarting my computer would solve it. But it did not. ChristianBergstrom
- ChristianBergstromApr 28, 2020Silver Contributor
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."