/build/static/layout/Breadcrumb_cap_w.png

KACE K1000 and Microsoft TEAMS

Hello 


Trying to push out a registry change via KACE using Scripting > Configuration Policies > Registry


MIcrosoft TEAMS program is already installed on user's workstation. We had users manaully set them to disable to auto-start. 


How do I change it to do the reverse where it will auto-start? 


Again we're using Kace K1000 and would like to push out a registry change on Windows 10 machines.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: TheITNooB 2 weeks ago
Yellow Belt
0

I dont think that this can be achieved via registry, however you should be able to get this done with PowerShell. I have a PS/Kace script that runs to DISABLE the auto startup. you should be able to reverse it and set it to auto start. Then run the script as you like

Teams stores the settings for each user in a .JSON file in the user appdata folder: C:\users\<user>\Microsoft\Teams\desktop-config.json


if you change this line from false to true then it will set auto startup to enabled 

$configarray.appPreferenceSettings.openAtLogin = ‘true’


This PowerShell script will DISABLE the auto startup on the currently logged in user.

$path = “$env:appdata\Microsoft\Teams\desktop-config.json”
$configarray = Get-Content $path | ConvertFrom-Json
$configarray.appPreferenceSettings.openAtLogin = ‘false’
Set-Content $path ($configarray | ConvertTo-Json)
Write-Host "User Appdata:" $path
Write-Host "Desktop-Config Contents:" $configarray.appPreferenceSettings

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ