Feb 14 2024 07:41 AM
Hello,
I'm encountering an issue where some users have the wrong language setting under the "Appearance and Accessibility" section in the new Teams (work or school) interface. Our company is based in the UK, so the correct setting should be English (United Kingdom), but currently, it's set to English (United States).
This discrepancy is causing problems with the spell check feature, as it provides incorrect corrections for UK spellings.
Previously, with "Classic" Teams, we addressed this issue using a PowerShell script to automatically adjust the language settings on user machines by modifying certain files within the Teams application directory. The script worked by iterating through user profiles on a machine, excluding system and default profiles, and replacing "en-US" with "en-GB" in specific configuration files related to Teams.
However, with the introduction of the new Teams and changes in file storage locations, this script no longer functions as intended.
I've identified what appears to be the relevant JSON files in the new Teams directory that should control language settings:
%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\app_settings.json
%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\ecs_request_param.json
Editing these files seemed promising because changing the language within the Teams app updates these files accordingly. However, after manually adjusting these files to "en-GB" and restarting Teams, the application still displays the language setting as English (United States), even though the JSON file retains the "en-GB" modification.
Given this situation, I'm seeking a script-based solution that can adjust the language settings for my end users without requiring their interaction. With over 2000 affected users out of approximately 10000, manually adjusting settings individually is impractical.
Is there an alternative location or method to script these changes effectively for the new Teams application?
Thank you
Feb 26 2024 03:32 AM
Jul 08 2024 11:35 PM - edited Jul 08 2024 11:37 PM
I'd also like a solution to this.
The old "classic" teams client may have referenced desktop-config.json but this doesn't seem to apply any more. So scripts like this will probably not work:
https://purple.telstra.com/blog/automate-microsoft-teams-desktop-settings-with-powershell
app_setttings.json is modified when changing the language but any changes directly to the .json are overwritten by the previous setting (that were last applied manually via the Team Client UI) are re-applied at next launch.
This setting must be stored elsewhere.
Path is: %AppData%\local\packages\localCache\Microsoft\MSTeams\app_settings.json for me.