Started by bezzoh, January 17, 2023, 03:28:58 AM
Quote from: cdnk3v on September 05, 2023, 07:57:24 PMI really think there should be some way to maybe add a prestart script in the PMPC deployment for Teams to remove and older version... or just remove the current version regardless.The challenge with having an old version of the System-Wide Installer installed on a machine is any new user that logs in, will get that initial version, then when it launches, it will get an update (at some point).Security scan software will pick up the System-Wide Installer that is out of date, and need to have it updated.So if the PatchMyPC deployment of Teams did do a remove first then an install, that I think may solve the issue.I also thought that the deployment would remove and install (not upgrade) the latest version, as we still have version 1.5 on our workstations, so a technician may log into a desktop for the first time, and it will install version 1.5, then they log out and never to log back into that machine, security scan software will detect this as out of date, and need it remediated, which means we have to rip it out of peoples profiles.the PatchMyPC Teams installer would not solve that issue, but keeping the System-Wide Installer up to date may help a bit in those use case scenarios... the ones Microsoft doesn't bother thinking of or testing.
Quote from: cdnk3v on September 05, 2023, 07:57:24 PMSo I vote for PMPC to look into this as part of the Teams installer.
Quote from: Adam Cook (Patch My PC) on September 07, 2023, 03:39:14 AMThanks, 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.)
Quote from: bezzoh on February 02, 2024, 01:56:11 AMYou 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'