PC installation. The Teams MSI places an installer in %SystemDrive%\Program Files\Teams Installer on bit Windows and %SystemDrive%\Program. 4. To start the installation, follow the three-step instruction from the browser. Click Run (1) to execute the installer. Click.
 
 

Teams machine wide installer command line

Attachments: Up to 10 attachments including images can be used with a maximum of 3. Hi JamesEdmonds ,. Yes, I saw this but there is a caveat to our use case; We only want to apply this for two particular machines remote app hosts. As it’s a per user setting, we would need to enable group policy loopback for this particular OU, which should be fine but I wanted to keep the group policy side of things simple. Therefore, if we can set it at install time using a transform and assigned software group policy, we can target it at the machines in a slightly simpler way.

For now I have just run the command line manually, but I know we have to keep the MWI up to date so it may be something we repeatedly have to consider during udpdates. Thanks James for the clarification. But from what I am aware of, I am afraid I cannot think of a way to realize this. If it honours it, then I guess we just do a manual install with these options set initially, then just use group policy assigned software to deploy new versions over time.

But it’s worth giving it a go and see how it goes. So, I had deployed MSI 1. I then downloaded the more recent 1. After I updated policies and restarted, the newer MSI was installed, but it seemed to honour the no auto start option. I logged in with an existing user that had Teams deployed from the MSI and it did not auto start. I then logged in as a new user, Teams was deployed no desktop shortcut oddly and it also did not start.

Clunky, but then Teams has always been clunky. How are you managing files in your Teams? Skip to main content. Find threads, tags, and users Thanks James. Current Visibility: Visible to all users. Many thanks. Cheers James. Related Questions.