Can we have a Teams GPO ADMX file so we can turn on/off user client items like "Auto-Start Application", "Open Application in Background"...
Can we have a Teams GPO ADMX file so we can turn on/off user client items like "Auto-Start Application", "Open Application in Background"?
We need to be able to disable hardware acceleration and do this through a policy rather than powershell to edit the json. Powershell is blocked running under the standard user context in our environment which causes more headache getting powershell to run and make the required changes. Why in 2020 would anyone manage an application in this way?
Would also appreciate Teams GPO-Management. Especially in terminalserver environments options like "Animations" should be set by the administrator. Thank you, Aknur, for the workaround, scripting the JSON changes via PS.
Agreed!! The default setting is extremely annoying. As an admin I'd prefer to set it to just open in the background so users don't quit inadvertently out of it.
Need better GPO management than what is currently offered on Teams. Not sure why this hasn't been improved on yet.
After 30+ years supporting Microsoft environments, our forced migration is being aided not by superior product line (like Zoom), but rather by Microsoft's inability to recognize the importance of their own MS-Teams as THE product line of the future. Please re-prioritize simple tasks in support efforts for MS Teams!
It is amazing that Zoom actually has better GPO controls available than Teams does. Please fix this issue. At a minimum, we need a way to disable autostart that works even if Teams is already installed on the computer. The existing GPO that must be set before the app is installed is not a good solution.
And the ability to manage items (like most enterprise software can)
e.g. Set the language, disable GPU, restrict access to mobile app + check for updates, opt out of MS surveys, disable webcam, restrict apps access - just common superfluous user settings
If you could create a template settings.json/desktop-config.json file to be inherited by new users - that would be a bonus
Guess this is on the to do list, like fixing the dominate my CPU , use loads of memory, and bloat my profile features
am writing this from a Citrix/RDS (multi-user) POV - however same could easily be applied to desktop/laptop
Not configuring "Open Application in Background" within an Administrative Template (ADMX) is a huge oversight on Microsoft's part for a corporate environment. Please review this 'Microsoft Teams' development team.
Also same setting to Intune please.
Just for general Information (took me a bunch of my time):
Teams got its Settings inside a File named "desktop-config.json" in %appdata%\Microsoft\Teams
There are a couple of Guides to get you a Powershell-Script to work, which you can hang into a gpo starting on userlogin.
Hope this will help many, who searched like me for that.
i recommend you to the following Sites for a more indepth Guide:
This is hilarious. Why is Teams even starting by DEFAULT. No wonder Microsoft was touting millions of users they forced all of them to install on every profile that logs into the machine AND forced the application to start on Windows boot. Its bad enough the application performs poorly but then you straight up force users to have to deal with this application behavior. At least give IT admins the ability to stop this with Intune configuration policies when GPOs aren't an option...
Ido Yavin commented
I have tried using the AMX based policy only to find out that (as mentioned in the previous comments) it only applies I cases where the policy has been applied BEFORE Teams is installed. That makes this policy irrelevant in our setup where we install office 365 from MDT. Teams installs automatically if you install o365 using the deployment tool. Installing Teams from Intune is problematic as well because there is no way to configure what is getting applied first… Besides, most of our clients already have Teams installed on their PC’s. We need a policy that IS getting applied to ALL devices whatever Teams is installed our not. It will be better if we get an option to allow Teams to run with Windows start - but it in the background.
ADMX backed CSP’s are great. I think that this is a way to go if you are using Intune. For Teams as well as for Office365 products. The thing is that this is great if the policy has effect. Otherwise it is not usable…
The ADMX documentation says the new ADMX's only work for new installs. We need this to work for any install including existing ones.
Office 365 Pro Plus GPOs, found here: https://www.microsoft.com/en-us/download/details.aspx?id=49030
These include the GPO for Microsoft Teams. Once the templates are in place,
User Config > Policies > Admin Templates > Microsoft Teams > "Prevent MS Teams from starting automatically after installation"
I just put this in my environment and it has remedied the issue.
***The date on the templates say Sept 25, 2019***
can the Teams Channel notification be turn on by default? Or is there any gpo for the notification setting?
In 8 more months, Microsoft will shrug and say they can't really be sure WHY news reports are that users are moving away from Teams, and to Slack or Zoom in droves... between this, and requiring 3rd party invitees to configure MFA just to join a meeting, they really missed the mark with how people are USING the tools. A lot like the Apple theory of "Here's the product, you WILL use it our way, or not at all."
CD Evans commented
Any update on this, it's a requirement for software these days.
Ben Weeks commented
I'd LOVE to be able to configure MS Teams VIA GPO, that contain settings such as controlling auto-start, credentials, etc. This would make delivering a CONSISTENT user experience much easier on a large scale deployment.
To save time for anyone looking, the new ADMX *do not* contain any new settings for controlling auto-start or open in background. The only Teams-related item in there is whether or not it gets installed with the rest of the suite. We're still waiting, Microsoft... this thing is NOT business-ready, and removing SFB before it IS ready will be a mistake!
To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.