Messages

Hello,

We have made progress on this. We were able to solve the detection pretty quick, but it exposed some other issues around having to split up version 2 and 3 .NET Core Runtime.

I think we should have this complete by the end of next week at the latest.

Hey there,

We are working on resolving this one. Unfortunately Microsoft has the display version in the registry as a completely different version, such as '24.80.28821' so we are discussing how to handle this scenario.

We will let you know when this is resolved.

Hey there,

We are working on resolving this one. Unfortunately Microsoft has the display version in the registry as a completely different version, such as '24.80.28821' so we are discussing how to handle this scenario.

We will let you know when this is resolved.

Hello,

The EXE version of Wireshark should now detect as expected. You will need to delete the application from Intune, and then run a Publisher sync to recreate it with an updated detection method.

Just to be safe, you can also uncheck Wireshark as a product, apply settings, then re-check Wireshark, and apply prior to running a sync.

Let us know if it doesn't work!

Yeah, I figured you understood 

It is a frustrating experience for us as well. Most vendors, by a large margin, do not give us these hash mismatch headaches!!

Here is an updated link for 15.9.4

https://patchmypc-my.sharepoint.com/:u:/p/cody/EdjzLBwnjoJAueEXrgFkrDkB4L_KfSLsICpF3xsW_WNbAg?e=jjusfN


Unfortunately, this is a TeamVeiwer vendor issue. We are reaching out to them in hopes they can help us understand why their download links provide an inconsistent binary.

The application should work as expected now.

The next version of Firefox that is created should not have this happen again. If it does, please let us know.

Hello,

This was a bug in an old build.

You can safely replace the %20 with a space character and then do an 'update content' on the distribution points.

Alternatively, you can delete the application and resync the publisher to have the application recreated.

Hello,

Unfortunately, TeamViewer seems to be distributing different files from different parts of their Content Delivery Network. This is causing a hash mismatch for some of our customers.

You can use this link -> https://patchmypc-my.sharepoint.com/:u:/p/cody/EdjzLBwnjoJAueEXrgFkrDkB4L_KfSLsICpF3xsW_WNbAg?e=SIHK2u to get a copy of TeamViewer 15 that matches the hash in our catalog.

We are currently waiting for TeamViewer to have a consistent hash across their CDN to update the value in our catalog.

In the meantime, you can use the link above and use our local content repo option described in the link below.

https://patchmypc.com/local-content-repository-for-licensed-applications-that-require-manual-download

Good to hear! Thanks for making us aware of the issue.

Hello,

We have just updated this on our end.

Can you please delete your Intune Application / Update for Node.JS, and then run a sync in the Publisher to recreate the app?

Node.JS NON LTS should now only update a version 14 install. So the Node.JS app will not update the version 10, or version 12 versions of Node.js.

Worth noting, it will also not update a version 13 build.

Let us know if this solves your issue.

Hi there, looks like we might need a major version filter on this! I'll do some testing and let you know.

brandonm,

You are welcome to install the SSRS reports that we provide and look at the existing queries to see how we do this filtering.

I believe there is a particular column that contains a URL. We use this column to filter out the Microsoft updates.

https://patchmypc.com/free-software-update-compliance-dashboard-reports-for-microsoft-sccm

We do have customers doing exactly what you are describing. They include files or folders, for Java such as configs and certificate stores, and then process them as part of the installer with the scripts.

This option is available in the 'Add custom pre/post update installation scripts/ right click option. Is this not working for you?

Hello,

Glad you were able to determine the root cause. I didn't see a Calendly event come through that I know of, so I don't think there is anything to cancel.