Messages

The process should be the same then.

Duplicate lines 189-201, modify them to copy your json and your new xml file.
It should work.
Let us know if it won't.
We recommend running a test on a few devices before deploying this to production.

Hello asgeirk,

Are the config files for those additional modules XML files as well?

If that's the case, you can specify those additional xml files in the "Additional files" section, and modify the script we use as an example to copy those additional file to the right destination path.

You can duplicate lines 189-201 and adjust them to account for your new configuration files.

That's definitely a step forward, thank you for the update!

If you run into any other issues, let us know!

Hi EricS,

Thanks for reporting this.
This issue will require further investigation, can you please open a support case with us?

I checked the applicability rules for this update, and they look correct.
I'm curious which VLC update you are deploying - x64/x86 and MSI/EXE.
I'm also curious to look at the VLC version installed on a device which is listed as already compliant.
Can you please run this script on such a device?
https://github.com/PatchMyPCTeam/CustomerTroubleshooting/blob/Release/PowerShell/Export-PMPCInstalledSoftware.ps1

It will export a CSV file with app information.
It will allow us to verify the applicability rules for the VLC update.

hey Madd,

Replying to this while Ben is out of the office.

At the moment, due to limitations in our detection scripts, any software with the same product code for each version cannot be used for updating the software, as it's going to be detected as installed.

We are working on updating the detection script template to account for such software as well, and look beyond the product code and check the DisplayVersion as well.

We are offering such software as an Intune App for customers that would like to install on devices which don't have it installed at all.

If you'd like to use it for updates, you would have to manually edit the detection rule and set it to check the product code AND the version instead of using our script.
This will have to be done manually every time there is a new version, unfortunately.

As I mentioned earlier, we are working on improving our detection scripts. If you'd like to be notified this will be complete, please upvote this idea on our UserVoice.

Hey JoeH,

Unfortunately, that isn't the case.
Intune doesn't collect app architecture information from the devices.
So, if one device has "Google Chrome" installed, the Scan feature will show "1" device to both Google Chrome x64 and x86.

It only works correctly for software which the DisplayName contains the architecture: e.g. Notepad++ (x64).

Thats True, but there is also an other Microsoft Power BI Desktop (Optimized for Power BI Report Server - May 2023)
Version 2.117.984.0
Exe: PBIDesktopSetupRS_x64.exe
https://www.microsoft.com/en-us/download/details.aspx?id=56723

We already support this application.

Hi Zuerom,

Could you please offer more details? Maybe I am misunderstanding your question.

PMPC already offers "Power Bi Desktop" and "Power BI Desktop Report Server" as two separate products.

Hello Nilz1,

PMPC has the latest build the vendor still supports on Windows in the catalog.

For some older versions they have released security fixes, but are no longer offering Windows installers. Here is an example, for instance.
https://www.python.org/downloads/release/python-3816/

Why is the release of Python 3.8 so old (3.8.10)?
We have some developers who need 3.8 but we would like to use a newer release.

Hey Nilz1,

Please allow me some time to check internally and see what happened here.

Could you please gather these log files from a device and open a support case with us?

• %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
• %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
• %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
• %ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
• %ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log

Hi,

MEM Intune/Azure Environment here.
Every second PC or so seems to be getting this error when trying to install Oracle Java 8 JRE 8.0.3710.11 (x64).  Just occurred on a freshly imaged and deployed device, but the previous device has no issues.
Both devices have the same basic staff profile, Microsoft Surface devices running Windows 10 22H2 Enterprise.

Hello Trevor,

That error message means that the file cannot be found on the device. It could mean that it was deleted before the install could take place.
This usually means that the file is being quarantined by a security solution. Can you please check your AV and whitelist installers from the IME Cache?

Seems like PMPC has stopped getting updates for Microsoft Azure CLI. Latest version from Microsoft is 2.48.1 (https://github.com/Azure/azure-cli/releases/tag/azure-cli-2.48.1), but PMPC is only providing 2.47.0.

Is there something wrong here?

Hello DavidS,

Thank you for reporting this to us. Our automation which should have notified us when newer version were released was broken for this software.
This is now fixed.
We will add the latest version to our catalog with today's release.

Hi dhwatts,

You were close!

If you need to make changes to an already published Intune App / Intune Updates you can either:

• Delete the entry in Intune, right-click on the software in PMPC and make the config change. Then run a new PMPC sync.
• Make the change in PMPC, right-click to enable the "Republish" option, run a new sync. Deleting the app will NOT be necessary.

In your case, I think running a new sync should fix it. If it doesn't, please open a support case with us.

A list of known issues can be found here:
https://patchmypc.com/known-issues-and-considerations-when-using-patch-my-pc

For anything that is not on that list, we recommend opening a support case with us, and we'll hunt for a resolution for you.