Oct 05 2023 01:07 AM
Oct 05 2023 01:07 AM
I try to install the Teams Wide Machine Installer (MSI file) with the option ProductLanguage="1036" for the French language but I have the error below :
If I remove the argument ProductLanguage, the installation works correctly but Teams is in English by default for each users.
Here is my command-line used :
msiexec /i "%~dp0Teams_windows_x64.msi" ProductLanguage="1036" OPTIONS="noAutoStart=true" /qn /norestart ALLUSERS="1"
Did you already encounter this issue ?
Thank you !
Oct 05 2023 04:32 AM
To install Teams Wide Machine Installer with the ProductLanguage option perhaps you can try to change the config.xml file:
<?xml version="1.0" encoding="utf-8"?> <Configuration> <ProductLanguage>1036</ProductLanguage> </Configuration>
msiexec /i Teams_windows_x64.msi /qb TARGETDIR="%SystemDrive%\Program Files\Microsoft Teams" ALLUSERS="1" CONFIG="config.xml"
This should install Teams Wide Machine Installer with the French language (ProductLanguage="1036").
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.
If the post was useful in other ways, please consider giving it Like.
Oct 05 2023 08:11 AM
Thanks for your answer.
Unfortunately, this doesn't work. How your command can run the MSI file if the command prompt is in the temporary folder with the config.xml file ?
But anyway I tried to install it with the MSI and EXE file and it doesn't work.
MSI installation seem to not execute the option CONFIG="config.xml"
Also, the option for the targetdirection is not supported for this MSI file.
Maybe the ProductLanguage argument is not supported for Teams ?
Thank you for your help
Oct 05 2023 03:36 PM
Oct 06 2023 12:02 AM
Oct 06 2023 06:44 AM
Hi, IBM and I have been working on this. This depends on if you are using the Microsoft Teams Classic which orphans' inactive users that remain vulnerable to data breaches in the c:\users\xxxxx\appdata folders. Orphaned users folders can be compromised if bad actors gain access and begin to move laterally as we know. Thus we have developed scripts to remove all teams once per month from the c:\users\xxxxx\appdata folders and then update the Teams Machine Wide Installer once per month with SCCM, Intune or group policy so that only active users get the current version.
The big unanswered question we are vetting in our sandbox at this time is with the New Teams MSIX package that installs the New Microsoft Teams Meeting Add-In for Microsoft Office that installs as a c:\Program Files app. Our groups in IBM and BFB Security promote zero trust and we are evaluating the cadence of the New Teams and how it operates in smaller SMBs without SCCM or Intune.
Oct 06 2023 07:26 AM