Teams Wide Machine Installer - "ProductLanguage" option

[BaptisteGauthier]

Hello,

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 !

[#2]

Hi @BaptisteGauthier,

To install Teams Wide Machine Installer with the ProductLanguage option perhaps you can try to change the config.xml file:

1. Download the Teams Wide Machine Installer (MSI file) from the Microsoft website.
2. Extract the MSI file to a temporary folder.
3. Open the temporary folder and create a new file called config.xml.
4. Open the config.xml file in a text editor and add the following code:

<?xml version="1.0" encoding="utf-8"?>
<Configuration>
  <ProductLanguage>1036</ProductLanguage>
</Configuration>

1. Save the config.xml file.
2. Open a command prompt and navigate to the temporary folder.
3. Run the following command:

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.

Kindest regards,

Leon Pavesic
(LinkedIn)

[#3]

Hi @LeonPavesic,

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

[#4]

What is the update cadence and patch. Will there be an autoupdate feature or GPO for update policy. Intune while great and promoted by our organization may not be for all SMBs and there needs to be a method to auto update the client

[#5]

Hi Bruce,

My goal is to install Teams Wide Machine in French during the computer deployment with SCCM.
Once Teams is installed in the user profile, no issue with the update.

[#6]

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. 

[#7]

Sorry but I don't see the rapport between your answer and my problem.
I just want to try to change the default language for Teams during his deployment.
Office365 support tel me to try the argument ProductLanguage in my command line but seem doesn't work.
Maybe Teams MSI file doesn't support it.
Our OS is in English so Teams configure itself in English by default but we have many French users.