Messages

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.

Chrome EXE is the EXE installer, Chrome (x64) is the MSI installer.

If you the data you are looking at is in the database scan tool, the two installers look nearly identical, which is why the EXE may be detected in that tool even if the MSI is installed.

Glad to hear! Have a great weekend!

I totally agree with the need. We're working on some things with the PSADT group to hopefully make this easier in the future, however I don't have timelines available at the moment.

Hey Paul,

For this, I would recommend raising a support request with the team so that we can get a full set of logs and see what happened. https://patchmypc.com/technical-support

Typically, the fastest resolution for these issues is to delete the broken apps and their content and sync them again. The causes for this type of issue vary, but typically it is due to the Publisher not being able to find the existing app or content and recreating the app new instead.

We are actually going to switch this app off of local content, and are planning on doing so with the next release. The original reason for the local content was to ensure that customers didn't auto-enable the product without a license. However, we now have other controls to block auto-enable for products, so we will turn that on for Java 8, and make it not a local content product. I believe the next release is scheduled for October, additionally we are going to improve the pre-install script for that app as well.

Hello, we have a similar idea here: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-4019

Please vote on that idea and provide additional feedback, and I'll see if I can get it in front of the devs. Thanks!

Hello, you can upload the file here: https://patchmypc.com/how-to-share-large-files

Thank you!