question

Franois-0770 avatar image
0 Votes"
Franois-0770 asked JoshuaHenderson-4455 commented

Upgrading Teams Machine wide installer

Hi,

We are installing Teams with a machine-wide installer. After updating the machine wide installer on computer, if Teams start, it will just loop with a white screen and never reach the teams interface.

I found by uninstalling Teams on each user profile then Teams is updating correctly.

Am I correct thinking after upgrading the MSI, I need uninstalling the Teams in each user profile the starting Teams to get update?

Thanks

office-teams-windows-itpro
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Teams deployment/management is genuinely one of the dumbest scenarios I've ever had to deal with!

We have experienced the same kinds of issues where there was a bug in a specific build of Teams that affected all users on a machine. Would you believe that this specific build was the one the machine wide installer was pushing to each user.
The per user install was not updating automatically for any user on this machine, therefore all users had this bug until they manually checked for updates.

We should not have to deal with update issues on a per user basis. We also wanted to know how to update the version of the machine wide installer, not because we wanted to use this process for all Teams updates, but simply to get us past this particular bug.

As has been mentioned before, uninstalling the machine wide installer (even if you then immediately reinstall it or the 365 apps/repair), it forces an uninstall on login for every user already logged in.

......Unmanageable!

0 Votes 0 ·

I think i have a sollution for updating the Machine wide installer if you use SCCM.

  • Let's say the first installer is called "Teams MWI March 2020" in SCCM, its the MSI installer of cause.

  • Now download the new one, let's call this one "Teams MWI April 2021" in SCCM (make the application in this step)

  • But at the detections method you delete what was put in there by default.

  • Instead make a detection method say file version of C:\Program Files (x86)\Teams Installer\Teams.exe is version 1.4.0.8872 (match this version with the teams.exe version that is installed), do this with the old ones as well.

  • In the supersedence tab select "Teams MWI March 2020" and make it uninstall.

  • Deploy it.

What happens if you deploy this:
- If another file version is detected it will uninstall the old Teams version
- The new Teams installer is installed after that.
- SCCM checks the file version after installation, now it's ok. Done.






0 Votes 0 ·
SharonZhao-MSFT avatar image
0 Votes"
SharonZhao-MSFT answered MarkF-9899 edited

@Franois-0770,

Updating Teams client with machine-wide installer is not supported now.

Once you have installed Teams on your computer, there are two ways to update the desktop client. One is to update itself automatically, another is to manually download updates by clicking Check for updates on the Profile drop-down menu on the top right of the top.

The MSI file is mainly used to broad deployment of Teams client.

For more information, please refer to this article.


If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

"One is to update itself automatically"

How doing it?
1. After updating the Machine wide installer, if the user restart Teams then it will be looping with a blanck screen and then never reach the interface.63969-and-then-teams-restart-after-blanck-screen-and-so.png


63970-blanck-screen-after-restart-after-new-machine-wide.png



Before that upgarde, we get an black line saying our installation is too old with 28 working days left

0 Votes 0 ·

@Franois-0770
Haven't received your update for a long time, any update now?
If the above suggestion helps, please be free to mark it as answer for helping more people.

1 Vote 1 ·

@Franois-0770,

Do you log in Teams daily?

Many factors could lead to a delay update, such as long time no sign into Teams client, network instability.

"One is to update itself automatically" How doing it?

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. So, you should log in Teams client frequently.

0 Votes 0 ·

@Franois-0770,
Do you have any further question on this topic?
If the suggestion helps, please be free to mark it as an answer for helping more people.

0 Votes 0 ·

See my reaction to Franois-0770, updating the machine wide installer is possible if you use SCCCM with the procedure i described.

And it is necessary, because eventually the version of the machine wide installer will be so old that a manual download is required imediatly after installation of this old version to be able to use Teams.

0 Votes 0 ·
BrianGe-5506 avatar image
0 Votes"
BrianGe-5506 answered

We are in a similar situation. We pushed out the Microsoft Teams Machine-wide installer to 1,500 PC's in our organization. The deployment was disappointing to begin with, in that all the installer does is create a Teams Installer directory under program files and then copies the installer (approx 100mb) to every single logged in user, which chews up the hard disk for multi user devices).
We've only just noticed now, that despite us pushing out version 1.3.003564 in the initial rollout, the end users were only receiving the updated Teams to their local profiles, so the initial installer is never updated due to being in a locked down environment.
We are now starting to get users who log into PC's for the first time and get prompted about not being a updated version and click here to update, which takes them to a download link for Teams. This will not install for all users as it requires elevated credentials which end users do not have.

Today I started working on a script to push out the new version only to find out that when we run:
"\\server\share\msteams\Teams_windows_x64.msi" ALLUSERS=1 /norestart OPTIONS="noAutoStart=true" (which was the initial script with /qn added for quiet mode) we get the error:
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use add/remove programs on the control panel.

That would be fantastic, except for the fact that Teams does not uninstall when doing this, nor does it uninstall when using the uninstall string from the registry with the /x option:
MsiExec.exe /I{731F6BAA-A986-45A4-8936-7C3AAAAA760B}.

I've also tried extracting the Teams.exe and setup.json files from the MSI and just dumping them in C:\Program Files\Teams Installer and my existing version does not update via this as it's searching online.

In writing this, I've just discovered that running the Teams.exe from the above directory has just kicked me out of Teams and performed the update on my profile installation. I guess I'll try and also push the update.exe file to all users and see if that works.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BatemanVern-3657 avatar image
0 Votes"
BatemanVern-3657 answered BatemanVern-3657 commented

@BrianGe-5506 I have the exact same issue as you, we have a wide range of versions when we first deployed the Machine installer, and are running into the issues where a new user signs in and the app wants a update.

I also tried the same thing as you - installing the latest version of the machine wide installer, and of course it failed with the message you got

The other day a new user signed in got the update message, so we let it download from the web, it installed, Teams launched but did not connect to their work account.

I'm going to try the idea of uninstalling the machine installer (with existing user Teams already installed), then re-install the latest version and see if it breaks anything.

Not sure how else to do this, I have to keep these installers up to date or I'm going to get a lot more of these issues with new users.

Anyone else??? - how do you handle this?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Glad I'm testing on my own machine - Don't uninstall the machine wide installer - it uninstalls all Teams on the machine (even my user install)

0 Votes 0 ·
BrianGe-5506 avatar image
0 Votes"
BrianGe-5506 answered

The trouble is, Teams is updated very often, so trying to keep the Machine Wide Installer up to date on all devices is a big challenge with a big administrative overhead.

Since running the updated Teams.exe on that test PC, a new login to that PC has resulted in an updated Teams. I'll be back to work on Tuesday, so will be doing more testing before writing up a script to redeploy.

Something like:
If exist c:\program files (x86)\Teams Installer\Teams.exe and version = 1.3.003564 then
copy Teams.exe and setup.json files from \\server (64 bit version)
If exist c:\program files\Teams Installer\Teams.exe and version = 1.3.003564 then
copy Teams.exe and setup.json files from \\server (32bit version)

It's still unclear if running Teams.exe manually once updates the application for all users of the PC, so that will need some testing. If it does, we can just add an extra line into the script after the files are copied to simply launch Teams.exe, if it doesn't we will have to also add to the User login script to update the files on their profile.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BrianGe-5506 avatar image
0 Votes"
BrianGe-5506 answered BrianGe-5506 commented

Here's a PS1 I've just whipped up, still needs some more testing on site, but so far it seems to be what I want. I've modified the script that we initially used to push Teams, so it'll also do the install on a new client along with an update if required:

$TeamsExist_64 = "C:\Program Files (x86)\Teams Installer\Teams.exe"
$TeamsExist_32 = "C:\Program Files\Teams Installer\Teams.exe"
$64Exists = Test-Path $TeamsExist_64
$32Exists = Test-Path $TeamsExist_32
If ($64Exists -eq $True) {
$64_Ver = (Get-Item "C:\program files (x86)\Teams Installer\Teams.exe").VersionInfo.FileVersion
If ($64_Ver -eq "1.3.00.3564")
{xcopy "\\server\share\msteams\Teams_x64.exe" "C:\Program Files (x86)\Teams Installer\Teams.exe" /Y}
}
If ($32Exists -eq $True) {
$32_Ver = (Get-Item "C:\program files\Teams Installer\Teams.exe").VersionInfo.FileVersion
If ($32_Ver -eq "1.3.00.3564")
{xcopy "\\server\share\msteams\Teams_x32.exe" "C:\Program Files\Teams Installer\Teams.exe" /Y}
}

If ($64Exists -eq $False -and $32Exists -eq $False) {
if ((gwmi win32_operatingsystem | select osarchitecture).osarchitecture -eq "64-bit")
{
#64-Bit install
Start-Process msiexec.exe -Wait -ArgumentList '/I \\server\share\msteams\Teams_windows_x64.msi ALLUSERS=1 /qn /norestart OPTIONS="noAutoStart=true"'
}
else
{
#32 bit Install
Start-Process msiexec.exe -Wait -ArgumentList '/I \\server\share\msteams\Teams_windows.msi ALLUSERS=1 /qn /norestart'
regedit /s "\\server\share\msteams\IMProviders.reg"
}
}

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BrianGe-5506 what you have posted is exactly what I've been experiencing. Is this PS1 working for you?

0 Votes 0 ·

The only addition I have is to run:
Start-Process -FilePath "C:\Program Files (x86)\Teams Installer\Teams.exe"
After the xcopy commands

It seems that after the new version is copied, you have to run the Teams.exe from Program Files directory once for it to update.

0 Votes 0 ·

what is the registry line doing at the bottom of the script? so far this is running without error but I didn't include the last registry line and teams is not updating...also changed the version of Teams that is checked to match what we are trying to update (which I can't imagine would prevent the update)

0 Votes 0 ·
Show more comments
BatemanVern-3657 avatar image
0 Votes"
BatemanVern-3657 answered BenjaminJohn-2954 commented

Here's what I ended up doing:

This is a batch file I run on the computers with a lower version (but is also based on the Uninstall string of the installer)

@echo off
set THISDIR=%~dp0
rem Forces the machine wide installer to re-cache itself using the new msi version. Caches to: (C:\Windows\Installer)
msiexec.exe /fv "Teams_windows_x64.msi" /qn
rem Forces the machine wide installer to re-install itself based on the new cached msi
msiexec.exe /f "Teams_windows_x64.msi" /qn

So in my case I created a collection in SCCM based on Teams installed with a version lower than 1.4.0.4167 and it needs to have the uninstall string of MsiExec.exe /I{731F6BAA-A986-45A4-8936-7C3AAAAA760B}

It does not affect users who have Teams already installed
It updates the Teams installer for any new user that logs in C:\Program Files (x86)\Teams Installer
It updates the existing version of Teams Machine Wide installer in Programs and Features

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@BatemanVern-3657

Sorry, can you explain what you are doing here?
I have Nessus complaining about teams.exe being vulnerable, which was installed on our master images.

<plugin_output>
Path : C:\Program Files (x86)\Teams Installer\
Installed version : 1.3.0.362
Fixed version : 1.3.0.13000
</plugin_output>

Are you copying the latest teams.msi to c:\windows\installer and running the above commands?
Have SCCM also.

Thanks

0 Votes 0 ·
BatemanVern-3657 avatar image
0 Votes"
BatemanVern-3657 answered SotkKamil-7170 edited

@BenjaminJohn-2954
I grab the latest Machine Wide installer v1.4.0.4167, then create a package and using a batch file to execute.

@echo off
set THISDIR=%~dp0
REM this command forces the machine wide installer to re-cache itself using the new msi from the sccm package. All installs of msi's reside here: (C:\Windows\Installer)
REM this command does not install anything,just updates the msi version in installer cache
REM the msiexec switches
REM /f (force) & v (Runs from source and re-caches the local package)

msiexec.exe /fv "Teams_windows_x64.msi" /qn

REM Forces the machine wide installer to re-install from the updated cache
msiexec.exe /f "Teams_windows_x64.msi" /qn

The machine wide installer has been updated to 1.4.0.4167 (use to be at 1.3.0.12058) & C:\Program Files (x86)\Teams Installer\Teams.exe is updated
This does nothing to any user that already is using Teams
The other thing I did is grab a report showing me all of the Machine Wide Installers and showing their unique GUID
...part1

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

..part2
I did not want to touch anything that did not match the GUID from the newest msi I was using, so in this case the latest v1.4.0.4167 has a GUID of [731F6BAA-A986-45A4-8936-7C3AAAAA760B}.
Just in case I end up with double installs of Teams Machine Wide Installer.

So I created a collection in SCCM based on Teams installed with a version lower than 1.4.0.4167 and it needs to have the uninstall string of MsiExec.exe /I{731F6BAA-A986-45A4-8936-7C3AAAAA760B}

Hope this helps, so far I have had no problems with this procedure, I will have to circle back and fix the other versions that have different GUID's, but that might be difficult as I'm thinking I would have to uninstall it - which would then uninstall Teams for the user as well.

0 Votes 0 ·

I was wondering the same as @BenjaminJohn-2954 :

So you create a package with the latest TMWI - okay. Are you copying that package to the Windows\Installer directory are you saying? I can create a package with the new TMWI but not sure how the batch file you have here executes it? I see much of the logic of this batch file just not sure how it all comes together in a package.

0 Votes 0 ·

No I dont copy it, I let the msiexec force it into the cache directory

msiexec.exe /fv "Teams_windows_x64.msi" /qn

Then I force Teams to re-install itself based on the updated msi in the cache

msiexec.exe /f "Teams_windows_x64.msi" /qn

0 Votes 0 ·
Show more comments
PaulSanders-5222 avatar image
0 Votes"
PaulSanders-5222 answered ElemerGazda-4665 commented

The solution for me at least was to update my O365 deployment repository.
Only my new deployments on 20H2 were having unwanted teams update appear
and all manner of messing with the teams machine wide installer just went down a
deep rabbit hole. The only other tweak I had to make was to add a reg hack to
stop the AAD nag to the user.

Given teams is now included within O365 and the teams machine wide installer appears to be unsupported
on later Win10 builds, I think this is probably your best way out.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@PaulSanders-5222
Could you please elaborate on how exactly you did this?

0 Votes 0 ·