Patch My PC Publisher

Please add a billing API so MSPs can ingest billing details for all of their partners so that we can ensure accurate, consistent billing is being charged to each partner without needless manual work.

Same Idea as this: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-4541 But for Publisher Pre/Post Scripts

The Update Windows of PatchMyPC for the Users are not informative enough with the dropdown of to close applications before the update begins. As we also use PSADT we saw how closing of applications for installations is handled there and asked us w...

Using PMPC on a local server that syncs to Intune. Twice I have had an app selected for a manual / selective sync, but when I went to run it, the selective sync dialog did not popup and it immediately went to run a full sync. Please add a dialog w...

Currently, ConfigMgr Apps made by Publisher have an administrative comment something like "Created by Patch My PC Version 2.1.99.0". This feature request is to provide the abiliy to customise this comment attribute via right-click option at the pr...

Currently we only have a tab to manually synch but in the sync status it seems like all or nothing approach. When importing an app, especially something you are working on testing different options in a pre/post, or tweaking 1 app and need to vali...

If i deploy an app/update and have enabled the Conflicting process option to prompt the user it would be nice to have an option for the UINotification process to provide a progress bar. Example: Zoom app is deployed with conflicting process option...

We ran into an issue where Custom Apps published through PMPC Publisher were failing to be published because the folder paths were too long (>260 characters). We enabled long paths on our server, but it appears the PMPC Publisher is not long pa...

So that the OnPrem Publisher is not running under the SYSTEM account, the option to run the Publisher under a Group Managed Service Account would be useful. Even if it's just a documentation of the permissions we need to be able to set this up.

Splunk 10.2 patch is not supported on Server 2016. Thus, all deployments to collections containing Server 2016 show failures. We already have plenty of Software Update Groups and collections and aren't looking to add more.