Patch My PC Feature and Application Request
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
Microsoft is rolling out a new Teams client engine and renaming the existing one as Teams Classic. There are 'bulk' rollout methods, but would be great to have this in PMPC. Please see reference linked from this video:
https://www.youtube.com/watch?v=YcYWqCMQ1no
Recommend the new Teams client simply be Microsoft Teams (as that is what it will be going forward) and the old one be renamed to Teams Classic Machine-wide Installer in order to differentiate them and use Microsoft's terminalogy to reference them.
| Which Product is this Request for (New Application Request Only) | Patch My PC |
Hope to get this out ASAP as well :)
Any update on this?
Unfortunately, I do not have an update at this time. We are hoping to ship this sometime early in Q1.
Has there been any updates on this?
Only been a year... Darn junior Techs keep bugging me for ETA..... Looked at spinning own solution, but don't want to maintain... Please get on this
Andrew, thank you for providing this update. I have nothing but confidence in the PMPC team. The fact that this feature is taking longer than expected simply proves you guys are more concerned with getting it right the first time rather than releasing a feature that is not fully tested. Thanks again!!!
We are hopeful to have this available in Q4 but it may slip into early Q1. We'll work on getting the existing Teams renamed to Teams Classic next week (week of 9/23/2024). As Jason mentioned, we are working on a complete rebuild of our catalog backend to support MSIX apps, as well as ARM architecture, multi-file support, and more. We are well aware of the frustration when it comes to MSIX support and are working quickly to provide this feature and many other improvements to our catalog.
Do you have a timeline with an ETA on when support for MSIX would be added? Do you think it will be done this year?
We completely understand the frustration here and want to assure you that we are working as quickly as we can to add support for the New Teams app. The teamsbootstrapper.exe installer provided still installs as a Windows App and doesn't show up in ARP so our current detection scripts won't work. We appreciate the scripts some have offered, however we are currently limited to the Patch My PC framework on which the Publisher was built and that means refactoring code on our end to add support for additional installer types such as MSIX along with different detection methods.
Really would like this. I have a script using the teamsbootstrapper.exe and patchmypc could just use that for now and a more standard install later so they don't have to reinvent the wheel just for this app.
Can Patch My PC speak to why they wouldn't have started using the teamsbootstrapper.exe file mentioned at https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client#option-1a-download-and-install-new-teams-for-a-single-computer? We've just begun testing Azure Virtual Desktop, but the current Teams install from Patch My PC installs Classic Teams, and as soon as a user launches Teams, they get prompted to upgrade to New Teams. We're trying to improve the end user experience and want to have New Teams installed by default. Is there a way to do this w/ the Patch My PC install, which appears to be using an MSI for the initial install, or do we need to at least temporarily switch installer methods to something other than Patch My PC? Thank you.
At the very least could it be renamed to Classic Teams for the timebeing, I am on a trial at the moment and it caused me some confusion, easy to identify by the version number but I think it's a simple thing to resolve.
The new Teams is MSIX-based and we do not currently support that installer type. In addition to adding support functionality for MSIX as a file type, our detection scripts will need to be tweaked as MSIX installers do not create entries in Add/Remove Programs like a standard EXE or MSI installer. The new Teams is definitely on our roadmap, but there is currently no timeline available on when this will be completed. Thank you for your patience while we work through this on the backend.
Please keep me updated when the new Teams will roll out, the old version expires at the end of the month.
Would like to get the New Teams packaged and published. Please let me know when this would be ready.
Thanks!
any word on this PMPC Team?
@Admins - Please provide a status update regarding MSIX support since there was reference in the comments below that you were targeting March and it is May now. Teams Classic goes EOS June 30. https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability.
Is MSIX support required for you to rename the old Teams as "Classic"?
Is MSIX support required for New Teams since Microsoft provides the TeamsBootStrapper.EXE that you can run with -p -o plus the path/filename to the MSIX.
Hi , We have already created a SCCM app for new Teams because we can not wait.... The SCCM app works but we have an issue in the Task Sequence with SCCM... There is no New Teams installed but in the log file (AppEnforce.log) I have exit code 0 (Installed). Can any help us?
Bump.... what is the status of this new backend that will support MSIX packages? Thanks!
This can be installed without the MSIX package, I am currently using the teamsbootstrapper.exe to doploy out and then have a powershell script to do the install plus removal of old machine wide installer.
Simplest way to install: teamsbootstrapper.exe -p
https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client