Mike B

My feedback

  1. 502 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
    Mike B commented  · 

    This one hurt.. but I scripted a solution. Had to throw out using Microsoft's solution of the machine wide installer and go with a per user solution with no help from Microsoft and their default settings for this install. They set this install pretty ugly. Maximized screen,, always showing the windows on boot up.. at not even getting alerts when you get messages. PowerShell to the rescue.. I'll admit now, it may not be pretty... but it made a bunch of people happy for our rollout. Since Teams builds the config file as it is installing, and adds more to it after opening for the first time, you have to edit that config file in stages, or at least that is what I found to work. Attached are the two PowerShell scripts I used for my SCCM application. Used a HKCU registry setting for my detection method. Or you can just use a package if you'd rather.

Feedback and Knowledge Base