Deploying Teams via Group Policy using the MSI Packageīefore you deploy the Teams client you should verify that Teams in your Office 365 tenant is configured the way you want it.Deploying Teams via Script or Group Policy using the Setup.exe Package.If you block Teams from self-updating, Microsoft warns that your Teams experience will likely degrade and you’ll miss out on new features and performance improvements that are released.
That makes it simple to maintain (as long as you allow it to self-update), and means that deploying Teams is basically a task of running the installer once, and then not running it again. It will check for, and download, any available updates each time the user runs the program. As you’ll see in the comments on this blog post below, this isn’t ideal for some environments for a variety of reasons. Whichever method you use to deploy Teams, the installer runs in the context of the logged on user, and installs to the %userprofile%\AppData\Local\Microsoft\Teams folder. This package is suitable for GPO and SCCM deployment, but works a little differently than the setup.exe package, as you’ll see in the demonstration below. An MSI package for Windows is also available in x86 and 圆4 versions.You can script the install and use GPO to deploy the package, which I’ll demonstrate later in this article. The Windows setup.exe package has basic command-line switches for silent install and uninstall. The Mac installer and the Windows setup.exe installer are available from Microsoft here.The Microsoft Teams desktop client installer is available for Windows, Mac, and mobile devices. Microsoft Teams is now generally available for Office 365 customers, and for those of you who are planning to use it you may be looking for a way to deploy the Teams client to your user’s computers.
0 kommentar(er)
