Apr 24 2020 04:27 AM
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?
Apr 24 2020 04:43 AM
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.
Apr 24 2020 05:01 AM
@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.
Apr 28 2020 07:20 AM
I would have hopened that a sign out from teams and restarting my computer would solve it. But it did not. @ChristianBergstrom
Apr 28 2020 07:27 AM
@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."
Apr 29 2020 09:49 AM - edited Apr 29 2020 09:50 AM
Check this out:
https://answers.microsoft.com/en-us/msteams/forum/all/loss-of-blur-and-background-feature-with-micro...
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.
Apr 29 2020 10:39 AM
Apr 30 2020 01:25 AM
@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 ;)
Jul 23 2020 07:07 AM - edited Jul 23 2020 07:10 AM
@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-pe...) 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-mi...) 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-a47... 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 :smiling_face_with_smiling_eyes:
Jul 23 2020 10:26 AM
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
Nov 19 2020 06:45 AM
@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.
Jan 11 2021 01:25 PM
@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).
Jan 22 2021 09:12 PM
SolutionPlease try the next Powershell command
Update a Teams App in Microsoft Teams.
Update-TeamsAppInstallation
[-AppInstallationId <String>]
[-AppId <String>]
-TeamId <String>
[-Permissions <String>]
[<CommonParameters>]
Update-TeamsAppInstallation
[-AppInstallationId <String>]
[-AppId <String>]
-UserId <String>
[-Permissions <String>]
[<CommonParameters>]
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.
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.
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.
Teams App identifier in Microsoft Teams.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
Installation identifier of the Teams App.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
RSC permissions for the Teams App.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
Team identifier in Microsoft Teams.
Type: | String |
Aliases: | GroupId |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
User identifier in Microsoft Teams.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
System.String
System.Object
Thanks
Host Zambrana
Microsoft L400 Teams Specialist
Jan 22 2021 09:13 PM
Peter try this please
Update a Teams App in Microsoft Teams.
Update-TeamsAppInstallation
[-AppInstallationId <String>]
[-AppId <String>]
-TeamId <String>
[-Permissions <String>]
[<CommonParameters>]
Update-TeamsAppInstallation
[-AppInstallationId <String>]
[-AppId <String>]
-UserId <String>
[-Permissions <String>]
[<CommonParameters>]
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.
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.
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.
Teams App identifier in Microsoft Teams.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
Installation identifier of the Teams App.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
RSC permissions for the Teams App.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
Team identifier in Microsoft Teams.
Type: | String |
Aliases: | GroupId |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
User identifier in Microsoft Teams.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
System.String
System.Object
Thanks Host Zambrana
Microsoft L400 Teams specialist
Jan 23 2021 01:42 AM
Jan 22 2021 09:12 PM
SolutionPlease try the next Powershell command
Update a Teams App in Microsoft Teams.
Update-TeamsAppInstallation
[-AppInstallationId <String>]
[-AppId <String>]
-TeamId <String>
[-Permissions <String>]
[<CommonParameters>]
Update-TeamsAppInstallation
[-AppInstallationId <String>]
[-AppId <String>]
-UserId <String>
[-Permissions <String>]
[<CommonParameters>]
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.
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.
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.
Teams App identifier in Microsoft Teams.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
Installation identifier of the Teams App.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
RSC permissions for the Teams App.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
Team identifier in Microsoft Teams.
Type: | String |
Aliases: | GroupId |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
User identifier in Microsoft Teams.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True |
Accept wildcard characters: | False |
System.String
System.Object
Thanks
Host Zambrana
Microsoft L400 Teams Specialist