![]() |
MS/365/Teams experts
We have about 400 physical machines to update Teams to the new teams. This was a sudden project thrust on us and these machines are not in InTune, but it looks like we can use Control Up to install if we can figure that part out and they are all on our domain.
My question was, can we force Teams Classic to use the toggle asking if we want New Teams. Either using a Group Policy or script? Something like psexec is out due to the security policies breaking it. Powershell should work but I am not well versed in PS. I know the Admin center in Teams can push it out to all, but we are looking to just update the physical machines, not the virtual pools. Any help or pointers would be appreciated. (I am more a VM/Networks/EXC_Prem guy, just trying to help the team on this one) |
Im on Linux and wfh so Teams etc is always via browser for me ... but I did notice the choice toggle on my work desktop, from what cowerkers have said the old/new toggle was an early opt-in and then it got auto updated. Dont think the update was triggered on our end
Good luck! |
We use SCCM to push out the teams client via a powershell script. Once a new enough client is on the workstation you can control the toggle via the Teams admin center.
https://learn.microsoft.com/en-us/microsoftteams/new-teams-deploy-using-policies?tabs=teams-admin-center FYI most of our users are not local administrators of their workstation, and if they tried to move the toggle themselves it would fail. I'm not a Teams admin or SCCM admin either, but I can sort of fumble through it. |
Thanks for the info. I think the PS script is what we will do based on that.
What can go wrong, right? |
All times are GMT -8. The time now is 07:44 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
Search Engine Optimization by vBSEO 3.6.0
Copyright 2025 Pelican Parts, LLC - Posts may be archived for display on the Pelican Parts Website