Messages

No. It won't. Not yet, anyway. You need to build an app that searches for the machine wide installer, uninstalls it, then clears out the app folders for all users %appdata%/local/microsoft/teams, then installs new teams. I know you said that you have mostly user installs, the easy way to nuke them is just nuking those folders. I can share some code if you'd like, I used PSADT.

Note that you will need to coincide this with changing your enterprise tenant default to new teams.

You CAN coexist them and then change default and then remove as well, just know that once the new flavor is there all the old flavors will stop updating and sit there vulnerable forever---well, assuming you change your default.

Hello, I'd be interested in seeing that code if you're still willing to share. Thanks

Thank you for the reply Spencer - I'm reviewing the link now.

Hello, I have a general question and I'm not sure if it's answered elsewhere.  If so, please do guide me to the relevant post/article/FAQ.

We're transitioning away from SCCM to Intune and have been using Patch My PC to publish apps and updates into Intune. 

I'm just trying to understand the main differences between full "apps" and "updates" and how the deployment works.  Ideally, I'd like to push all of the appropriate "updates" to our "All Windows PC" AAD group.  What happens on PCs which don't require the update?  Does the full content drop, a script run and then decide the update isn't required, or does it run the script and then pull the content if it is needed?

My ideal situation is to turn on all updates, but I don't want to drop content on thousands of PCs which isn't required just to patch a few hundred PCs.  Equally, I don't want to be manually populating AAD groups for the apps which have a smaller footprint in our estate.

Thanks in advance

Hi All

We're trying to upgrade the version of Cisco AnyConnect used across our estate to the latest version (4.10) and have successfully used Patch My PC to package it for Intune.

However, we're encountering an issue as some of our devices originally had version 4.2 and were updated to a newer version.  On these PCs, the installer fails.  From manually running the installer, it's because it's looking for the 4.2 installer which was originally in the SCCM Cache but has long since been removed.  If I manually install 4.2 and then let Intune run the 4.10 update again it successfully upgrades.

I know this isn't strictly a Patch My PC issue, but I was wondering if anyone else had encountered it and if so, how did you resolve it as we have over 7000 PCs to update.