Patch My PC Publisher

I added the option to include logging for the updates but I later discovered that I needed to republish the apps. If I did not look at my daily patch email and saw the warnings, I would never have known and my systems would not get the changes.

The ability to choose between merging and overwriting settings when importing. use case: 2 installations of the Publisher, 1 for ConfigMgr and 1 for Intune only. when wanting to consolodate down to 1 install there is no easy way to merge those set...

A customer asked if it was possible to filter which settings are copied between tabs in the publisher when using the "Enable all all products from the x tab.." - commonly referred to as the "Copy Settings" button. For example, if you set a custom ...

Now if you change a setting in a pmp app (pre-post action) trigger the publishing sync a new alert is send, would only want an alert with new version/update. Not when modifying the app settings.

Allow us to be able to set the default security scope of a newly created app, like Test or Testing so we can test the apps functionality before we release it for mainstream use among other co-workers.

Hi! I didn't see anyone else suggesting this, apologies if it already exists! The Powershell App Deploy Toolkit has an option to pass parameters to an installer and hide them from any log files the toolkit spits out. Is it possible to add an optio...

If the option to "Update Existing application in place" is set, and the "delay" option is used, if the switch is made to the "Create a new application" option, create the postponed apps at the next sync run, instead of waiting until the delay peri...

When updating existing SCCM apps in place, and when a new version is released, the update in SCCM is delayed by an X number of days, reference in the log file for how many days the publish is still delayed.

Display notification when trying to configure Azure App Registration within Intune Tab and Customer only has Enterprise license. Currently only says "Permissions not required", which is true, but it isn't clear why they aren't required.

Currently, the Publisher does not write to PatchMyPC.log when it posts to a webhook, but it does when it sends an email report. Additionally, writing to PatchMyPC.log when failing to post to a webhook would greatly help in troubleshooting.