Teams- end of the line.

[blu4]

Hi all,

 

I am really hoping someone could shed some light on an issue we've been having for quite a while. I reckon it was maybe in June/July, all of a sudden ALL of our student machines pop up with this:

 

 

In a nutshell, this is an issue for every single device because no matter if I update it on my profile or local admin profile, this pop up every time a student logs on. It's causing delays in learning and so far we had to resolve to using Teams Online (not ideal).

 

There is a "solution" here: Teams needs an update issue - WinCert

 

The solution above is really out of the question because I cannot do every single computer manually. So far I have tried doing the things below:

 

-Deploy the latest Teams.msi via SCCM

-Deploy Teams via the O365 Packager

 

Both of them give me the same results. There was a solution that the shortcut for Teams should be this so that it invokes the update as soon as it launches: %localappdata%\Microsoft\Teams\Update.exe --processStart "Teams.exe" but that doesn't work either.

 

So my plea, is there a way around this? Would appreciate all the help...

 

Cheers

[clareq]

Is it only happening for students? If a member of staff logs onto a student machine is it OK? If it is, that points to permissions - do students have the right to run Update.exe?

[3s-gtech]

I *think* you can update Teams app using a GPP update, copying new Teams files into a central deployment share then pushing them out from there with an Update command. No registry complications. Only requires one up-to-date copy on site to push out as a folder copy.

[blu4]

Is it only happening for students? If a member of staff logs onto a student machine is it OK? If it is, that points to permissions - do students have the right to run Update.exe?

 

No- it keeps happening to staff as well, sometimes it updates and sometimes it doesn't (but mostly doesn't).

 

- - - Updated - - -

 

I *think* you can update Teams app using a GPP update, copying new Teams files into a central deployment share then pushing them out from there with an Update command. No registry complications. Only requires one up-to-date copy on site to push out as a folder copy.

Do you have this running in your setup? Would appreciate ANYTHING only to get this image off the desktops ;<

[psydii]

This might help, after the first script block there is a script to remove teams for all users.

 

https://lazyadmin.nl/powershell/microsoft-teams-uninstall-reinstall-and-cleanup-guide-scripts/

[3s-gtech]

Yes, this is how I update it. It works pretty well - I copy the source files from the Teams install on my PC (no GPs applied) into a folder which GPP then copies to client local home areas in their AppData on logon.

[Koldov]

I don't use Teams and we don't use it as a school, but we have it installed for a couple of users.

 

Is this because of something like Teams installs per user in the UserProfile and needs to update something in there as well.

 

Would it mean that things like user permissions locked down for the students in those folders block it updating or some sort of SRP or Applocker policy, roaming profile, redirected appdata...?

 

There was a discussion about using a regedit or something that needed changing to make it install into Program Files rather than per user:

 

https://www.masterpackager.com/blog/mst-to-install-microsoft-teams-msi-vdi-to-regular-windows-10

 

But that sort of thing is at your own risk...

 

There's also these that might give you some other ideas:

 

http://www.edugeek.net/forums/educational-software/221091-installing-teams.html

 

http://www.edugeek.net/forums/office-software/220319-teams-client-not-updating-nothing-happens-if-staff-try-manually-update.html

 

http://www.edugeek.net/forums/cloud-services/216157-teams-desktop-version-school-pcs.html

 

http://www.edugeek.net/forums/windows-10/219523-how-do-i-push-out-ms-teams-all-teacher-pcs.html

 

http://www.edugeek.net/forums/cloud-services/216718-teams-per-machine-install.html

[MartinByard]

I presume you're getting this problem due to having the Teams Machine-Wide Installer on your computers (installed as part of Office 365 or pulled down through Office updates) and that never gets updated ... whilst once Teams is installed into someones profile, that version gets updated.

 

This is not an issue if you have static PCs with only one primary user, but falls over if they are hotdesks that dont get reimaged much.

 

The way we found to get round it is to download the latest version of the machine wide installer (link), extract the contents of it and copy the .exe into C:\Program Files (x86)\Teams Installer (for 32 bit office, 64 bit in C:\Program Files\Teams Installer). This will then mean that the version of Teams installed when someone new logs into the PC is up-to-date (admittedly, this does nothing for existing accounts).

 

Hope this helps....

[AM369]

We used to run into this issue though we've only installed the machine wide installer on staff and teaching pcs. Students use Teams through the browser only (automatically opens on a new tab) to avoid the updating issue.

 

For staff, we've added the installer/updater to an accessible location with the instructions of if you ever need to update Teams, run this, wait 2 minutes and try again. (Or rather we double click on it for them). We then update the machine wide installer through GPO every month just in case.

[free780]

There is a group policy setting to prevent launch from the machine wide installer.

 

Pre COVID I had a script that downloaded the latest version and pushed out shortcuts to start that file which in turn installed the latest version in the profile.

 

This was before the machine level installer.