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"?
Not having these admin templates in Intunes is limiting staff usage of their Teams. For example, we'd like to set everyone's activities to "on" for all alerts. Staff belong to numerous Teams and are forgetting that they have notifications out there.
Teams is now the go to application by everyone in my community, it would be useful to control some of the desktop application functions.
Completely agree with Aaron and Steve, We need a GPO to set many settings accross our school specifically New Experience as its too difficult to ask all users to do this plus we use mandatory volatile profiles so the setting resets after logoff anyway. No roaming profiles here......
Does anyone know if anything has changed in regards to the admx files?
Massively struggling without them.
Steve Jaworski commented
Exactly what Aaron said below. We have hundreds of users and some have "new Experience" on and some have it off. So we have to manually explain to people how to set it or remote in to fix it. There NEEDS to be a way to manage this firm wide.
This... plus, auto-start, default Chat app for Office. There needs to be a centralized management for this.
Aaron Rummery commented
New experience feature now available some have it enabled automatically some don't would be nice to include teams admx files with office 365 to set the option
Completely agree to this. Having this limited options für managing an Application by Microsoft is just irritating.
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.