Upgrading Teams Machine wide installer

Question

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

Answer 1

I usually uninstall the old one with wmic:

:: https://www.reddit.com/r/sysadmin/comments/hzektt/teams_for_all_users_with_one_install_solved/
:: machine wide install, ends up being 32-bit

:: bail if running
tasklist | find /i "Teams.exe"
if %errorlevel%==0 exit 99

:: machine wide install workaround
reg add HKLM\SOFTWARE\Citrix\PortICA /f

:: can't upgrade, error 1638
:: avoid nuget prompt with -provider
:: powershell uninstall-package 'Teams Machine-Wide Installer' -ea 0 -provider msi
wmic product where name="Teams Machine-Wide Installer" call uninstall

:: not having ALLUSERS=1 is a disaster
start /wait msiexec /i Teams_windows_x64.1.6.0.27573.msi /qn ALLUSER=1 ALLUSERS=1

set err=%errorlevel%  

del "c:\users\public\desktop\Microsoft Teams.lnk"

reg delete hklm\software\wow6432node\microsoft\windows\currentversion\run /f /v teams  

exit /b %err%

Answer 2

More typical M$ garbage. Release an application, offer sysadmins next to no real-world solutions to govern it.

Again M$, get bent.

Answer 3

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.

Answer 4

@Benjamin John
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

Answer 5

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