$NewFileContent | Set-Content -Path "$ENV:APPDATA\Microsoft\Teams\desktop-config.json" $NewFileContent=$JSONObject | ConvertTo-Json $JSONObject.appPreferenceSettings.$RunningOnClose=$RunningOnClose # Convert file content from JSON format to PowerShell object $FileContent=Get-Content -Path "$ENV:APPDATA\Microsoft\Teams\desktop-config.json" # Close Teams App fully instead of running on Taskbar $true or $false
# Teams open automatically at user login $true or $false # Teams open in the background Hidden $true or $false Here it was written as a Parameterized Script param( EnergizedTech looked at me funny when it happened ? ) I launched the Teams process and examined the settings which confirmed it was updated properly! I actually did a little dance on that one when I saw it work. $NewFileContent | Set-Content -path “$ENV:APPDATA\Microsoft\Teams\desktop-config.json” $NewFileContent=$JSONObject | Convertto-JSON
$ENV:APPDATA\Microsoft\Teams\desktop-config.json It was located under the following folder With a little bit of work I found a file which seemed to be written to when I checked and cleared the respective boxes. In addition there are books written by Mark Russinovich and Aaron Margosis to show you all the ins and outs of this great suite of tools.
#MS ACCESS RUNTIME CONFIG FILE SET UPDATE SETTINGS HOW TO#
If you are curious on how to use this tool there is an excellent link from Christopher Haun on MSDN as well as a cool video from Scott Hanselman. To find that answer I pulled out the ever trustworthy tool from Sysinternals called “Procmon” which allows you to see what files and registry entries a process is accessing. The first question which needed to be answered was “Where are the settings stored?” Since I couldn’t find a way online to do it so I decided to investigate. In addition, if so desired you could edit the XML file for Office Click to run to exclude the installation of Teams if so desired.īut if Teams was deployed and initially an Office wanted to delay use (*after say, until staff were trained*) it would still launch at login in some cases. There was a Policy that could be found here to prevent the initial startup that could be found here. I saw the settings in questions but there didn’t appear to be a Group Policy which managed them. They can be accessed under the “Settings” in Teams
Let’s begin by examining the settings we are trying to change. For which it produced a most interesting solution when I asked Sean Kearney one of our Microsoft PFE’s to look at it. Could you lend me a hand?Ī very excellent question. I can change it in the Interface, but I need to be able to edit across multiple systems. I need to be able to change the Startup settings in Teams (like the Auto launch feature). Summary: Using the ConvertFrom-JSON and ConvertTo-JSON Cmdlets to edit a configuration file