• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Recent posts

#31
Any News about this
What does MS say?

Quote from: Hugo Marinho (Patch My PC) on October 17, 2025, 07:47:21 AMHi Niclas,

We'd love to support "update-only" behavior on macOS, but the limitation comes from Microsoft Intune, not from Patch My PC.

On Windows, we rely on Intune's Win32 app model, which allows custom requirements and detection scripts to check whether an app is already installed before updating. macOS app deployments in Intune don't have those same capabilities, there are no requirement scripts available for macOS apps, so we can't distinguish between "install" and "update" in the same way.

That said, macOS app deployment through Patch My PC Cloud is already available, and customers can absolutely use it today. As a workaround, you could assign macOS apps as "Required" to your target groups, which will make sure the apps are always up-to-date. To be clear, though, this is not "Update-only" because it will also install the app if it is missing.

Once Microsoft expands Intune's macOS app model to include requirement scripts or similar functionality, we'll add full update-only support.

Hope this clarifies the topci for you :)
#32
Thanks for reaching out!

When creating custom apps and uploading folders/files, you'll want to keep the same folder structure as defined by the application.

Therefore, it sounds like option 1 is the correct method here!

Upload the Primary installer file and then upload the entire base folder under "Additional Folders" so when the base installer runs it can correctly find and reference those other files.

If you run into any issues, please feel free to open a support ticket with us and we can help further!

https://patchmypc.com/technical-support/
#33
I am trying to build out a custom App, and before I commit to fully going in with this one I wanted some advice from those who have done it successfully.

The app I need to install is nested into a folder structure with several installers attached to the main install.  I have tested the commandline and it works so I just want to deploy it from PMPC instead of building intunewin every few months as it needs constant security updates.

Do I select the installer file and upload the base folder or the folder structure inside the base folder where the installer is? 1 or 2

Basic folder structure for reference.

Base folder (1 upload this to additional folder)
   - Installer which calls the other installers based on parameters selected in the commandline
      - several folders with separate installers for each piece (2 upload this to additional folder)
#35
For ConfigMgr, ScriptRunner can use the ID's to pull some information from the ccm client for additional information, but it's not strictly necessary. Intune deployments don't do any of that, so nothing really beyond that for the actually installation.

ConfigMgr App publishing will also use the values in the package.xml for doing some checking on what specific version is created.
#36
Thanks!

Re the notification bug. Yeah I think I spotted that previously running a PMPC package where the conflicting process was running on multiple users. I ended up killing the processes manually and running again and it worked fine.

Re the ID's. PMPC desktop publisher and it was 7-Zip by memory. Not a custom app.
Am I correct in understanding your response that this is mainly a logging thing? Just a plain text thing used to quote into the log files for troubleshooting purposes?

Or is there some functionality impacted beyond that?
#37
The AppID and UpdateID are mostly used to correlate installations with the specific versions of the product. And as you've noticed, there is no direct communication between scriptrunner and Intune. The Packages are self contained. You'll notice the values are used in the log as well.

Are the Intune Apps/Updates you are copying built by the Publisher, or our Cloud Portal? I ask because you'll notice our packages from the Cloud Portal can use a new command line parameter that has configurations built into it. So if you just run the patchmypc-scriptrunner.exe only, it's possible some of your configurations are not being passed to the 'installation'.

For the MCP notifications, they are only shown if the process is running. If no user has the app open, then the installation will continue and run.

With multi user devices, it will show the notification to which ever user has the process open. But I think we have an active bug right now that if more than one user has the process open, the installation will be skipped.
#38
Hey KRGU,

Please note that there was a hash change by the vendor for the installer recently and we have updated it in the catalogue.


Please re-publish the product and let us know how it goes.
#39
Currently on our servers we are manually installing software to them as our CIO did not want to deprecated WSUS and we didnt get budget approval for SCCM.

This has often simply just been us exporting a copy of an APP package from Intune, copying to the target device and running the script runner exe as admin. Works well enough and also means we have a consistent experience for things like user notifications, conflicts etc. etc.

Though looking at the XML with the packages configs I am a little curious how the ApplicationID and UpdateID fields are used by the script runner if at all.

The software appears to install perfectly fine on these non-intune managed devices and I am not aware of any direct upstream connectivity from the script runner to the Intune graph from the target endpoints.

Does anyone know how these values are utilised if at all?


As I was thinking of user notifications just made me wonder on a second thing...

When running the script runner as an admin, or as system, how many users get the notifications? If its a multi-user device do all users get the notification or only a subset?
#40
The first public release of Opera 134, specifically 134.0.5954.46, which is not the version PMPC incorrectly showed on July 30, and still shows on PMPC notices as current today, has been made available today (Aug 6) both from within the browser and at https://blogs.opera.com/desktop/