Messages

You really shouldn't have to worry about it any more. Just migrate to 'New Teams for Work or School' which is a WindowsApp and moves to C:\Program Files\WindowsApps\*  using a new directory for each version release - So that does mean you need to get your user shortcuts from 'shell:appsfolder'

I really, really dislike advice like this. Is there feature parity between new teams and classic teams? What if an organisation, lets just throw out a hypothetical, had users who were preventing your solution from working?

How about we just patch the version of teams that's used as a stub installer that lives in program files, while people handle their own migrations?

Thanks, cdnk3v.

We plan to support it by adjusting our detection scripts to ignore product code (when told to do so, for edge cases like this) and explicitly look at DisplayName and DisplayVersion (which is how EXE detection works.)

Wondering how this is going Adam? I appreciate and understand what you're saying about teams living in the users profile, but I need to update the old copy in program files, so that the 'source' installer is not a vulnerable version on my fleet.

Can I ask what you mean about the MSI code never changing? I thought from version to version, you want an app to maintain the same MSI code, so that it gracefullly replaces the old one when an install succeeds. I can't see what you mean by microsoft warning you not to update the machine wide MSI once it's installed - on this page? https://learn.microsoft.com/en-us/microsoftteams/msi-deployment#pc-installation