Jakub Płuska

My feedback

  1. 501 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    54 comments  ·  Public » Settings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jakub Płuska commented  · 

    So far no problems encountered. The logon script works perfect.

    I think it's better to substitute a fragment of text string than letting Powershell convert the JSON file to object and then back to JSON. Powershell seems to create the JSON in a pretty way with spaces, line feeds etc. But Teams expects an ugly single-line JSON. I read somewhere that this can cause some issues. Anyway my command works for me and maybe somebody else will find it useful as well.

    An error occurred while saving the comment
    Jakub Płuska commented  · 

    I didn't test that long script from Alkane but I wrote a simple one-liner to modify that JSON file. I included it in our logon scripts. Fingers crossed!

    (Get-Content $ENV:APPDATA\Microsoft\Teams\desktop-config.json).replace('"openAsHidden":false', '"openAsHidden":true') | Set-Content $ENV:APPDATA\Microsoft\Teams\desktop-config.json

    An error occurred while saving the comment
    Jakub Płuska commented  · 

    The script from Alkane Solutions looks very promising. Did anyone test it? Are there any things to consider when using this script? Potential problems etc?

    Jakub Płuska supported this idea  · 

Feedback and Knowledge Base