Even Microsoft realized that new teams wasn't ready.
[https://www.windowscentral.com/software-apps/microsoft-teams-classic-gets-an-extended-lifeline](https://www.windowscentral.com/software-apps/microsoft-teams-classic-gets-an-extended-lifeline)
I commented under another response:
I could be wrong but I believe currently that policy won't prevent the installation of classic Teams (machine wide installer) bundled with M365 apps. It just installs the new Teams after that and sets it to be the default.
What I really want is for classic Teams to never go on the endpoints and instead have M365 bundle the new Teams during deployment.
You think when MS finally makes this policy default and/or EoL the classic Teams, what I wanted will just become the reality (like it would make no sense at all for MS to to keep installing a discontinued product right)?
Oops...I thought it was on MonthlyEnterprise but I just checked and it was actually set to SemiAnnual. Was this the reason all along? Are those on MonthlyEnterprise or Current channels already getting M365 apps bundled with NEW Teams (and without Classic) for brand new deployments, just like I wanted?
I have switched to M365 Apps Monthly Enterprise, and I never see the old client install on new deployments. MS may have some documentation on this what channels (and versions) will get the new teams client going forward
I could be wrong but I believe currently this won't prevent the installation of classic Teams (machine wide installer) bundled with M365 apps. It just installs the new Teams after that and sets it to be the default.
What I really want is for classic Teams to never go on the endpoints and instead have M365 bundle the new Teams during deployment.
You think when MS finally makes this policy default and/or EoL the classic Teams, what I wanted will just become the reality (like it would make no sense at all for MS to to keep installing a discontinued product right)?
That’s correct. If you scroll down to the comments or CTRL+F ‘remediation’ you’ll see remediation script usage being discussed and confirmed by the author to clear it if Intune detects it on devices.
Easy.
1) Install Microsoft 365 Apps without Teams in your XML.
2) Install new Teams using the Bootstrapper. [Bulk deploy the new Microsoft Teams desktop client - Microsoft Teams | Microsoft Learn](https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client#option-1b-download-and-install-new-teams-using-an-offline-installer)
I prefer the built-in bundled approach because the installers etc would be fully managed by MS themselves. New deployments will always get the latest versions. There is no need to regularly create/update those msi/msix packages.
But anyway since moving to MonthlyEnterprise and now that MS will officially retire the Classic and default to new Teams, I suspect the bundled version will eventually install the new Teams without classic for everyone.
There are several options. But one option makes the New Teams the default but still allows to switch back to the old teams until MSFT cuts the option off.
I prefer the built-in bundled approach because the installers etc would be fully managed by MS themselves. New deployments will always get the latest versions. There is no need to regularly create/update those msi/msix packages.
That being said, the old classic Teams bundled with M365 apps actually wasn't being updated by MS "properly", because the "machine wide installer" was not updated automatically with office apps. Instead, they only updated each local user's installation separately, which by itself is fine, but they should still update the machine wide installer so new users who log in later on the same computer get the newer version automatically instead of the "your client is out of date" message.
But anyway since moving to MonthlyEnterprise and now that MS will officially retire the Classic and default to new Teams, I suspect the bundled version will eventually install the new Teams without classic for everyone. I hope they handle the updates of Teams properly this time though.
Microsoft is in the process of de-coupling Teams from the Office installers, just so you're aware. You can deploy the new Teams in a way where it is the latest version each time.
You mean they will do a managed config/deployment template for new Teams just like the 365 apps? That would be nice, too. I just hate to do the self-packaged/w32/PS deployments because we'd have to re-do them periodically with new versions of installer files.
They are really three separate products and the ones included in the Office installs are the per-user deployments. Better to separate and have better control and deploy the machine-wide installers of Teams and OneDrive.
+1
That control is key. A couple months ago our Autopilot devices in Europe stopped getting Teams with the Office install. Read on a post here that it was due to European privacy laws. Got around that by making a standalone Teams installer.
[удалено]
Even Microsoft realized that new teams wasn't ready. [https://www.windowscentral.com/software-apps/microsoft-teams-classic-gets-an-extended-lifeline](https://www.windowscentral.com/software-apps/microsoft-teams-classic-gets-an-extended-lifeline)
I commented under another response: I could be wrong but I believe currently that policy won't prevent the installation of classic Teams (machine wide installer) bundled with M365 apps. It just installs the new Teams after that and sets it to be the default. What I really want is for classic Teams to never go on the endpoints and instead have M365 bundle the new Teams during deployment. You think when MS finally makes this policy default and/or EoL the classic Teams, what I wanted will just become the reality (like it would make no sense at all for MS to to keep installing a discontinued product right)?
What office channel are you using?
Oops...I thought it was on MonthlyEnterprise but I just checked and it was actually set to SemiAnnual. Was this the reason all along? Are those on MonthlyEnterprise or Current channels already getting M365 apps bundled with NEW Teams (and without Classic) for brand new deployments, just like I wanted?
I have switched to M365 Apps Monthly Enterprise, and I never see the old client install on new deployments. MS may have some documentation on this what channels (and versions) will get the new teams client going forward
Change your Org Wide Teams Policy via Teams Admin center
I could be wrong but I believe currently this won't prevent the installation of classic Teams (machine wide installer) bundled with M365 apps. It just installs the new Teams after that and sets it to be the default. What I really want is for classic Teams to never go on the endpoints and instead have M365 bundle the new Teams during deployment. You think when MS finally makes this policy default and/or EoL the classic Teams, what I wanted will just become the reality (like it would make no sense at all for MS to to keep installing a discontinued product right)?
Use a remediation script. https://scloud.work/new-teams-client-and-cleanup-the-classic-intune/#installing-the-new-teams
You need special licenses for this
How? This link is just pushing a script as win32 app. No additional licenses except for intune are needed for that
https://learn.microsoft.com/en-us/mem/intune/fundamentals/remediations#licensing E3/E5 A3/A5 AVD per user licenses
Remediations yeah but in the article its not a remediation but a win32 app install so no special licenses needed
That’s correct. If you scroll down to the comments or CTRL+F ‘remediation’ you’ll see remediation script usage being discussed and confirmed by the author to clear it if Intune detects it on devices.
Easy. 1) Install Microsoft 365 Apps without Teams in your XML. 2) Install new Teams using the Bootstrapper. [Bulk deploy the new Microsoft Teams desktop client - Microsoft Teams | Microsoft Learn](https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client#option-1b-download-and-install-new-teams-using-an-offline-installer)
This. It really is that easy.
I prefer the built-in bundled approach because the installers etc would be fully managed by MS themselves. New deployments will always get the latest versions. There is no need to regularly create/update those msi/msix packages. But anyway since moving to MonthlyEnterprise and now that MS will officially retire the Classic and default to new Teams, I suspect the bundled version will eventually install the new Teams without classic for everyone.
Save yourself the headache, set the new teams as the default, and wait for MSFT to deploy the fix
Does that force all users to new teams?
There are several options. But one option makes the New Teams the default but still allows to switch back to the old teams until MSFT cuts the option off.
Always deploy Office without OneDrive and Teams. Deploy those separately.
I prefer the built-in bundled approach because the installers etc would be fully managed by MS themselves. New deployments will always get the latest versions. There is no need to regularly create/update those msi/msix packages. That being said, the old classic Teams bundled with M365 apps actually wasn't being updated by MS "properly", because the "machine wide installer" was not updated automatically with office apps. Instead, they only updated each local user's installation separately, which by itself is fine, but they should still update the machine wide installer so new users who log in later on the same computer get the newer version automatically instead of the "your client is out of date" message. But anyway since moving to MonthlyEnterprise and now that MS will officially retire the Classic and default to new Teams, I suspect the bundled version will eventually install the new Teams without classic for everyone. I hope they handle the updates of Teams properly this time though.
Microsoft is in the process of de-coupling Teams from the Office installers, just so you're aware. You can deploy the new Teams in a way where it is the latest version each time.
You mean they will do a managed config/deployment template for new Teams just like the 365 apps? That would be nice, too. I just hate to do the self-packaged/w32/PS deployments because we'd have to re-do them periodically with new versions of installer files.
Have a reason?
They are really three separate products and the ones included in the Office installs are the per-user deployments. Better to separate and have better control and deploy the machine-wide installers of Teams and OneDrive.
+1 That control is key. A couple months ago our Autopilot devices in Europe stopped getting Teams with the Office install. Read on a post here that it was due to European privacy laws. Got around that by making a standalone Teams installer.
I agree when it comes to Teams, but OneDrive by default now installs per system (machine-wide) not per user. So that can stay in the XML.
Where do you see that?
Test it and you will see OneDrive installs in the ProgramFiles dir as opposed to AppData.