Messages

This is definitely something that we can consider in the future. Right now, it is an on/off switch where "on" is "skip".

I found this idea: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-4417 which seems close to what you are looking for. I'd recommend voting for that idea and adding a comment on it, then you'll get notified if/when we ship it.

Hi Jesse,

For apps that we automatically enable Manage Conflicting Processes for (the ones with the icon next to them). We set them to "Skip" by default, as this has the least user-facing impact. You are free to adjust the setting to notify or force close.

Hello,

We will likely have Android Studio renamed to "Android Studio Latest" so that the update title is more accurate according to our naming standards: https://patchmypc.com/products-multiple-versions-patch-my-pc

Unfortunately, we will not be offering the previous versions at this time, as we already have many difficulties with this application due to the way they register their application in the registry. It also seems like your environment may be quite unique as Google recommends on this page: https://developer.android.com/studio/archive to use the latest version.

I think your best bet will be to have a collection of devices that can stay on the latest Android Studio version, and only deploy Android Studio updates to that collection. The other devices would need to be self-managed, or you could create installation packages for those devices.

I think you'll find all of your answers for logs here: https://patchmypc.com/logs

What you are seeing is expected. Typically WSUS updates run from SoftwareDistribution, and ConfigMgr Apps will run from CCMCache.

Hello,

We were able to ship this update today!

Thanks for making us aware of this! This one slipped through the cracks. We're investigating now, as the products we have currently specify the .NET framework as either 3.5 or 4.5 and it seems they only offer a .NET 6.0 compatible version now, so we'll likely need to make some changes on our backend for these newer versions. I expect we'll be able to make those changes and have an updated version sometime in the next week.

Hello,

This is the only report of this issue we have received. Would you please open a support case here: https://patchmypc.com/technical-support and provide the logs listed here: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs-intune

Thanks!

Perfect! Unfortunately, at the moment, those changes require a change in content, and we'll only sync updated content on a republish for Intune Apps and Updates. Glad it is working now!

Do both, choose republish on next sync, then choose selective sync, then run a sync and it should just republish that 1 app, and not process anything else.

Hello,

Since you've changed the settings in Manage Conflicting Processes, have you republished the App/Update? The Jabber App will need to be republished to get the latest changes in Manage Conflicting Processes.

I would still suspect a firewall block in this situation.

The publisher uses the .net built-in browser to download content (which is equivalent to IE) and the downloads occur as SYSTEM. So in order to accurately test the download, you would need to do so as SYSTEM, using either IE, or PowerShell. We've seen many times that firewalls will block downloads from the SYSTEM account specifically.

Hello,

This is helpful, however since it is downloading a zip, still can't fully automate it yet. The good news is, we are adding zip support in the publisher. I am hoping we'll be able to remove the manual download requirement by the end of the year (probably after the November Publisher release).

Because the Intune App is available, when a new version comes out, that new version will be deployed as available. So the new version will still just be available. Intune Updates should only be deployed as required, so the Intune Update will determine if an older version of the app is installed and install it via the required assignment. The Intune App will just sit in Company Portal, as it is only an available assignment.

Hello,

Our current plan is to keep it held back until the next version releases; we expect a new version within a month. Once that new version is released, we'll watch it closely to see if the same issue reoccurs. We've decided to continue to hold this one back because it is especially disruptive when a customer encounters the issue with it.

Hi Paul,

Thanks for the update. I'll work with the Advanced Insights team and see if they think that prescript is still required.